Difference between revisions of "Archivematica 1.0 Micro-services"

From Archivematica
Jump to navigation Jump to search
(Created page with "Main Page > Documentation > Technical Architecture > Micro-services > Archivematica 1.0 Micro-services A micro-service may consist of a number of discrete tas...")
 
Line 77: Line 77:
 
</div>
 
</div>
 
| Quarantine's the transfer for a set duration, to allow virus definitions to update, before virus scan.
 
| Quarantine's the transfer for a set duration, to allow virus definitions to update, before virus scan.
|-
 
|  <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">
 
|  <div class="toccolours mw-collapsible mw-collapsed">'''Scan for viruses'''<div class="mw-collapsible-content">
Line 98: Line 91:
 
| 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.
 
| 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">'''Identify file format'''<div class="mw-collapsible-content">
 +
<br/>Move to select file ID tool
 +
<br/>Select file format identification command
 +
<br/>Determine which files to identify
 +
<br/> Identify file format
 +
</div>
 +
</div>
 +
| Identifies formats of the objects in the transfer using either FIDO or file extension based on user choice. Format types are managed in the Format Policy Registry. This micro-service can be skipped and done in Ingest instead.
 +
|-
 +
|  <div class="toccolours mw-collapsible mw-collapsed">'''Extract packages'''<div class="mw-collapsible-content">
 +
<br/>Extract contents from compressed archives
 +
</div>
 +
</div>
 +
| Extracts objects from any zipped files or other packages. Extracts attachments from maildir transfers.
 +
|-
 +
 
|  <div class="toccolours mw-collapsible mw-collapsed">'''Characterize and extract metadata'''<div class="mw-collapsible-content">
 
|  <div class="toccolours mw-collapsible mw-collapsed">'''Characterize and extract metadata'''<div class="mw-collapsible-content">
 
<br/>Characterize and extract metadata
 
<br/>Characterize and extract metadata
<br/>Identify Files ByExtension
 
 
<br/>Load labels from metadata/file_labels.csv
 
<br/>Load labels from metadata/file_labels.csv
 +
<br/>Set file permissions
 +
<br/>Check for specialized processing
 
</div>
 
</div>
 
</div>
 
</div>
| Identifies and validates formats and extracts object metadata using the File Information Tool Set (FITS). Also identifies file extensions, which are used for selecting normalization paths.
+
| Characterizes and validates formats and extracts object metadata using the File Information Tool Set (FITS).  
 
|-  
 
|-  
 
|  <div class="toccolours mw-collapsible mw-collapsed">'''Complete transfer'''<div class="mw-collapsible-content">
 
|  <div class="toccolours mw-collapsible mw-collapsed">'''Complete transfer'''<div class="mw-collapsible-content">
 
<br/>Index transfer contents
 
<br/>Index transfer contents
<br/>Set file permissions
+
<br/>Move to SIP creation directory for completed transfers
<br/>Move to completedTransfers directory
 
 
</div>
 
</div>
 
</div>
 
</div>
| Indexes transfer contents, then marks the transfer as complete.
+
| Indexes transfer contents, then marks the transfer as complete.  
 
|-  
 
|-  
 
|  <div class="toccolours mw-collapsible mw-collapsed">'''Create SIP from Transfer'''<div class="mw-collapsible-content">
 
|  <div class="toccolours mw-collapsible mw-collapsed">'''Create SIP from Transfer'''<div class="mw-collapsible-content">
 
<br/>Check transfer directory for objects
 
<br/>Check transfer directory for objects
 +
<br/>Load options to create SIPs
 
<br/>Create SIP(s)
 
<br/>Create SIP(s)
 +
<br/>Move to processing directory
 
<br/>Create SIP from transfer objects
 
<br/>Create SIP from transfer objects
 
<br/>Send transfer to backlog
 
<br/>Send transfer to backlog
 +
<br/>Move to SIP creation directory for completed transfers
 
</div>
 
</div>
 
</div>
 
</div>
| This is the approval step that moves the transfer to the SIP packaging micro-services (Ingest).
+
| This is the approval step that moves the transfer to the SIP packaging micro-services (Ingest) if user chooses to Create single SIP and continue processing. User can also choose to Send transfer to backlog at this time.
 
