Skip to content

Instantly share code, notes, and snippets.

@tomcrane

tomcrane/IIIF-Notes-Wellcome_102016.md

Last active January 27, 2017 13:09
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tomcrane/44c39a3408e43a2185eef0fff552da0c to your computer and use it in GitHub Desktop.
Save tomcrane/44c39a3408e43a2185eef0fff552da0c to your computer and use it in GitHub Desktop.
Download ZIP
Raw
IIIF-Notes-Wellcome_102016.md

Some examples about how your objects in IIIF (the bridge to the Human Presentation API) link to semantic description (your model, or other shared models). The IIIF manifests for all "catalogue" objects would link to a semantic description via the seeAlso property:

seeAlso

A link to a machine readable document that semantically describes the resource with the seeAlso property, such as an XML or RDF description. This document could be used for search and discovery or inferencing purposes, or just to provide a longer description of the resource. The profile and format properties of the document should be given to help the client to make appropriate use of the document.

While your catalogue Manifests link to some experimental RDF, your IIIF Collections currently don't link to seeAlso resources, but they should, expecially when you start making ad hoc curated collections. And similarly for ad hoc manifests.

This strong link between the Presentation API object that people "see" and the semantic description in your model is fundamental to a complete representation of your objects, and that the distinction between the purposes of the two descriptions informs some fundamental design decisions. The strong link goes both ways:

from the manifest:

  "seeAlso": {
    "@id": "http://wellcomelibrary.org/resource/b23984995",
    "format": "text/turtle"
  }

and to the manifest (in the model you'll create and I hope express as JSON-LD):

<http://wellcomelibrary.org/resource/b23984995> wdrs:describedBy <http://wellcomelibrary.org/iiif/b23984995/manifest>.
<http://wellcomelibrary.org/iiif/b23984995/manifest> a <http://iiif.io/api/presentation/2#manifest>.

Discovery and inferencing...

There's something extra on the UAT environment that I've been experimenting with:

http://wellcomelibrary.org/iiif/b23984995/manifest

Whereas your live manifests only have one seeAlso link, this one has three - each with a different profile. These profiles are not real, but they represent how an IIIF aggregator or discovery platform might better understand what your IIIF resources are through common models like Dublin Core and Schema.org

  "seeAlso": [
    {
      "@id": "http://wellcomelibrary.org/data/b23984995.json",
      "format": "application/json",
      "profile": "http://wellcomelibrary.org/profiles/res"
    },
    {
      "@id": "http://wellcomelibrary.org/resource/schemaorg/b23984995",
      "format": "application/ld+json",
      "profile": "http://iiif.io/community/profiles/discovery/schema"
    },
    {
      "@id": "http://wellcomelibrary.org/resource/dublincore/b23984995",
      "format": "application/ld+json",
      "profile": "http://iiif.io/community/profiles/discovery/dc"
    }
  ]

The latter two link to small chunks of data that a community might agree on. These just happen to be the structured data embedded in your item pages right now, and would need a bit of tidying up before using them on their own as I am here, but you get the idea:

http://wellcomelibrary.org/resource/dublincore/b23984995

{
  "@context": {
    "@vocab": "http://purl.org/dc/terms/"
  },
  "@type": "http://purl.org/dc/dcmitype/StillImage",
  "title": "Healthy adult human brain, tractography from MRI.",
  "subject": "Magnetic Resonance Imaging., Brain.",
  "description": "Sagittal view of a healthy adult, living human brain, virtually sliced down a vertical axis dividing it into left and right halves. The front of the head is facing towards the left side of the image. Information on neural tracts or pathways of white matter in the brain were collected by a type of magnetic resonance imaging (MRI) which tracks the movement of water molecules within tissue, similar to diffusion tensor imaging (DTI). This was used to reconstruct a digital model in the style of a Joseph Jules Dejerine anatomical drawing. This method of tractography is being used to map networks inside the brain to use as a tool for teaching neuroanatomy and to build atlases of the human brain. Field of view is 256 x 140 mm. Magnetic resonance imaging 2014",
  "type": "http://purl.org/dc/dcmitype/StillImage",
  "relation": {
    "@id": "http://wellcomelibrary.org/iiif/b23984995/manifest",
    "@type": "http://iiif.io/api/presentation/2#manifest"
  },
  "creator": "Dell'Acqua, Flavio; Wellcome Images",
  "identifier": "b23984995"
}

http://wellcomelibrary.org/resource/schemaorg/b23984995

{
  "@context": "http://schema.org/",
  "@type": "Painting",
  "name": "Healthy adult human brain, tractography from MRI.",
  "description": "Sagittal view of a healthy adult, living human brain, virtually sliced down a vertical axis dividing it into left and right halves. The front of the head is facing towards the left side of the image. Information on neural tracts or pathways of white matter in the brain were collected by a type of magnetic resonance imaging (MRI) which tracks the movement of water molecules within tissue, similar to diffusion tensor imaging (DTI). This was used to reconstruct a digital model in the style of a Joseph Jules Dejerine anatomical drawing. This method of tractography is being used to map networks inside the brain to use as a tool for teaching neuroanatomy and to build atlases of the human brain. Field of view is 256 x 140 mm. Magnetic resonance imaging 2014",
  "thumbnailUrl": "https://dlcs.io/thumbs/wellcome/1/8735b6e2-d91d-4f63-8535-97643eceb9b6/full/100,75/0/default.jpg",
  "creator": [
    "Dell'Acqua, Flavio.",
    "Wellcome Images."
  ],
  "datePublished": "2013.",
  "about": [
    "Magnetic Resonance Imaging.",
    "Brain."
  ]
}

You might notice that this is of type https://schema.org/Painting... the metadata needs work!

IIIF Collection route through archives

This could drive a visual browse interface (possible discussion topic for discovery tomorrow).

seeAlso at every level links to semantic description (plus schema.org and dc variants for interested aggregators) - this is what discovery tools should index - NOT the strings in the IIIF resources!

I haven't put the thumbnails in yet - a collection browser/explorer would have to negotiate the clickthrough auth step. The new "external" pattern in the Auth spec lets you handle that absolutely any way you like if you're controlling the UI (e.g., your web site rather than someone else's viewer - the someone else falls back to clickthrough).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment