Difference between revisions of "Micro-services"
| Line 43: | Line 43: | ||
#*readPackage | #*readPackage | ||
#*updatePackage | #*updatePackage | ||
| + | #monitorPreservation | ||
| + | #*triggerPreservationAction | ||
#provideDIP | #provideDIP | ||
#*uploadPackage | #*uploadPackage | ||
#*updateMetadata | #*updateMetadata | ||
| − | + | ||
| − | |||
|style="padding: 0.5em 1em 1em; color: rgb(0, 0, 0);"| | |style="padding: 0.5em 1em 1em; color: rgb(0, 0, 0);"| | ||
Revision as of 22:25, 30 April 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
|
