UChicagoNode IIIF Workflow Detail

See also UChicagoNode Workflow Overview.

 1. a. CM creates a v1 manifest[1]
    b. MY tests it
    c. If OK
       then MY creates a test bag with one of these for b2a1b2c3d4e5 and sends to SG
         SG unpacks
         CB tests
         If OK
         then CM creates v1 manifests for all items in the collection

2. a. MY creates a complete set of bags, including v1 manifests, preservation files, and viewer access 
      files, and sends to SG
   b. SG unpacks one bag and gives CB the ARK ID
   c. CB tests the manifest (this is a belt and suspenders approach to manifest accuracy in case a 
      breaking change has inadvertently crept in)
   d. If OK
      then SG unpacks the rest of the bags and gives MA the ARK IDs and list of URLs constructed from 
      those ARK IDs for the-collection-name
        MA gives ODS the ARK IDs for the-collection-name when requested
        MA gives the constructed URLs from those ARK IDs to Technical Services for items cataloged in OCLC

3. a. Digitization creates v2 manifests using the descriptive metadata in OCHRE
   b. MY creates bags containing the v2 manifests and sends to SG
   c. SG unpacks the bags and deposits the v2 manifests
   d. SG communicates to MA that the process has been completed for that collection

4. MA gives ODS a green light for publication as far as this aspect of the workflow is concerned
   
[1] In OCFL the v1 manifest may or may not be in v1 of the pairtree. For new deposits, it will be. For
    existing deposits which lack manifests it will not be.

CB: Charles Blair (Director, Digital Library Development Center)
CM: Christina Miranda (Head of Digitization)
MA: Madeline Alft (UChicagoNode Project Manager)
ML: Molly Laumakis (UChicagoNode Data Migration Specialist)
MY: Matt Yang (Digital Preservation Specialist)
SG: Shawn Goodwin (Digital Repository Manager)
SS: Sandy Schloen (Manager, OCHRE Data Service)