search

wellcomecollection / platform

Wellcome Collection Digital Platform
https://developers.wellcomecollection.org/
MIT License
48 stars 10 forks source link

Exercising the new IIIF-Builder dashboard #4683

Closed tomcrane closed 4 years ago

tomcrane commented 4 years ago

Currently (Live = "old")

  1. Goobi calls the Live DDS
  2. Live DDS queues a workflow job
  3. Live WorkflowProcessor takes the job (starts to build packages, text)
  4. Live WorkflowProcessor queues a DlcsProcessorJob
  5. Live DlcsProcessor takes the job (synchronises METS-view with DLCS)

Proposal - Test Phase

Add Step 1a: Live DDS calls iiif-test.wellcomecollection.org

The above runs exactly as-is on Live, and its twin runs on iiif-test, synchronising with space 6. We can then compare, at leisure, what the current system put into DLCS space 5 and what the new system put into DLCS space 6.

Proposal - PreLive phase

When we are satisfied with this (let it run for a good while), change step 1a to call new PRODUCTION iiif.wellcomecollection.org. Add a delay to the DlcsProcessorJob on Live (i.e., old), so that iiif.wc.org will do the sync first.

Goobi only needs to start calling iiif.wc.org directly when we are really going live (IIIF served from iiif.wc.org and not wl.org).

@aray-wellcome will still need to use the old dashboard for cachebusting, as the new one can't make changes to the old DDS. But if you are inspecting a sync issue, or image problems, you can use the new dashboard.

tomcrane commented 4 years ago

Also - add a link to the named query version of the manifest to both old and new dashboards. It means you can view a skeleton manifest for a work in the new dashboard, even though you can't see the iiif-builder manifest yet.

tomcrane commented 4 years ago

The first part of this and the comment above are done, will make a new issue to add to the backlog for the "PreLive Phase" proposal.