Editing Workflow:Cloud-based preservation and access workflow for MXF and MPG video
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 36: | Line 36: | ||
#* creating a bag | #* creating a bag | ||
# The bag is sent to the Wellcome Storage Service where it is verified and stored. The .mxf files are automatically life cycled to Glacier Deep Store. The storage sends a callback to Goobi to verify the bag has been stored successfully | # The bag is sent to the Wellcome Storage Service where it is verified and stored. The .mxf files are automatically life cycled to Glacier Deep Store. The storage sends a callback to Goobi to verify the bag has been stored successfully | ||
− | # When Goobi gets the call back, it calls the DDS API. DDS | + | # When Goobi gets the call back, it calls the DDS API. DDS then reads the METS in storage and starts writing a IIIF manifest while DLCS begins making an access copy of the high res MP4 or MPG |
# When the IIIF manifest and access copies are ready, wellcomecollection.org/collection starts displaying the video | # When the IIIF manifest and access copies are ready, wellcomecollection.org/collection starts displaying the video | ||