View source for IIIF Linking Darwin Core

Part of [[IIIF|IIIF Pages]]

Many institutions publish their data to GBIF and other data aggregators using the [https://dwc.tdwg.org/ Darwin Core] metadata standard and its extensions. During the course of the project we established a convention for using the [https://www.tdwg.org/standards/ac/ Audubon Core] multimedia extension to publish IIIF manifest locations through Darwin Core. The extension is used in essentially the same way as it would be for a JPEG file. The figure below shows an example of a Audubon Core extension in a Darwin Core Archive metadata file.

<pre>&lt;extension 
   encoding=&quot;UTF-8&quot;
   fieldsTerminatedBy=&quot;,&quot;
   linesTerminatedBy=&quot;\n&quot;
   fieldsEnclosedBy=&quot;&quot;&quot;
   ignoreHeaderLines=&quot;0&quot;
   rowType=&quot;http://rs.tdwg.org/ac/terms/Multimedia&quot;&gt;
   &lt;files&gt;
      &lt;location&gt;darwin_core_images.csv&lt;/location&gt;
    &lt;/files&gt;
    &lt;coreid index=&quot;0&quot;/&gt;
    &lt;field index=&quot;1&quot; term=&quot;http://purl.org/dc/elements/1.1/type&quot;/&gt;
    &lt;field index=&quot;2&quot; term=&quot;http://purl.org/dc/elements/1.1/format&quot;/&gt;
    &lt;field index=&quot;3&quot; term=&quot;http://rs.tdwg.org/ac/terms/accessURI&quot;/&gt;
    &lt;field index=&quot;4&quot; term=&quot;http://rs.tdwg.org/ac/terms/associatedSpecimenReference&quot;/&gt;
    &lt;field index=&quot;5&quot; term=&quot;http://purl.org/dc/terms/identifier&quot;/&gt;
    &lt;field index=&quot;6&quot; term=&quot;http://purl.org/dc/terms/description&quot;/&gt;
    &lt;field index=&quot;7&quot; term=&quot;http://ns.adobe.com/xap/1.0/rights/Owner&quot;/&gt;
    &lt;field index=&quot;8&quot; term=&quot;http://purl.org/dc/terms/rights&quot;/&gt;
    &lt;field index=&quot;9&quot; term=&quot;http://purl.org/dc/elements/1.1/rights&quot;/&gt;
    &lt;field index=&quot;10&quot; term=&quot;http://purl.org/dc/elements/1.1/creator&quot;/&gt;
    &lt;field index=&quot;11&quot; term=&quot;http://rs.tdwg.org/ac/terms/serviceExpectation&quot;/&gt;
&lt;/extension&gt;</pre>
In the associated CSV file (in this case darwin_core_images.csv) the columns for the manifests would contain “application/ld+json” in the third column (dc:format), the URI of the IIIF manifest in the fourth column (ac:accessURI) and “IIIF” in the twelfth column (ac:serviceExpectation).

This can be implemented using the GBIF Integrated Publishing Toolkit. All records in the Meise Botanic Garden Herbarium that have an image of the specimen (about 1.3 M images available at the time of writing) have 2 rows in the Audubon Core extension. The first row is describing the available JPEG file, the second row is including the IIIF manifest.

[[File:Screenshot_of_the_IPT_of_Meise_Botanic_Garden_with_the_usage_of_the_%E2%80%98Audubon_Media_Description%E2%80%99_extension.png|Screenshot of the IPT of Meise Botanic Garden with the usage of the ‘Audubon Media Description’ extension.]]

This technique worked successfully and GBIF has added IIIF Icons to their portal interface.

[[File:Example_of_actionable_IIIF_Icon_from_RBGE_data_in_GBIF_data_portal.png|Example of actionable IIIF Icon from RBGE data in GBIF data portal]]

'''Recommendation:''' If you publish data using Darwin Core Archive format, please add the manifest locations using this method. They will then automatically appear in the GBIF portal as interoperable links and in the GBIF data API for incorporation into other applications.

Back to [[IIIF|IIIF Home]]