Data Ingestion Guidance: Difference between revisions

Jump to navigation Jump to search
Line 148: Line 148:
*If submitting media records with specimen data records, here are the critical fields to fill in:
*If submitting media records with specimen data records, here are the critical fields to fill in:
** sample
** sample
***id = (this is the coreid field in the Audubon Core extension file), it matches one identifier among the related specimen records <pre>urn:catalog:institutionCode:collectionCode:catalogNumber</pre>
***id (dc:identifier) = (this is the coreid field in the Audubon Core extension file), it matches one identifier among the related specimen records <pre>urn:catalog:institutionCode:collectionCode:catalogNumber</pre>
***identifier  (dcterms:identifier) = id of the media record - needs to be unique within Audubon Core file, is the equivalent of the occurrenceID in the occurrence file <pre>urn:catalog:institutionCode:collectionCode:Image:catalogNumber</pre>
***identifier  (dc:identifier) = id of the media record - needs to be unique within Audubon Core file, is the equivalent of the occurrenceID in the occurrence file <pre>urn:catalog:institutionCode:collectionCode:Image:catalogNumber</pre>
***accessURI (ac:accessURI) = direct http link to the media file. See other info about this not being a link to an enclosing web page containing the media file <pre>http://bgbasesrvr.univ.edu/DATABASEIMAGES/LONN00000001.JPG</pre>
***accessURI (ac:accessURI) = direct http link to the media file. See other info about this not being a link to an enclosing web page containing the media file <pre>http://bgbasesrvr.univ.edu/DATABASEIMAGES/LONN00000001.JPG</pre>
***providerManagedID (ac:providerManagedID) =  if you have a UUID GUID for your media records, then assign it to the optional ac:providerManagedID field. <pre>urn:uuid:32e5da5d-c747-435c-a368-07d989259bf4  (optional)</pre>
***providerManagedID (ac:providerManagedID) =  if you have a UUID GUID for your media records, then assign it to the optional ac:providerManagedID field. <pre>urn:uuid:32e5da5d-c747-435c-a368-07d989259bf4  (optional)</pre>
here are further recommended fields to fill in:
*ac:associatedSpecimenReference
*dc:rights or dcterms:rights
*xmpRights:Owner
*dc:creator
*dc:type or dcterms:type
*dc:format
*dcterms:title
*ac:licenseLogoURL
*'''Note to aggregators''': In the case where the data are coming from an aggregator, an additional ''recordId'' field is required (idigbio:recordId). This is the media identifier, distinct from the one given by the provider in the dcterms:identifier field. It is assumed that aggregators are building their own archives, as this is not a Darwin Core term, and is not supported in the IPT.
*'''Note to aggregators''': In the case where the data are coming from an aggregator, an additional ''recordId'' field is required (idigbio:recordId). This is the media identifier, distinct from the one given by the provider in the dcterms:identifier field. It is assumed that aggregators are building their own archives, as this is not a Darwin Core term, and is not supported in the IPT.
*'''Terms''': Use Audubon Core terms, http://terms.tdwg.org/wiki/Audubon_Core_Term_List, with one record for each media record. The more you can flesh out the details of the image, the more likely it will be to be highly retrievable. The best practice is to use the taxonomic and geographic fields to capture as much information as possible when only media are given to iDigBio.
*'''Terms''': Use Audubon Core terms, http://terms.tdwg.org/wiki/Audubon_Core_Term_List, with one record for each media record. The more you can flesh out the details of the image, the more likely it will be to be highly retrievable. The best practice is to use the taxonomic and geographic fields to capture as much information as possible when only media are given to iDigBio.
5,887

edits

Navigation menu