As an aggregator of data, I want to aggregate both external IIIF resources and additionnal IIIF resources produced internally, while allowing external reuse of the latter

[regisrob]

Description

Context: the Biblissima web portal, which aggregates data from a wide spectrum of specialized databases and catalogues dealing with medieval manuscripts and early printed books, has a lot of information about illuminations and decoration, including captions, that can be linked to their corresponding Canvases.

What we have:

• links to IIIF manifests representing the physical objects, coming from Gallica and the BVMM (another french digital library of medieval manuscripts). These manifests URLs are used to initialized Mirador on the "Manuscripts" pages (and elsewhere in the portal).
• captions that describe the illuminations (among other metadata like rubrics, artists, dates, descriptors...), coming from iconographic databases like Mandragore (BnF) and Initiale (IRHT). Every caption can be linked to the Canvas that holds the illumination inside the manuscript.

What we need (to provide a better user experience):

• generate and expose a Range to represent the index of captions for each manuscript
• and populate this Range into Mirador wherever it is needed in the Biblissima portal, so as to enable users to browse through the illuminations without leaving the viewer

What we do not want (possibly):

• create, use and expose a derivative Manifest that would only include the Range we produce on our own with the data that we have, i.e. a new Manifest that would compete the "canonical" one (e.g. the Gallica one). Such a situation could be quite confusing for users and in our opinion does not go in the right direction in terms of data reuse (the Gallica manifest will always be the "preferred" one outside of Biblissima, in other contexts...)

What we want:

• create, use and expose a Range for our own needs AND allow reuse of this additionnal IIIF resource outside of Biblissima (first and foremost in Gallica itself, but potentially anywhere else, in another Manuscript portal referencing the same Manifest etc.)

Solution considered

Use a Notification mechanism to let client applications (including ourselves) know there are additionnal IIIF resources (Ranges) available at this URL we provide.

Additional Background

LDN work for IIIF Data Sharing and Mirador LDN plugin (with @jeffreycwitt and @cubap)