UM transfer 1.0 - Revision history

Evelyn at 18:48, 26 February 2014

2014-02-26T18:48:48Z

Courtney: /* Process the transfer */

2014-02-20T21:39:12Z

Process the transfer

Courtney: /* Create a transfer with submission documentation */

2014-02-20T20:59:49Z

Create a transfer with submission documentation

Courtney: /* Create a transfer with submission documentation */

2014-02-20T20:51:35Z

Create a transfer with submission documentation

Courtney: /* General description */

2014-02-19T23:27:56Z

General description

Courtney: /* Format identification */

2014-02-19T23:19:35Z

Format identification

Courtney at 23:02, 19 February 2014

2014-02-19T23:02:30Z

Courtney: /* Process the transfer */

2014-02-19T23:01:43Z

Process the transfer

Evelyn at 01:47, 18 February 2014

2014-02-18T01:47:23Z

Evelyn at 21:09, 17 February 2014

2014-02-17T21:09:28Z

@@ Line 73: / Line 73: @@
 #See [[UM ingest|Ingest]] for next steps.
 [[Image:CreateSIP1.png|600px|right|thumb|'''Figure 4'''  A transfer that is ready to be packaged into a SIP or stored in backlog]]
 == Format identification ==

@@ Line 52: / Line 52: @@
 #Click on the micro-service to display jobs that have completed, including the one requiring action.
 #In the Actions drop-down menu, select "Approve transfer" to begin processing the transfer ('''figure 3'''). You may also "Reject transfer" and quit processing.
-#The transfer will now run through a series of micro-services. These include:
+#The transfer will now run through a series of [[Archivematica_1.0_Micro-services|micro-services]]. These include:
 #*Verify transfer compliance (verifies that the transfer is properly structured - i.e. with the logs, metadata and objects folders)
-#*Create transfer UUID (assigns a unique universal identifier for the transfer as a whole)
+#*Rename with transfer UUID (assigns a unique universal identifier for the transfer as a whole; directly associates the transfer with its metadata)
-#*Assign file UUIDs to objects (assigns a unique universal identifier to each file in the /objects directory)
+#*Assign file UUIDs and checksums to objects (assigns a unique universal identifier and sha-256 checksum to each file in the /objects directory)
-#*Verify metadata directory checksums (verifies any checksums included with the transfer)
+#*Verify transfer checksums (verifies any checksums included with the transfer in its metadata directory)
-#*Assign checksums to objects (assigns a sha-256 checksum to each file in the /objects directory)
+#*Generate METS.xml document (creates a METS file capturing the original order of the transfer. This METS file is added to any SIPs generated from this transfer)
-#*Generate METS.xml document (creates a METS file capturing the original order of the transfer. This METS file is added to any SIPs generated from this transfer)
+#*Quarantine (quarantines the transfer to a set duration based on preconfiguration settings in the Administration tab of the dashboard; to allow virus definitions to update before a virus scan)
 #*Scan for viruses (scans for viruses and malware)
 #*Identify file format (this is the identification that normalization will be based upon, the user can choose between FIDO and extension or skipping format identification at this stage) See [[UM_transfer_1.0#Format_identification|Format identification]] below for more information.
 #*Characterize and extract metadata (identifies and validates file formats; extracts technical metadata embedded in the files). If you have preconfigured it to do so, Archivematica will stop during this micro-service and allow the user to choose a file identification command from a dropdown menu. To learn about preconfigured options, please see [[Administrator_manual_1.0#Processing_configuration|Administrator manual 1.0 - Processing configuration]]. Archivematica's file identification default is set to identification by file extension. You can also choose to skip identification and run it later, during Ingest, instead.
-#* Index transfer (Indexes transfer)
+#* Complete transfer (Includes indexing transfer)
 #A transfer that is in the middle of processing will show which micro-services have been completed (green) and which are in progress (orange).
 #When a micro-service fails or encounters an error, the micro-service background turns from green to pink and a "failed" icon appears next to the transfer or SIP name. See [[UM error handling|Error handling]] for more information about how to handle an error.

