A repository manager or scholar wishes to query a third-party tool with IIIF ingest capability for collections, manifests or canvases that have been imported into that tool, and receive a response providing useful information

[jbhoward-dublin]

Description

Some information services support IIIF client capability to enable ingest of resources via IIIF collections, manifests or canvases. These services might support transcription, new manifest derivation, etc. A repository manager or scholar may wish to query these services to determine whether a resource of interest has been ingested into the service, and receive useful information about the resource and its state.

Variation(s)

The issue could apply to transcription platforms, portals that aggregate resources supporting IIIF (such as Europeana), tools for synthesizing new manifests from distributed IIIF resources, etc.

Proposed Solutions

(1) a common query service for the various platform types might ask the basic question, "Is there a resource in the target platform derived from this collection, manifest or canvas ID?" ; a response might provide a URI in response, either to the manifestation(s) of the resource, or to an info service that returns metadata about the derivative resource.

(2) as different third-party platforms that ingest IIIF manifests will have varying service profiles, a IIIF service might be conceived to characterise the platform and provide a link to a service profile and a query endpoint.

Additional Background

A local use case involves creating a hyperlink, either in a view of a resource's descriptive metadata or a view of the digital resource in Mirador, to a remote transcription platform. A query originating locally would ask a remote endpoint whether the resource represented by a specific manifest ID or canvas ID exists in the transcription platform. A response could be a simple link to a view of the resource in the transcription platform; or a JSON response might include further useful details, including status of the resource (transcribed or not, translated or not, etc.), and disseminations of transcribed resources by MIME type, etc. The response would be parsed and appropriate action taken to create a link, etc.

[sdellis]

I am unclear of the problem that this proposal is trying to solve. Is the problem that a repository manager has no way of knowing what third-party transcriptions (or other derivations or annotations) of an object exist? If so, is this not expressed adequately enough in #71?

[jbhoward-dublin]

Perhaps the intentions are the same. In this case the problem is discovering whether some IIIF resource has been ingested into, or a derivative resource has been created in, a in a third-party's information system; further whether that system can return useful information about the state of the resource and how to capture manifestations of it. I am simply offering a more detailed use case including proposed solutions and additional background that the template provides for. Hope that helps.

[azaroth42]

Discussion on call: The flip side of #83, and possibly a notification pattern for something other than a change. Not sure whether it's in scope or not, but certainly not going to work on it until we're further down the line with harvest / index and import.