Micro-services
Main Page > Documentation > Technical Architecture > Micro-services
Archivematica implements a micro-service approach to digital preservation. The Archivematica micro-services are granular system tasks which operate on a conceptual entity that is equivalent to an OAIS information package: Submission Information Package (SIP), Archival Information Package (AIP), Dissemination Information Package (DIP). The physical structure of an information package will include files, checksums, logs, submission documentation, XML metadata, etc..
These information packages are processed using a series of micro-services. Micro-services are provided by a combination of Archivematica Python scripts and one or more of the free, open-source software tools bundled in the Archivematica system. Each micro-service results in a success or error state and the information package is processed accordingly by the next micro-service. There are a variety of mechanisms used to connect the various micro-services together into complex, custom workflows. Resulting in a complete ingest to access system.
Archivematica implements a default ingest to access workflow that is compliant with the ISO-OAIS functional model. Micro-services can be distributed to processing clusters for highly scalable configurations.
Current Micro-services in Archivematica[edit]
A micro-service may consist of a number of discrete tasks, or jobs. In the Archivematica 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).
The table below shows micro-services and jobs in the current release of Archivematica (Updated July 2015 for release 1.4.1).
Transfer[edit]
Micro-service | Description |
---|---|
ExpandApprove Transfer
|
This is the approval step that moves the transfer into the Archivematica processing pipeline. |
ExpandVerify 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/. |
ExpandRename with transfer UUID
|
Directly associates the transfer with its metadata by appending the transfer UUID to the transfer directory name. |
ExpandInclude 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. |
ExpandAssign 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. |
ExpandVerify transfer checksums
|
Checks any checksum files that were placed in the /metadata/ folder of the transfer prior to moving the transfer into Archivematica. |
ExpandGenerate 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. |
ExpandReformat metadata files
|
Transforms JSON metadata included with transfer to metadata.csv |
ExpandQuarantine
|
Quarantines the transfer for a set duration, to allow virus definitions to update, before virus scan. |
ExpandScan 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. |
ExpandGenerate transfer structure report
|
Uses Tree to create transfer structure report (original order report) in txt format |
ExpandClean 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. |
ExpandIdentify 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. |
ExpandExtract packages
|
Extracts objects from any zipped files or other packages. Extracts attachments from maildir transfers. User can preconfigure choices about whether to extract and whether to keep one or both of extracted object contents and/or the package itself. |
ExpandUpdate METS.xml document
|
Creates a structMap in the transfer METS to reflect structure of transfer |
ExpandCharacterize and extract metadata
|
Characterizes formats and extracts object metadata using File Information Tool Set (FITS), FFprobe, Exiftool and/or Mediainfo |
ExpandValidation
|
Validates formats using JHOVE. |
ExpandExamine Contents
|
Runs Bulk Extractor on transfer contents and creates reports |
ExpandComplete transfer
|
Indexes transfer contents, creates transfer METS XML, then marks the transfer as complete. |
ExpandCreate 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, which creates an associated PREMIS event. |
Ingest[edit]
Micro-service | Description |
---|---|
ExpandApprove SIP creation
|
Applies to SIPs that have been created from backlog. Approves creation of SIP, and creates PREMIS event for removal from backlog. |
ExpandVerify transfer compliance
|
Verifies the METS from the transfer. |
ExpandVerify 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/. |
ExpandRename SIP directory with SIP UUID
|
Directly associates the SIP with its metadata by appending the SIP UUID to the SIP directory name and checks if SIP is from Maildir transfer type to determine workflow. |
ExpandInclude default SIP processingMCP.xml
|
Copies the processing configuration file added to the transfer in Include default Transfer processingMCP.xml, above, to the SIP. |
ExpandRemove cache files
|
Removes any thumbs.db files. |
ExpandClean 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. |
ExpandNormalize
|
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. |
ExpandProcess manually normalized files
|
Processed files manually normalized during processing |
ExpandAdd final metadata
|
Provides the operator a reminder to add metadata through the UI if desired. |
ExpandTranscribe SIP contents
|
Runs Tesseract OCR tool on any JPG or TIFF image files in SIP. |
ExpandProcess submission documentation
|
Processes any submission documentation included in the SIP and adds it to the /objects/ directory. |
ExpandProcess metadata directory
|
Processes metadata. |
ExpandVerify checksums
|
Verifies checksums generated on ingest |
ExpandGenerate AIP METS
|
Generates Archivematica AIP METS.xml document |
ExpandPrepare DIP
|
Creates a DIP containing access copies of the objects, thumbnails and a copy of the METS file. |
ExpandPrepare AIP
|
Creates an AIP in Bagit format. Creates the AIP pointer file. Indexes the AIP, then losslessly compresses it. |
ExpandUpload DIP
|
Allows the user to choose to upload the DIP AtoM, CONTENTdm, Archivist's Toolkit. Also allows user to store DIP or reject DIP. |
ExpandUpload DIP to AtoM
|
The user uploads the DIP to a selected description in AtoM. |
ExpandUpload DIP to CONTENTdm
|
The user creates a DIP suitable for upload to CONTENTdm using Project Client. |
ExpandUpload DIP to Archivists' Toolkit
|
The user uploads the DIP metadata to Archivists' Toolkit |
ExpandStore DIP
|
The user stores the DIP in a location pre-configured in the Storage Service. |
ExpandStore AIP
|
Moves the AIP to /sharedDirectoryStructure/www/AIPsStore/ or another specified directory. Before the AIP has been stored, a copy of it is extracted to a local temp directory, where it is subjected to standard BagIt checks: verifyvalid, checkpayloadoxum, verifycomplete, verifypayloadmanifests, verifytagmanifests. |