Difference between revisions of "Workflows"

From Archivematica
Jump to navigation Jump to search
(Created page with '=(Default) workflow steps in Archivematica 0.7= {| border="1" cellpadding="10" cellspacing="0" width=90% |- |- style="background-color:#cccccc;" !style="width:25%"|'''Event (mos...')
 
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=(Default) workflow steps in Archivematica 0.7=
+
This page documents the default Archivematica workflows which are pre-configured for each installation. Alternate workflows can be defined using the [[MCP]] configuration files.
 +
 
 +
=1. Primary (default) Archivematica workflow=
 +
 
 +
The following steps represent a successful series of Archivematica workflow steps (i.e. without any errors). This "sunny day" workflow is derived from the orignal Archivematica [[UML_Activity_Diagrams|requirements]] and pre-1.0, pilot project findings.
  
 
{| border="1" cellpadding="10" cellspacing="0" width=90%
 
{| border="1" cellpadding="10" cellspacing="0" width=90%
Line 10: Line 14:
 
|Assign SIP UUID
 
|Assign SIP UUID
 
|This happens immediately after the SIP is dropped into Archivematica.
 
|This happens immediately after the SIP is dropped into Archivematica.
|ingestion
+
|receive SIP
 
|-
 
|-
 
|Verify SIP compliance
 
|Verify SIP compliance
Line 36: Line 40:
 
|Start quarantine
 
|Start quarantine
 
|
 
|
|start quarantine
+
|quarantine
 
|-
 
|-
 
|End quarantine
 
|End quarantine
 
|
 
|
|end quarantine
+
|unquarantine
 
|-
 
|-
 
|Unpackage
 
|Unpackage
Line 54: Line 58:
 
|Name sanitize
 
|Name sanitize
 
|A PREMIS event is generated only for those files that have had their names sanitized.
 
|A PREMIS event is generated only for those files that have had their names sanitized.
|remove prohibited characters
+
|name cleanup
 
|-
 
|-
 
|Virus scan
 
|Virus scan

Latest revision as of 13:32, 26 November 2010

This page documents the default Archivematica workflows which are pre-configured for each installation. Alternate workflows can be defined using the MCP configuration files.

1. Primary (default) Archivematica workflow[edit]

The following steps represent a successful series of Archivematica workflow steps (i.e. without any errors). This "sunny day" workflow is derived from the orignal Archivematica requirements and pre-1.0, pilot project findings.

Event (mostly in order of occurence) Description PREMIS event name
Assign SIP UUID This happens immediately after the SIP is dropped into Archivematica. receive SIP
Verify SIP compliance The SIP should have four directories: objects, logs/fileMeta, logs, metadata. We don't currently know when/how these directories are created. A pass/fail notification appears to the user. It does not form a PREMIS event. n/a
Assign file UUIDs/Generate checksums Note that checksums are assigned even if the objects arrive with checksums. See next step.
  • identifier assignment
  • message digest calculation
Verify checksum If the objects arrive with checksums they are verified at this point, but the checksums are not retained once they have been verified. The checksums generated in Assign file UUID/Generate checksums are kept instead. fixity check
Appraise SIP for submission This is a yes/no decision. If no, the SIP is deleted. If yes, the archivist can decide to keep the entire SIP or delete some of the files. n/a
Scan for deleted files This step identifies any files that are deleted during the Appraise SIP for submission step. A log of deleted files is saved to the logs directory. No PREMIS event is generated. n/a
Start quarantine quarantine
End quarantine unquarantine
Unpackage A PREMIS event is generated only for files that are unpackaged. unpackage
Assign file UUIDs/Generate checksums for unpackaged files
  • identifier assignment
  • message digest calculation
Name sanitize A PREMIS event is generated only for those files that have had their names sanitized. name cleanup
Virus scan Output is pass or fail. A PREMIS event is generated only for those files that pass the scan. virus check
File format identification format identification
File format validation format validation
Appraise SIP for Preservation This appraisal step is based on format identification and validation information provided by FITS tools. This is a yes/no decision. If no, the SIP is deleted. If yes, the archivist can decide to keep the entire SIP or delete some of the files. n/a
Scan for deleted files This step identifies any files that are deleted during the Appraise SIP for preservation step. A log of deleted files is saved to the logs directory. No PREMIS event is generated. n/a
Normalization normalization
Assign file UUIDs/Generate checksums for normalized files
  • identifier assignment
  • message digest calculation
Generation of access copy n/a
Review DIP n/a
Upload DIP to access system n/a
Store AIP n/a