To edit this page, please answer the question that appears below (more info):
What short name does OAIS use for an information package that is used for submission?
Free text:
==Workflow Description== <!-- To add an image of your workflow, open the "Upload File" link on the left in a new browser tab and follow on screen instructions, then return to this page and add the name of your uploaded image to the line below - replacing "workflow.png" with the name of your file. Replace the text "Textual description" with a short description of your image. Filenames are case sensitive! If you don't want to add a workflow diagram or other image, delete the line below --> [[File:workflow.png|Textual description]]<br> <!-- --> ==Purpose, Context and Content== <!-- Describe what your workflow is for - i.e. what it is designed to achieve, what the organisational context of the workflow is, and what content it is designed to work with --> ==Evaluation/Review== <!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate --> ==Further Information== <!-- Provide any further information or links to additional documentation here * Internal teams deposit assets in pre-agreed formats via hard drives or file transfer services * Digital Archive staff load the assets and run manual quality assurance checks, focussing on naming conventions, descriptive and searchable metadata and copyright * The assets are loaded onto the Archive cloud server, which has a mirrored server in a separate geographical location * Digital Archive staff manually create two backups of the material from the cloud server * Staff sync the assets from the cloud server to our DAMS, Portfolio, where internal users can search and view assets--> <!-- Add four tildes below ("~~~~") to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow --> <!-- Note that your workflow will be marked with a CC3.0 licence -->