Conference Agenda

We introduce Wolpi, a new open source IIIF Image API server with a focus on quick and easy extensibility to adapt to individual requirements. Extensions can be written in JavaScript or Python and shared with the community through their respective native package ecosystems. Wolpi is built on the JVM and libvips for efficient and high quality image processing.

Get an insider view of a versatile and lightweight component that gives archivists a visual tool to create, edit and publish IIIF structural ranges. Using intuitive design, digital curation experts can take advantage of infinite possible combinations and structure configurations, empowered with a clear visual representation of the ranges being created. This talk will cover the design, development, user feedback, and iterations that have been necessitated over the last four years of the visual structure editor’s implementation.

We present aiiinotate (https://github.com/Aikon-platform/aiiinotate), a fast and scalable IIIF annotation server aimed at managing computer vision data. aiiinotate offers a minimal REST API with routes to read, update and delete annotations, as well as routes for batch processing and a CLI for maintenance operations. The annotation server relies on robust technologies built with speed in mind: the MongoJS database system, the NodeJS Web framework Fastify, and AJV for fast schema validation. To be easily integrated in preexisting workflows, aiiinotate is compatible with Mirador 4 and its Mirador-Annotation-Editor plugin. It is distributed through NPM and can be deployed using Docker. In benchmarks, aiiinotate has handled up to 100 million annotations, demonstrating its scalability.

How does IIIF affect the process of migrating to a new repository and vice versa?

Leiden University Libraries (UBL) is currently in the process of developing and migrating to a brand new repository for all our (millions) digital objects. This has impact on the way we work with IIIF.

The issue we faced is that in the new situation, all the manifests and their location would change, resulting in broken links for our users. Furthermore, because of other projects going on, it is likely for us that this would occur again in our near future. Not user-friendly.

Therefore, we developed an elegant solution we call the Endpoint to our manifests. The ensures a seamless transition that our end users will not even notice, and will make sure that this remains true in the future, even if we change the manifests or locations again. In short, it does so by using unique identifiers to make sure the correct manifest is retrieved for the requested item. In this presentation, we will go show in detail how this Endpoint works and is in line with the IIIF-philosophy: sustainable, future-ready and user friendly.