Difference between revisions of "Workflows"
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...') |
|||
Line 1: | Line 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% |
Revision as of 14:20, 15 November 2010
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 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. | ingestion |
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. |
|
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 | start quarantine | |
End quarantine | end quarantine | |
Unpackage | A PREMIS event is generated only for files that are unpackaged. | unpackage |
Assign file UUIDs/Generate checksums for unpackaged files |
| |
Name sanitize | A PREMIS event is generated only for those files that have had their names sanitized. | remove prohibited characters |
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 |
| |
Generation of access copy | n/a | |
Review DIP | n/a | |
Upload DIP to access system | n/a | |
Store AIP | n/a |