Closed GoogleCodeExporter closed 2 years ago
Comment from Cyndy Parr <parrc@si.edu> during public comment:
Re: dcterms:source
We have trouble explaining this one to our providers. In many if not
most cases, the published source is the provider's own page (e.g. if
the image is original to a particular website, we want the URL of the
web page which provides the context in which it first appeared). So
an example like this in the Notes would be helpful.
Note from Steve: I agree that examples both for dcterms:source and
ac:derivedFrom would be useful. I am not sure whether it is appropriate to put
more in the notes section or if it would be better to just include this in
examples given in an informational (Type 3) guide that isn't actually included
in the standard.
Original comment by steve.ba...@vanderbilt.edu
on 25 Apr 2013 at 4:52
Comment from Cyndy Parr <parrc@si.edu> during public comment:
If the resource has been assigned a GUID or is also associated with an
identifier issued by a previous agent or project, where would that go?
Original comment by steve.ba...@vanderbilt.edu
on 25 Apr 2013 at 5:57
Comment from Margaret Cawsey <Margaret.Cawsey@csiro.au> after the end of the
public review:
I am recording details of the transportMechanism i.e. how we hold/receive the
sound recordings from the recordists (= collectors) and the brand of this
mechanism, e.g. CD-R might be the transportMechanism and Verbatim might be the
brand. Probably more important for open reel tapes. Cornell sound library keeps
this kind of information at the and we are following their example.
A reply from Steve in an email: As far as the transport/mechanism is concerned,
it seems a bit more complicated. There is the term dcterms:format which would
be appropriate for describing the format of the resource that was sent to you,
although the recommended values don't get as specific as you mention (there's
Data-CD and Audio-CD, but nothing about the brand). If the metadata that you
are recording is for a resource that will be electronically online, then
perhaps the most appropriate thing would be to have two records: one for the
available (online, digital) resource and one for the physical (CD-R) resource
and then link them using dcterms:source. But I'm not sure about this.
Original comment by steve.ba...@vanderbilt.edu
on 29 Apr 2013 at 4:00
Original comment by morris.bob
on 3 Jun 2013 at 4:55
Original comment by morris.bob
on 3 Jun 2013 at 5:08
I've assigned this to Milestone-BestPracticesDoc as these should be in
information documents as Steve suggests
Original comment by morris.bob
on 9 Jun 2013 at 2:13
Original comment by morris.bob
on 22 Oct 2013 at 2:40
Comment copied from https://github.com/tdwg/ac/issues/117:
Find out how GBIF, iDigBio, SYMBIOTA etc. are, or would like to, be using Audubon Core and create best practice document based on that.
Comment copied from https://github.com/tdwg/ac/issues/117:
An example of use is the NEVP project, wrapping DwC and AC assertions about information captured at a high throughput digitization apparatus in a W3C Annotation document for transport to Symbiota and the database of record for ingest of that data. For an example document see: https://sourceforge.net/p/filteredpush/svn/HEAD/tree/FP-Design/trunk/ontologies/oadExamples/NEVP_specimen_example.xml There is also code in Symbiota to process these documents. @ramorrismorris was involved in crafting these documents.
We now have an examples guide for Still Images: https://github.com/tdwg/ac/blob/master/image/examples.md and a stub for Sound: https://github.com/tdwg/ac/blob/master/sound/examples.md We have established this paradigm and can generate guides for other media types when there is interest to create them.
Original issue reported on code.google.com by
steve.ba...@vanderbilt.edu
on 9 Apr 2013 at 1:20