Difference between revisions of "Workflow:Workflow for ingesting internally-generated material"

From COPTR
Jump to navigation Jump to search
Line 12: Line 12:
  
 
<!--  
 
<!--  
* Internal teams deposit material in pre-agreed formats via hard drives or file transfer services
+
* Internal teams deposit assets in pre-agreed formats via hard drives or file transfer services
* Digital Archive staff load the material and run manualquality assurance checks, focussing on naming conventions, descriptive and searchable metadata and copyright
+
* Digital Archive staff load the assets and run manual quality assurance checks, focussing on naming conventions, descriptive and searchable metadata and copyright
* The material is loaded onto the Archive cloud server, which has a mirrored server in a separate geographical location
+
* 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-->
+
* 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-->
  
 
==Purpose, Context and Content==
 
==Purpose, Context and Content==

Revision as of 13:52, 28 April 2021

Workflow for ingesting internally-generated material
Status:Production
Input:.tiff - born digital images or scans of physical material or .tiff & .dwg & .pdf
Organisation:Historic England

Workflow Description

Textual description


Purpose, Context and Content

Evaluation/Review

Further Information