Micro-service and job names

From Archivematica
Jump to navigation Jump to search

Main Page > Development > Development documentation > Micro-service and job names

This page is no longer being maintained and may contain inaccurate information. Please see the Archivematica documentation for up-to-date information.

Not all MCP modules should be identified as micro-services in the dashboard. For example, "Set file permissions" does not really constitute a micro-service. We should group jobs and tasks under the micro-services to which they belong; the dashboard would display only micro-services by default but the user could expand each micro-service to see the jobs and tasks associated with it, as shown in the following mock-up:


Here is a suggested list of micro-services:

  • Approve transfer
  • Verify transfer compliance
  • Assign file UUIDs and checksums
  • Verify transfer checksums
  • Generate METS.xml
  • Quarantine
  • Extract packages
  • Scan for viruses
  • Complete transfer
  • Approve SIP creation
  • Verify SIP compliance
  • Create SIP backup
  • Clean up names
  • Normalize
  • Approve normalization
  • Process submission documentation
  • Generate DIP
  • Upload DIP
  • Prepare AIP
  • Store AIP