Currently, the synchronisation process between Goobi and DLCS that makes digitised items available online is part of DDS and runs 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 synchronisation processes from DDS into a standalone set of services that use our current approaches for deployment and authentication.
Objective
Better preservation of our digitised and born-digital collections
Measures
Is digitised content registered with DLCS in AWS?
Initiatives
Set up environment for local development and deployment
Deploy a working dashboard secured with Azure OIDC
Set up Goobi to DDS/DLCS workflow and job processing
jtweed
commented
4 years ago
Description
Currently, the synchronisation process between Goobi and DLCS that makes digitised items available online is part of DDS and runs 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 synchronisation processes from DDS into a standalone set of services that use our current approaches for deployment and authentication.
Objective
Better preservation of our digitised and born-digital collections
Measures
Initiatives
Set up environment for local development and deployment
Deploy a working dashboard secured with Azure OIDC
Set up Goobi to DDS/DLCS workflow and job processing