IIIF Discovery Client

[glenrobson]

From the EuropeanaTech IIIF workshop

The adoption of IIIF Change Discovery has been slow. Aggregators are waiting for a minimum number of available endpoints among their data providers, while data providers do not have a strong motivation to implement IIIF Change Discovery since aggregators are not yet operating based on it.

Although there are already some data providers with IIIF Discovery support, their endpoints are not widely known. Having a registry of available IIIF Change Discovery endpoints may help aggregators to see more potential in supporting aggregation via IIIF Change Discovery.

In addition, having open source tools to help in software development with IIIF Change Discovery could help in the uptake of the protocol.

Having a Python / Java / other programming language that wraps the Change Discovery API would make it easier to use.

[aisaac]

@glenrobson Maybe we could add a few more things for the notes (I think these mostly relate to the idea of demo-ing the client, not specifying more functions that it should support at the core):

• Need to provide some comparison to show the value of the Change Discovery API versus OAI-PMH. For instance, in terms of incremental harvesting.
• need to leverage the progress on standardised way to provide semantic metadata in IIIF resources with seeAlso and Registry of Profiles https://iiif.io/api/registry/profiles/
• would end-user facing demo of a Change Discovery API-driven interface help to make the standard more popular?
• connect with the idea of "IIIF universe", for which a seed can be found in the IIIF Registry at https://registry.iiif.io/. A demo could encourage registering Discovery streams there