Feature #2064
closed
Added by Alexander Watzinger over 1 year ago.
Updated about 1 year ago.
Description
As discussed in the last developer meeting we also need an OpenAtlas IIIF client integration.
The choice and implementation of the IIIF client will be assign to our frontend team because it's more in their realm of expertise and we also want to use one at the presentation sites. But of course others can be involved too.
Mirador was mentioned, we can also ask our ACDH-CH sysadmins who have already some experience with it.
Short info: https://guides.iiif.io/guide_for_implementers/#viewers-and-site-integration
Branch: feature/iiif
Files
- Start date changed from 2023-09-14 to 2022-12-09
- Follows Feature #1909: IIIF image API server added
- Subject changed from OpenAtlas IIIF client integration to IIIF client integration
- Subject changed from IIIF client integration to IIIF viewer integration
- Description updated (diff)
- Description updated (diff)
- Start date changed from 2022-12-09 to 2023-09-18
ColverIIIF looks promising. It looks lightweight and easy to install/use. And it has a size that can be nicely integrated in the user interface.
It can be used as Vanilla JS, React or Next.js as far as I understood.
- Assignee changed from Moritz Großfurtner to Bernhard Koschiček-Krombholz
Assigning it back to me. Mocca has other things to handle.
I made a proof of concept for the IIIF viewer with Mirador:
If you want to try, please follow IIIF install instructions. Then checkout feature/iiif and reinstall the node modules (following upgrade.md).
- Status changed from In Progress to Closed
- Category changed from UI to IIIF
Also available in: Atom
PDF
Updated by 
Updated by