Difference between revisions of "Archivematica 0.9 Micro-services"
(→Ingest) |
|||
Line 1: | Line 1: | ||
+ | [[Main Page]] > [[Documentation]] > [[Technical Architecture]] > [[Micro-services]] > Archivematica 0.9 Micro-services | ||
+ | |||
+ | =Transfer= | ||
+ | {| border="1" cellpadding="10" cellspacing="0" width=90% | ||
+ | |- | ||
+ | |- style="background-color:#cccccc;" | ||
+ | !style="width:30%"|'''Micro-service''' | ||
+ | !style="width:70%"|'''Description''' | ||
+ | |- | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Approve Transfer'''<div class="mw-collapsible-content"> | ||
+ | Set file permissions | ||
+ | </div> | ||
+ | </div> | ||
+ | | Once the transfer has all its digital objects and has been formatted for processing, the user selects "Transfer complete" from the Actions drop-down menu. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Verify transfer compliance'''<div class="mw-collapsible-content"> | ||
+ | <br/>Set file permissions | ||
+ | <br/>Move to processing directory | ||
+ | <br/>Set transfer type | ||
+ | <br/>Remove hidden files and directories | ||
+ | <br/>Attempt restructure for compliance | ||
+ | <br/>Verify transfer compliance | ||
+ | </div> | ||
+ | </div> | ||
+ | | Verifies that the transfer conforms to the folder structure required for processing in Archivematica. The structure is as follows: /logs/, /metadata/, /metadata/submissionDocumentation/, /objects/. Standard transfers are restructured for compliance if pessary. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Rename with transfer UUID'''<div class="mw-collapsible-content"> | ||
+ | <br/>Rename with transfer UUID | ||
+ | </div> | ||
+ | </div> | ||
+ | | Directly associate the transfer with it's metadata by appending the transfer UUID to the transfer directory name. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Include default Transfer processingMCP.xml'''<div class="mw-collapsible-content"> | ||
+ | <br/>Include default Transfer processingMCP.xml | ||
+ | </div> | ||
+ | </div> | ||
+ | | Includes a file named [[processingMCP.xml]] in the root of the transfer. This is a configurable xml file to pre-configure processing decisions. It can configure workflow options such as creating transfer backups, quarantining the transfer and selecting a SIP creation option. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Assign file UUIDs and checksums'''<div class="mw-collapsible-content"> | ||
+ | <br/>Assign file UUIDs to objects | ||
+ | <br/>Assign checksums and file sizes to objects | ||
+ | </div> | ||
+ | </div> | ||
+ | | Assigns a unique universal identifier and sha-256 checksum to each file in the /objects/ directory. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Verify transfer checksums'''<div class="mw-collapsible-content"> | ||
+ | <br/>Verify metadata directory checksums | ||
+ | </div> | ||
+ | </div> | ||
+ | | Checks any checksum files that were placed in the /metadata/ folder of the SIP prior to ingest. Note that the filenames need to be named based on their algorithm: checksum.sha1, checksum.sha256, checksum.md5. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Generate METS.xml document'''<div class="mw-collapsible-content"> | ||
+ | <br/>Generate METS.xml document | ||
+ | </div> | ||
+ | </div> | ||
+ | | Generates a basic mets file with a fileSec and structMap to record the presence of all objects in the /objects/ directory and their location in any subdirectories. Designed to capture the original order of the transfer in the event the user chooses subsequently to delete, rename or move files or break the transfer into multiple SIPs. The mets file is automatically added to any SIP generated from the transfer. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Extract packages'''<div class="mw-collapsible-content"> | ||
+ | <br/>Extract packages | ||
+ | <br/>Extract attachments | ||
+ | </div> | ||
+ | </div> | ||
+ | | Extracts objects from any zipped files or other packages. Extracts attachments from maildir transfers. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Scan for viruses'''<div class="mw-collapsible-content"> | ||
+ | <br/>Scan for viruses | ||
+ | </div> | ||
+ | </div> | ||
+ | | Uses ClamAV, parses the output and creates a PREMIS event. If a virus is found, the SIP is automatically placed in /sharedDirectoryStructure/failed/. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Clean up names'''<div class="mw-collapsible-content"> | ||
+ | <br/>Sanitize object's file and directory names | ||
+ | <br/>Sanitize Transfer name | ||
+ | </div> | ||
+ | </div> | ||
+ | | Some file systems do not support unicode or other special characters in filenames. This micro-service removes prohibited characters and replaces them with dashes. Original filenames are preserved in the PREMIS metadata. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Characterize and extract metadata'''<div class="mw-collapsible-content"> | ||
+ | <br/>Characterize and extract metadata | ||
+ | <br/>Identify Files ByExtension | ||
+ | <br/>Load labels from metadata/file_labels.csv | ||
+ | </div> | ||
+ | </div> | ||
+ | | Identifies and validates formats and extracts object metadata using the File Information Tool Set (FITS). Adds output to the PREMIS metadata. Also identities file extensions, these identifications are used for normalization. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Complete transfer'''<div class="mw-collapsible-content"> | ||
+ | <br/>Index transfer contents | ||
+ | <br/>Set file permissions | ||
+ | <br/>Move to completedTransfers directory | ||
+ | </div> | ||
+ | </div> | ||
+ | | Index transfer contents, before marking the transfer as complete. | ||
+ | |- | ||
+ | | <div class="toccolours mw-collapsible mw-collapsed">'''Create SIP from Transfer'''<div class="mw-collapsible-content"> | ||
+ | <br/>Check transfer directory for objects | ||
+ | <br/>Create SIP(s) | ||
+ | <br/>Create SIP from transfer objects | ||
+ | </div> | ||
+ | </div> | ||
+ | | The user chooses among a number of SIP creation options. See the user manual for details. | ||
+ | |- | ||
+ | |} | ||
+ | |||
=Ingest= | =Ingest= | ||
{| border="1" cellpadding="10" cellspacing="0" width=90% | {| border="1" cellpadding="10" cellspacing="0" width=90% |
Revision as of 12:19, 27 August 2012
Main Page > Documentation > Technical Architecture > Micro-services > Archivematica 0.9 Micro-services
Transfer
Micro-service | Description |
---|---|
Approve Transfer
Set file permissions |
Once the transfer has all its digital objects and has been formatted for processing, the user selects "Transfer complete" from the Actions drop-down menu. |
Verify transfer compliance
|
Verifies that the transfer conforms to the folder structure required for processing in Archivematica. The structure is as follows: /logs/, /metadata/, /metadata/submissionDocumentation/, /objects/. Standard transfers are restructured for compliance if pessary. |
Rename with transfer UUID
|
Directly associate the transfer with it's metadata by appending the transfer UUID to the transfer directory name. |
Include default Transfer processingMCP.xml
|
Includes a file named processingMCP.xml in the root of the transfer. This is a configurable xml file to pre-configure processing decisions. It can configure workflow options such as creating transfer backups, quarantining the transfer and selecting a SIP creation option. |
Assign file UUIDs and checksums
|
Assigns a unique universal identifier and sha-256 checksum to each file in the /objects/ directory. |
Verify transfer checksums
|
Checks any checksum files that were placed in the /metadata/ folder of the SIP prior to ingest. Note that the filenames need to be named based on their algorithm: checksum.sha1, checksum.sha256, checksum.md5. |
Generate METS.xml document
|
Generates a basic mets file with a fileSec and structMap to record the presence of all objects in the /objects/ directory and their location in any subdirectories. Designed to capture the original order of the transfer in the event the user chooses subsequently to delete, rename or move files or break the transfer into multiple SIPs. The mets file is automatically added to any SIP generated from the transfer. |
Extract packages
|
Extracts objects from any zipped files or other packages. Extracts attachments from maildir transfers. |
Scan for viruses
|
Uses ClamAV, parses the output and creates a PREMIS event. If a virus is found, the SIP is automatically placed in /sharedDirectoryStructure/failed/. |
Clean up names
|
Some file systems do not support unicode or other special characters in filenames. This micro-service removes prohibited characters and replaces them with dashes. Original filenames are preserved in the PREMIS metadata. |
Characterize and extract metadata
|
Identifies and validates formats and extracts object metadata using the File Information Tool Set (FITS). Adds output to the PREMIS metadata. Also identities file extensions, these identifications are used for normalization. |
Complete transfer
|
Index transfer contents, before marking the transfer as complete. |
Create SIP from Transfer
|
The user chooses among a number of SIP creation options. See the user manual for details. |
Ingest
Micro-service | Description |
---|---|
Verify SIP compliance
|
Verifies that the SIP conforms to the folder structure required for processing in Archivematica. The structure is as follows: /logs/, /metadata/, /metadata/submissionDocumentation/, /objects/. |
Include default SIP processingMCP.xml
|
Includes a file named processingMCP.xml in the root of the transfer. This is a configurable xml file to pre-configure processing decisions. It can configure workflow options such as creating transfer backups, quarantining the transfer and selecting a SIP creation option. |
Remove cache files
|
Removes any Thumbs.db files |
Normalize
|
Determins which normalization options are available for the SIP and presents them to the user as choices. Normalizes based on selection.
If desired, the user can verify the quality of normalized files in /sharedDirectoryStructure/watchedDirectories/approveNormalization/. |
Process submission documentation
|
|
Prepare DIP
|
Create the DIP with copies of the METS file, and thumbnails. Moves the DIP to the upload DIP watched directory. |
Prepare AIP
|
Create an AIP in Bagit format. Index the AIP, then losslessly compress it. |
Store AIP
|
Moves the AIP to a specified directory. In the demo version of Archivematica the directory is /sharedDirectoryStructure/www/AIPsStore/. In other environments it can be a remote network mounted directory. The directory structure of the AIP store contains UUID quad directories and an index.html file listing the AIPs in storage. The index.html file is displayed in the dashboard in the Archival storage tab.
Once the AIP has been stored, a copy of the AIP is extracted from storage to a local temp directory, and is validated with the various BagIt checks: verifyvalid, checkpayloadoxum, verifycomplete, verifypayloadmanifests, verifytagmanifests. |
Upload DIP to contentDM
|
It is now possible to upload to ContentDM. |
Upload DIP to ICA-Atom
|
The user uploads the DIP to a selected description in the access system. See the user manual for details. |