[Discovery] SiteMap linking to IIIF Resources (with ResourceSync properties)

[Nuno Freire]

Hello everyone,

After gathering all the comments on the first attempt to build a  SiteMap at University College Dublin for resources available by IIIF, we are preparing another solution of a sitemap based on ResourceSync elements. We are at a stage were the community advice would be very welcome.

This is the current SiteMap with a ResourceSync element:

...
<url>

  <loc>https://digital.ucd.ie/view/ucdlib:38491</loc>

  <rs:ln rel="alternate" href="https://data.ucd.ie/api/img/manifests/ucdlib:38491" type="application/json"/>
...
</url>

In this SiteMap, the 'loc' element contains the URL on the digital library website, and refers to the IIIF resource as alternate resource.

This sitemap, however, does not allow the IIIF provider to explicitly state that the related resource is IIIF compliant.

If a dcterms:conformsTo attribute is added, with value 'http://iiif.io/api/presentation/2.1/', would we have a valid solution?

Example:

...
<url>

  <loc>https://digital.ucd.ie/view/ucdlib:38491</loc>
  <rs:ln rel="alternate" href="https://data.ucd.ie/api/img/manifests/ucdlib:38491" type="application/json" dcterms:conformsTo="http://iiif.io/api/presentation/2.1/"/>
...
</url>

Thank you in advance for any comments and suggestions.

Kind regards,

Nuno  

[Nuno Freire]

Hello everyone,

The second Europeana case study, on using SiteMaps for discovery of IIIF resources, is with the National Library of Wales (NLW).

The NLW has provided a Sitemap with a different approach. Instead of the ResourceSync elements, elements from the IIIF Presentation namespace are used.

Here is an example:

<url>

 <loc>http://newspapers.library.wales/view/3679651</loc>

 <iiif:manifest xmlns:iiif="http://iiif.io/api/presentation/2/">

   http://dams.llgc.org.uk/iiif/newspaper/issue/3679651/manifest.json

  </iiif:manifest>

 <iiif:within xmlns:iiif="http://iiif.io/api/presentation/2/">

   http://dams.llgc.org.uk/iiif/newspapers/3679650.json

 </iiif:within>

 <lastmod>

 2014-11-08

 </lastmod>

</url>

Thank you in advance for any comments and suggestions.

Kind regards,

Nuno  

PS: Thanks and acknowledgments to Glen's and John's efforts with the Sitemaps. 

[Jason Ronallo]

I've created a branch of the tasks I use to create sitemaps in our
Blacklight catalog that can include URLs to manifests using the
<iiif:manifest> tag from the NLW demo:
https://github.com/jronallo/blacklight-sitemap/tree/iiif-manifest

I have this sitemapindex in our staging environment:
http://scrc.lib.ncsu.edu/sal_staging/sal-sitemap.xml

And an example urlset:
http://scrc.lib.ncsu.edu/sal_staging/sal-sitemap0.xml.gz

I do like that I can include the URL to the manifest in the same
sitemap that I'm already creating for the search engines which. That
made it easy to accomplish. I can easily change my implementation
based on whatever the community adopts.

Even if this approach is the one accepted by the community I don't
know that I've included the namespace and all correctly. The NLW demo
includes the xmlns:iiif directly on each element that uses
iiif:manifest while I added it at the root element.

I thought I'd give this a try since I'm eager to hear more feedback on
Europeana's experiments and see more folks publish something like this
in sitemaps.

Best,

Jason

> --
> -- You received this message because you are subscribed to the IIIF-Discuss
> Google group. To post to this group, send email to
> iiif-d...@googlegroups.com. To unsubscribe from this group, send email to
> iiif-discuss...@googlegroups.com. For more options, visit this
> group at https://groups.google.com/d/forum/iiif-discuss?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "IIIF Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iiif-discuss...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Nuno Freire]

Hello Jason,

I'm very glad to have your feedback.

Using the iiif:manifest element is a very straightforward solution. The sitemap is very easy to read and interpret. 

I wonder if anyone sees benefits in using ResourceSync elements, instead. I lack practical experience with ResourceSync to form a strong opinion...

 

Even if this approach is the one accepted by the community I don't 
know that I've included the namespace and all correctly. The NLW demo 
includes the xmlns:iiif directly on each element that uses 
iiif:manifest while I added it at the root element. 

Stating the namespace is correct in both cases. It results in equivalent XML data.  

All the best,

Nuno