@@ Line 39: / Line 39: @@
 Another option is to create a transfer in a structured directory prior to beginning processing in Archivematica. The structured directory in Archivematica is the basic configuration of the transfer. If you just add a directory to the dashboard and start transfer processing, Archivematica will restructure it so it complies with this structure. There should be three subdirectories: logs, metadata, objects. The objects directory contains the digital objects that are to be preserved. The metadata directory contains the checksum, the METS file, and a submissionDocumentation subfolder, which can be used for transfer forms, donation agreements or any other documents that relate to the acquisition of the records. The logs folder will eventually contain logs generated when processing the transfer in Archivematica. You can create subdirectories within objects if desired.
-* Please do not include submission documentation that has non-standard characters in the filename, as submission documentation names are not sanitized.
+* Please do not include submission documentation that has non-standard characters in the filename, as submission documentation names are not sanitized. Any filenames other than plain ASCII names may cause errors in processing.
 #Open the file browser by clicking on the Home folder on the Archivematica desktop

← Older revision		Revision as of 20:51, 20 February 2014
Line 38:		Line 38:

	Another option is to create a transfer in a structured directory prior to beginning processing in Archivematica. The structured directory in Archivematica is the basic configuration of the transfer. If you just add a directory to the dashboard and start transfer processing, Archivematica will restructure it so it complies with this structure. There should be three subdirectories: logs, metadata, objects. The objects directory contains the digital objects that are to be preserved. The metadata directory contains the checksum, the METS file, and a submissionDocumentation subfolder, which can be used for transfer forms, donation agreements or any other documents that relate to the acquisition of the records. The logs folder will eventually contain logs generated when processing the transfer in Archivematica. You can create subdirectories within objects if desired.		Another option is to create a transfer in a structured directory prior to beginning processing in Archivematica. The structured directory in Archivematica is the basic configuration of the transfer. If you just add a directory to the dashboard and start transfer processing, Archivematica will restructure it so it complies with this structure. There should be three subdirectories: logs, metadata, objects. The objects directory contains the digital objects that are to be preserved. The metadata directory contains the checksum, the METS file, and a submissionDocumentation subfolder, which can be used for transfer forms, donation agreements or any other documents that relate to the acquisition of the records. The logs folder will eventually contain logs generated when processing the transfer in Archivematica. You can create subdirectories within objects if desired.
		+
		+	* Please do not include submission documentation that has non-standard characters in the filename, as submission documentation names are not sanitized.

	#Open the file browser by clicking on the Home folder on the Archivematica desktop		#Open the file browser by clicking on the Home folder on the Archivematica desktop

@@ Line 6: / Line 6: @@
 In Archivematica, Transfer is the process of transforming any set of digital objects and/or directories into a SIP. Transformation may include appraisal, arrangement, description and identification of donor restricted, private or confidential contents.
