Ablewer at 20:13, 11 December 2019

2019-12-11T20:13:40Z

Courtney: /* Transfer */

2014-04-28T18:39:36Z

Transfer

Courtney: Created page with "Main Page > Documentation > Technical Architecture > Micro-services > Archivematica 1.1 Micro-services A micro-service may consist of a number of discrete tas..."

2014-04-28T18:35:07Z

Created page with "Main Page > Documentation > Technical Architecture > Micro-services > Archivematica 1.1 Micro-services A micro-service may consist of a number of discrete tas..."

New page

[[Main Page]] > [[Documentation]] > [[Technical Architecture]] > [[Micro-services]] > Archivematica 1.1 Micro-services

A micro-service may consist of a number of discrete tasks, or jobs. In the Archivematica 1.1 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).

</br>

[[Image:Micro-services1.png|600px|center|thumb|Archivematica dashboard showing a micro-service and its jobs]]

</br>

The table below shows micro-services and jobs in Archivematica 1.1. Note that this is is only a list of micro-services; detailed user instructions are available in the [[User manual 1.0|user manual]].
</br>
=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>
| This is the approval step that moves the transfer into the Archivematica processing pipeline.
|-
| <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: (Standard, Zipped bag, Unzipped bag, DSpace, Maildir)
<br/>Remove hidden files and directories
<br/>Remove unneeded files
<br/>Attempt restructure for compliance
<br/>Verify transfer compliance
<br/>Verify mets_structmap.xml compliance
</div>
</div>
| 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/''.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Rename with transfer UUID'''<div class="mw-collapsible-content">
<br/>Rename with transfer UUID
</div>
</div>
| Directly associates the transfer with its 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>
| 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.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Assign file UUIDs and checksums'''<div class="mw-collapsible-content">
<br/>Set file permissions
<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 and sets file permission to allow for continued processing.
|-
| <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 transfer prior to moving the transfer into Archivematica.
|-
| <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 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.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Quarantine'''<div class="mw-collapsible-content">
<br/>Workflow decision - send transfer to quarantine
<br/>Move to quarantine
<br/>Remove from quarantine
</div>
</div>
| Quarantine's the transfer for a set duration, to allow virus definitions to update, before virus scan.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Scan for viruses'''<div class="mw-collapsible-content">
<br/>Scan for viruses
</div>
</div>
| 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.
|-
| <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">'''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">
<br/>Characterize and extract metadata
<br/>Load labels from metadata/file_labels.csv
<br/>Set file permissions
<br/>Check for specialized processing
</div>
</div>
| 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">
<br/>Index transfer contents
<br/>Move to SIP creation directory for completed transfers
</div>
</div>
| 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">
<br/>Check transfer directory for objects
<br/>Load options to create SIPs
<br/>Create SIP(s)
<br/>Move to processing directory
<br/>Create SIP from transfer objects
<br/>Send transfer to backlog
<br/>Move to SIP creation directory for completed transfers
</div>
</div>
| 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.
|-
|}
</br>

