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

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).

Archivematica dashboard showing a micro-service and its jobs

The table below shows micro-services and jobs in the current release of Archivematica (Updated July 2015 for release 1.4.1).

Transfer

Micro-service	Description
ExpandApprove Transfer	This is the approval step that moves the transfer into the Archivematica processing pipeline.
ExpandVerify transfer compliance Set file permissions Move to processing directory Set transfer type: (Standard, Zipped bag, Unzipped bag, DSpace, Maildir) Remove hidden files and directories Remove unneeded files Attempt restructure for compliance Verify transfer compliance Verify mets_structmap.xml 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 Rename 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 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.
ExpandAssign file UUIDs and checksums Set file permissions Assign file UUIDs to objects Assign checksums and file sizes to objects	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 Verify metadata directory 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 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.
ExpandReformat metadata files Process transfer JSON metadata	Transforms JSON metadata included with transfer to metadata.csv
ExpandQuarantine Workflow decision - send transfer to quarantine Move to quarantine Remove from quarantine	Quarantine's the transfer for a set duration, to allow virus definitions to update, before virus scan.
ExpandScan for viruses 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.
ExpandGenerate transfer structure report Generate transfer structure report Move to generate transfer tree	Uses Tree to create transfer structure report (original order report) in txt format
ExpandClean up names Sanitize object's file and directory names Sanitize Transfer name	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 Move to select file ID tool Select file format identification command Determine which files to identify 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.
ExpandExtract packages Move to processing directory Move to extract packages Extract packages? (preconfigured choice) Delete package after extraction? (preconfigured choice) Extract contents from compressed archives	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 Add processed structMap to METS.xml document	Creates a structMap in the transfer METS to reflect structure of transfer
ExpandCharacterize and extract metadata Characterize and extract metadata Load labels from metadata/file_labels.csv	Characterizes and validates formats and extracts object metadata using the File Information Tool Set (FITS).
ExpandValidation Validate formats	Validates formats and extracts object metadata using the File Information Tool Set (FITS).
ExpandComplete transfer Index transfer contents Move to SIP creation directory for completed transfers	Indexes transfer contents, then marks the transfer as complete.
ExpandCreate SIP from Transfer Check transfer directory for objects Load options to create SIPs Create SIP(s) Move to processing directory Create SIP from transfer objects Send transfer to backlog Move to SIP creation directory for completed transfers	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
ExpandVerify SIP compliance Set file permissions Move to processing directory 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/.
ExpandVerify transfer compliance Verify mets_structmap.xml compliance	Verifies the METS from the transfer.
ExpandRename SIP directory with SIP UUID Rename SIP directory with SIP UUID Check if SIP is from Maildir Transfer	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 Include 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 Remove cache files	Removes any thumbs.db files.
ExpandClean up names Sanitize SIP name Set file permissions	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 Identify manually normalized files Check for Service directory Check for Access directory Set remove preservation and access normalized files to renormalize link. Grant normalization options for no pre-existing DIP Move to workFlowDecisions-createDip directory Find options to normalize as Set resume link after tool selected Move to select file ID tool Select pre-normalize file format identification commant Identify file format Resume after normalization file identification tool selected Normalize Move to processing directory Create DIP directory Create thumbnails directory Normalize thumbnails Normalize access Normalize preservation Set file permissions Remove files without linking information (failed normalization artifacts etc.) Move to approve normalization directory Approve normalization Load post approve normalization link Set resume link after handling any manually normalized files Move to processing directory Set file permissions Check for manually normalized files Load finished with manual normalized link	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 submission documentation Copy transfer submission documentation Check for submission documentation Move submission documentation into objects directory Assign file UUIDs to submission documentation Assign checksums and file sizes to submissionDocumentation Sanitize file and directory names in submission documentation Scan for viruses in submission documentation Characterize and extract metadata on submission documentation	Processes any submission documentation included in the SIP and adds it to the /objects/ directory.
ExpandProcess metadata directory Set resume link after processing metadata directory Move metadata to objects directory Assign file UUIDs to metadata Assign checksums and file sized to metadata Sanitize file and directory names in metadata GScan for viruses in metadata Load finished with metadata processing link	Processes metadata.
ExpandPrepare DIP Copy thumbnails to DIP directory Copy METS to DIP directory Set file permissions Generate DIP	Creates a DIP containing access copies of the objects, thumbnails and a copy of the METS file.
ExpandUpload DIP Upload DIP	Allows the user to choose to upload the DIP to either ICA-AtoM or CONTENTdm.
ExpandUpload DIP to ICA-AtoM Upload DIP Move to the uploadedDIPs directory	The user uploads the DIP to a selected description in ICA-AtoM.
ExpandUpload DIP to CONTENTdm Restructure DIP for CONTENTdm upload Select upload type (Project Client or direct upload) Select target CONTENTdm server Get list of collections on server Select destination collection Upload DIP to contentDM Move to the uploadedDIPs directory	The user uploads the DIP to a selected description in CONTENTdm.
ExpandPrepare AIP Remove files without linking information (failed normalization artifacts, etc.) Verify checksums generated on ingest Copy transfers metadata and logs Remove empty manual normalization directories Generate METS.xml document Index AIP contents Prepare AIP Move to compressionAIPDecisions directory Select compression algorithm Select compression level Compress AIP Create AIP pointer file Set bag file permissions Removed bagged files	Creates an AIP in Bagit format. Creates the AIP pointer file. Indexes the AIP, then losslessly compresses it.
ExpandStore AIP Move to the store AIP approval directory Store AIP Retrieve AIP Storage Locations Store AIP location Move to processing directory Verify AIP Store the AIP Index AIP Remove processing directory	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.

Historical Micro-services in Archivematica Releases

• Archivematica 1.1 Micro-services
• Archivematica 1.0 Micro-services
• Archivematica 0.10 Micro-services
• Archivematica 0.9 Micro-services
• Archivematica 0.8 Micro-services
• Archivematica 0.7.1 Micro-services