-In the Transfer tab of the Dashboard, the user moves digital objects from source directories accessible via the Storage Service into Archivematica. See [[https://www.archivematica.org/wiki/Administrator_manual_1.0#Storage_service|Administrator manual - Storage Service]] for instructions on how to set up shared transfer source directories. Once uploaded to the dashboard, transfers run through several micro-services: UUID assignment; checksum verification (if checksums are present); package extraction (i.e. unzipping of zipped or otherwise packaged files); virus checking; indexing; format identification and validation; and metadata extraction. </br>
+In the Transfer tab of the Dashboard, the user moves digital objects from source directories accessible via the Storage Service into Archivematica. See [[Administrator_manual_1.0#Storage_service|Administrator manual - Storage Service]] for instructions on how to set up shared transfer source directories. Once uploaded to the dashboard, transfers run through several micro-services: UUID assignment; checksum verification (if checksums are present); package extraction (i.e. unzipping of zipped or otherwise packaged files); virus checking; indexing; format identification and validation; and metadata extraction. </br>
 At the end of transfer, the user creates a SIP from one or more standard transfer(s). Once this is done, the SIP is moved into ingest.
@@ Line 18: / Line 18: @@
 If your transfer is composed of objects that are the result of digitization, please see [[UM digitization output .10|Digitization output]].
-If you would like to skip some of the default decision points or make preconfigured choices for your desired workflow, see [[Administrator_manual_1.0#Processing_configuration|Administrator manual - Processing configuration]]
+If you would like to skip some of the default decision points or make preconfigured choices for your desired workflow, see [[UM_administration_1.0#Processing_configuration|User manual - User administration - Processing configuration]]
 </br>

← Older revision		Revision as of 23:19, 19 February 2014
Line 73:		Line 73:

	== Format identification ==		== Format identification ==
		+
		+	Archivematica's default is to allow the user to choose identification options to base normalization actions upon during transfer and then use those results to base normalization upon in ingest. However, you can set your [[UM_administration_1.0#Processing_configuration\|preconfiguration options]] to allow for the opposite (skip at transfer and identify before normalization) or for both transfer and ingest to allow for user choice in the dashboard.
		+
		+	Artefactual included the ability to skip identification at transfer and/or to change identification tool before normalization mainly to allow for the possibility that content in the transfer backlog may contain formats for which there are not currently entries in the FPR. While the transfers are in the backlog, you can add rules that allow for the format(s) not identified or identifiable at time of transfer to the FPR so that, when they are processed through ingest, all formats will be identified and normalization attempted based on those identifications.
		+
		+	There may be other use case scenarios in the future that this configuration flexibility facilitates. In general, we aim to include as much flexibility as possible when it comes to workflow choices so that the archivist is as central as possible to AIP and DIP processing rather than hardcoding and automating so much that the archivist is left less influence on ingest.
		+
		+	Format identification is logged as a PREMIS event in the METS.xml using the results of running FITS tools (DROID, in particular), not the results of the tool selected to base normalization upon. This will change in coming releases.

← Older revision		Revision as of 23:02, 19 February 2014
Line 71:		Line 71:
	#See [[UM ingest\|Ingest]] for next steps.		#See [[UM ingest\|Ingest]] for next steps.
	[[Image:CreateSIP1.png\|600px\|right\|thumb\|'''Figure 4''' A transfer that is ready to be packaged into a SIP or stored in backlog]]		[[Image:CreateSIP1.png\|600px\|right\|thumb\|'''Figure 4''' A transfer that is ready to be packaged into a SIP or stored in backlog]]
		+
		+	== Format identification ==

@@ Line 14: / Line 14: @@
 If your transfer is a DSpace export, please see [[UM DSpace exports .10|DSpace export]].
-If your transfer is a bag or a zipped bag, please see [[UM Bags.10|Bags]]
+If your transfer is a bag or a zipped bag, please see [[UM Bags 1.0|Bags]]
 If your transfer is composed of objects that are the result of digitization, please see [[UM digitization output .10|Digitization output]].

@@ Line 34: / Line 34: @@
 </br>
-===Create a transfer with submission documentation===
 Another option is to create a transfer in a structured directory prior to beginning processing in Archivematica. The structured directory in Archivematica is the basic configuration of the transfer. If you just add a directory to the dashboard and start transfer processing, Archivematica will restructure it so it complies with this structure. There should be three subdirectories: logs, metadata, objects. The objects directory contains the digital objects that are to be preserved. The metadata directory contains the checksum, the METS file, and a submissionDocumentation subfolder, which can be used for transfer forms, donation agreements or any other documents that relate to the acquisition of the records. The logs folder will eventually contain logs generated when processing the transfer in Archivematica. You can create subdirectories within objects if desired.