=Ingest=
{| 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">'''Verify SIP compliance'''<div class="mw-collapsible-content">
<br/>Set file permissions
<br/>Move to processing directory
<br/>Verify SIP compliance
</div>
</div>
| Verifies that the SIP conforms to the folder structure required for processing in Archivematica. The structure is as follows: ''/logs/'', ''/metadata/'', ''/metadata/submissionDocumentation/'', ''/objects/''.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Verify transfer compliance'''<div class="mw-collapsible-content">
<br/>Verify mets_structmap.xml compliance
</div>
</div>
| Verifies the METS from the transfer.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Rename SIP directory with SIP UUID'''<div class="mw-collapsible-content">
<br/>Rename SIP directory with SIP UUID
<br/>Check if SIP is from Maildir Transfer
</div>
</div>
| 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.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Include default SIP processingMCP.xml'''<div class="mw-collapsible-content">
<br/>Include default SIP processingMCP.xml
</div>
</div>
| Copies the processing configuration file added to the transfer in '''Include default Transfer processingMCP.xml''', above, to the SIP.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Remove cache files'''<div class="mw-collapsible-content">
<br/>Remove cache files
</div>
</div>
| Removes any thumbs.db files.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Clean up names'''<div class="mw-collapsible-content">
<br/>Sanitize SIP name
<br/>Set file permissions
</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">'''Normalize'''<div class="mw-collapsible-content">
<br/>Identify manually normalized files
<br/>Check for Service directory
<br/>Check for Access directory
<br/>Set remove preservation and access normalized files to renormalize link.
<br/>Grant normalization options for no pre-existing DIP
<br/>Move to workFlowDecisions-createDip directory
<br/>Find options to normalize as
<br/>Set resume link after tool selected
<br/>Move to select file ID tool
<br/>Select pre-normalize file format identification commant
<br/>Identify file format
<br/>Resume after normalization file identification tool selected
<br/>Normalize
<br/>Move to processing directory
<br/>Create DIP directory
<br/>Create thumbnails directory
<br/>Normalize thumbnails
<br/>Normalize access
<br/>Normalize preservation
<br/>Set file permissions
<br/>Remove files without linking information (failed normalization artifacts etc.)
<br/>Move to approve normalization directory
<br/>Approve normalization
<br/>Load post approve normalization link
<br/>Set resume link after handling any manually normalized files
<br/>Move to processing directory
<br/>Set file permissions
<br/>Check for manually normalized files
<br/>Load finished with manual normalized link
</div>
</div>
| 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.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Process submission documentation'''<div class="mw-collapsible-content">
<br/>Copy transfer submission documentation
<br/>Check for submission documentation
<br/>Move submission documentation into objects directory
<br/>Assign file UUIDs to submission documentation
<br/>Assign checksums and file sizes to submissionDocumentation
<br/>Sanitize file and directory names in submission documentation
<br/>Scan for viruses in submission documentation
<br/>Characterize and extract metadata on submission documentation
</div>
</div>
| Processes any submission documentation included in the SIP and adds it to the ''/objects/'' directory.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Process metadata directory'''<div class="mw-collapsible-content">
<br/>Set resume link after processing metadata directory
<br/>Move metadata to objects directory
<br/>Assign file UUIDs to metadata
<br/>Assign checksums and file sized to metadata
<br/>Sanitize file and directory names in metadata
<br/>GScan for viruses in metadata
<br/>Load finished with metadata processing link
</div>
</div>
| Processes metadata.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Prepare DIP'''<div class="mw-collapsible-content">
<br/>Copy thumbnails to DIP directory
<br/>Copy METS to DIP directory
<br/>Set file permissions
<br/>Generate DIP
</div>
</div>
| Creates a DIP containing access copies of the objects, thumbnails and a copy of the METS file.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Upload DIP'''<div class="mw-collapsible-content">
<br/>Upload DIP
</div>
</div>
| Allows the user to choose to upload the DIP to either ICA-AtoM or CONTENTdm.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Upload DIP to ICA-AtoM'''<div class="mw-collapsible-content">
<br/>Upload DIP
<br/>Move to the uploadedDIPs directory
</div>
</div>
| The user uploads the DIP to a selected description in ICA-AtoM.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Upload DIP to CONTENTdm'''<div class="mw-collapsible-content">
<br/>Restructure DIP for CONTENTdm upload
<br/>Select upload type (Project Client or direct upload)
<br/>Select target CONTENTdm server
<br/>Get list of collections on server
<br/>Select destination collection
<br/>Upload DIP to contentDM
<br/>Move to the uploadedDIPs directory
</div>
</div>
| The user uploads the DIP to a selected description in CONTENTdm.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Prepare AIP'''<div class="mw-collapsible-content">
<br/>Remove files without linking information (failed normalization artifacts, etc.)
<br/>Verify checksums generated on ingest
<br/>Copy transfers metadata and logs
<br/>Remove empty manual normalization directories
<br/>Generate METS.xml document
<br/>Index AIP contents
<br/>Prepare AIP
<br/>Move to compressionAIPDecisions directory
<br/>Select compression algorithm
<br/>Select compression level
<br/>Compress AIP
<br/>Create AIP pointer file
<br/>Set bag file permissions
<br/>Removed bagged files
</div>
</div>
| Creates an AIP in Bagit format. Creates the AIP pointer file. Indexes the AIP, then losslessly compresses it.
|-
| <div class="toccolours mw-collapsible mw-collapsed">'''Store AIP'''<div class="mw-collapsible-content">
<br/>Move to the store AIP approval directory
<br/>Store AIP
<br/>Retrieve AIP Storage Locations
<br/>Store AIP location
<br/>Move to processing directory
<br/>Verify AIP
<br/>Store the AIP
<br/>Index AIP
<br/>Remove processing directory
</div>
</div>
| 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.
|-
|}

← Older revision		Revision as of 20:13, 11 December 2019
Line 1:		Line 1:
	[[Main Page]] > [[Documentation]] > [[Technical Architecture]] > [[Micro-services]] > Archivematica 1.1 Micro-services		[[Main Page]] > [[Documentation]] > [[Technical Architecture]] > [[Micro-services]] > Archivematica 1.1 Micro-services
		+
		+	<blockquote style="background-color:orange;">
		+	'''Note: The documentation on this page is out of date. Please see the [https://www.archivematica.org/docs official documentation page] for the latest.'''
		+	</blockquote>

	A micro-service may consist of a number of discrete tasks, or jobs. In the Archivematica 1.1 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).		A micro-service may consist of a number of discrete tasks, or jobs. In the Archivematica 1.1 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).

@@ Line 101: / Line 101: @@
 |-
 |  <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.
+| 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.
 |-

Archivematica 1.1 Micro-services - Revision history

Ablewer at 20:13, 11 December 2019

Courtney: /* Transfer */

Courtney: Created page with "Main Page > Documentation > Technical Architecture > Micro-services > Archivematica 1.1 Micro-services A micro-service may consist of a number of discrete tas..."