|-
 
|-
 
|}
 
|}

Revision as of 13:07, 6 February 2014

Main Page > Documentation > Technical Architecture > Micro-services > Archivematica 1.0 Micro-services

A micro-service may consist of a number of discrete tasks, or jobs. In the Archivematica 1.o dashboard, micro-services are always shown, while jobs may be viewed by expanding the micro-service (i.e. by clicking on the grey background behind the micro-service name).


Arhivematica dashboard showing a micro-service and its jobs


The table below shows micro-services and jobs in Archivematica 1.0. Note that this is is only a list of micro-services; detailed user instructions are available in the user manual.

Transfer

Micro-service Description
Approve Transfer
This is the approval step that moves the transfer into the Archivematica processing pipeline.
Verify transfer compliance
Moves the transfer to a processing directory based on selected transfer type (standard, zipped bag, unzipped bag, DSPace export or maildir). Verifies that the transfer conforms to the folder structure required for processing in Archivematica and restructures if required. The structure is as follows: /logs/, /metadata/, /metadata/submissionDocumentation/, /objects/.
Rename with transfer UUID
Directly associates the transfer with its metadata by appending the transfer UUID to the transfer directory name.
Include default Transfer processingMCP.xml
Adds a file named processingMCP.xml to 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 and sets file permission to allow for continued processing.
Verify transfer checksums
Checks any checksum files that were placed in the /metadata/ folder of the transfer prior to moving the transfer into Archivematica.
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 locations 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. A copy of the METS file is automatically added to any SIP generated from the transfer.
Quarantine
Quarantine's the transfer for a set duration, to allow virus definitions to update, before virus scan.
Scan for viruses
Uses ClamAV to scan for viruses and other malware. If a virus is found, the transfer is automatically placed in /sharedDirectoryStructure/failed/ and all processing on the transfer is stopped.
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.
Identify file format
Identifies formats of the objects in the transfer using either FIDO or file extension based on user choice. Format types are managed in the Format Policy Registry. This micro-service can be skipped and done in Ingest instead.
Extract packages
Extracts objects from any zipped files or other packages. Extracts attachments from maildir transfers.
Characterize and extract metadata
Characterizes and validates formats and extracts object metadata using the File Information Tool Set (FITS).
Complete transfer
Indexes transfer contents, then marks the transfer as complete.
Create SIP from Transfer
This is the approval step that moves the transfer to the SIP packaging micro-services (Ingest) if user chooses to Create single SIP and continue processing. User can also choose to Send transfer to backlog at this time.


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/.
Rename SIP directory with SIP UUID
Directly associates the SIP with its metadata by appending the SIP UUID to the SIP directory name.
Include default SIP processingMCP.xml
Copies the processing config file added to the transfer in Include default Transfer processingMCP.xml, above, to the SIP.
Remove cache files
Removes any Thumbs.db files.
Normalize
Determines which normalization options are available for the SIP and presents them to the user as choices. Normalizes (i.e. generates preservation and/or access copies) based on selection. Thumbnail files are also generated during this micro-service.
Process submission documentation
Processes any submission documentation included in the SIP and adds it to the /objects/ directory.
Prepare DIP
Creates a DIP containing access copies of the objects, thumbnails and a copy of the METS file.
Upload DIP
Allows the user to choose to upload the DIP to either ICA-AtoM or CONTENTdm.
Upload DIP to ICA-AtoM
The user uploads the DIP to a selected description in ICA-AtoM.
Upload DIP to CONTENTdm
The user uploads the DIP to a selected description in CONTENTdm.
Prepare AIP
Creates an AIP in Bagit format. Indexes the AIP, then losslessly compresses it.
Store AIP
Moves the AIP to /sharedDirectoryStructure/www/AIPsStore/ or another specified directory. Once the AIP has been stored, a copy of it is extracted from storage to a local temp directory, where it is subjected to standard BagIt checks: verifyvalid, checkpayloadoxum, verifycomplete, verifypayloadmanifests, verifytagmanifests.