Currently, our IIIF APIs and related APIs for full text content are part of DDS and run on-premises. As we will still be using these services after we decommission wellcomelibrary.org, they need to be migrated to AWS. We will extract the IIIF APIs from DDS, sourcing catalogue data from Catalogue API instead of directly from Sierra, and add support for IIIF v3.
Objective
Better preservation of our digitised and born-digital collections
Measures
Are all IIIF APIs migrated to AWS?
Is all digitised content, including AV, available?
Initiatives
End-to-end prototype providing JSON serialisation of METS
Support METS AV changes and new videos in DDS/DLCS
Produce IIIF v3 and v2.1 using the Catalogue API and METS
Fix the snapshot generator to enable IIIF rebuild
Add support for IIIF search and related text services
Set up Goobi to DDS/DLCS workflow and job processing
jtweed
commented
4 years ago
Description
Currently, our IIIF APIs and related APIs for full text content are part of DDS and run on-premises. As we will still be using these services after we decommission wellcomelibrary.org, they need to be migrated to AWS. We will extract the IIIF APIs from DDS, sourcing catalogue data from Catalogue API instead of directly from Sierra, and add support for IIIF v3.
Objective
Better preservation of our digitised and born-digital collections
Measures
Are all IIIF APIs migrated to AWS?
Is all digitised content, including AV, available?
Initiatives
End-to-end prototype providing JSON serialisation of METSSupport METS AV changes and new videos in DDS/DLCSProduce IIIF v3 and v2.1 using the Catalogue API and METSFix the snapshot generator to enable IIIF rebuildAdd support for IIIF search and related text servicesSet up Goobi to DDS/DLCS workflow and job processing