Micro-service and job names - Revision history

Sallain at 21:57, 11 February 2020

2020-02-11T21:57:45Z

Evelyn at 18:36, 23 September 2011

2011-09-23T18:36:09Z

Evelyn at 18:31, 23 September 2011

2011-09-23T18:31:19Z

Evelyn: Created page with 'Main Page > Development > Development documentation > Reporting Here is a suggested list of micro-services (this is very flexible...'

2011-09-23T18:26:59Z

Created page with 'Main Page > Development > Development documentation > Reporting Here is a suggested list of micro-services (this is very flexible...'

New page

[[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > Reporting

Here is a suggested list of micro-services (this is very flexible at this point)

*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

[[Category:Development documentation]]

← Older revision		Revision as of 21:57, 11 February 2020
Line 1:		Line 1:
	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > Micro-service and job names		[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > Micro-service and job names
		+
		+	<div style="padding: 10px 10px; border: 1px solid black; background-color: #F79086;">This page is no longer being maintained and may contain inaccurate information. Please see the [https://www.archivematica.org/docs/latest/ Archivematica documentation] for up-to-date information. </div> <p>

	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:		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:

@@ Line 1: / Line 1: @@
 [[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > Micro-service and job names
-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.
+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

← Older revision		Revision as of 18:31, 23 September 2011
Line 1:		Line 1:
−	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > ~~Reporting~~	+	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > Micro-service and job names
		+
		+	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.
		+
		+

	Here is a suggested list of micro-services (this is very flexible at this point)		Here is a suggested list of micro-services (this is very flexible at this point)