Difference between revisions of "Micro-services"

From Archivematica
Jump to navigation Jump to search
Line 10: Line 10:
 
In early iterations of the Archivematica system, some of the workflow controls (e.g. event triggering, error reporting, etc.) are handled via the Thunar file manager (e.g. drag-and-drop, desktop notifications). As the system approaches beta maturity all of the micro-services workflow will be managed via a web-based [[Dashboard]] application.
 
In early iterations of the Archivematica system, some of the workflow controls (e.g. event triggering, error reporting, etc.) are handled via the Thunar file manager (e.g. drag-and-drop, desktop notifications). As the system approaches beta maturity all of the micro-services workflow will be managed via a web-based [[Dashboard]] application.
  
==Archivematica Micro-services==
+
==Archivematica Micro-services=
 
 
[[File:Archivematica-architecture-7May2010-2.png|thumb|right|600px|Archivematica architecture - May 2010]]
 
  
 
{| border="1" cellpadding="10" cellspacing="0" width=40%
 
{| border="1" cellpadding="10" cellspacing="0" width=40%

Revision as of 10:24, 11 May 2010

Main Page > Overview > Micro-services

The Archivematica micro-services are based on the project's use case and workflow analysis of the ISO-OAIS functional model. Each service is available to a conceptual entity that is equivalent to an OAIS information package:

  • Submission Information Package (SIP)
  • Archival Information Package (AIP)
  • Dissemination Information Package (DIP)

These packages are moved from one service to the next using the Unix pipeline design pattern implemented with a combination of Bash and Python scripts. Each service is provided by one or more of the open-source software utilities and applications bundled in the Archivematica system.

In early iterations of the Archivematica system, some of the workflow controls (e.g. event triggering, error reporting, etc.) are handled via the Thunar file manager (e.g. drag-and-drop, desktop notifications). As the system approaches beta maturity all of the micro-services workflow will be managed via a web-based Dashboard application.

=Archivematica Micro-services

Category Micro-service
receiveSIP
  • verifyChecksum
reviewSIP
  • extractPackage
  • assignIdentifier
  • parseManifest
  • cleanFilename
quarantineSIP
  • lockAccess
  • virusCheck
appraiseSIP
  • identifyFormat
  • validateFormat
  • extractMetadata
  • decidePreservationAction
prepareAIP
  • gatherMetadata
  • normalizeFiles
  • createPackage
reviewAIP
  • decideStorageAction
storeAIP
  • writePackage
  • replicatePackage
  • auditFixity
  • readPackage
  • updatePackage
provideDIP
  • uploadPackage
  • updateMetadata
monitorPreservation
  • updatePolicy
  • migrateFormat