UM transfer 1.2 - Revision history

Courtney: /* Process the transfer */

2014-10-14T22:42:49Z

Process the transfer

Sromkey: /* Process the transfer */

2014-08-26T23:08:46Z

Process the transfer

Sromkey: /* Format identification */

2014-08-07T21:11:46Z

Format identification

Sromkey: Removed note about manual SIP creation not existing yet.

2014-08-07T21:05:25Z

Removed note about manual SIP creation not existing yet.

Courtney: /* Process the transfer */

2014-08-07T20:23:32Z

Process the transfer

Courtney: /* Create a transfer */

2014-08-07T20:21:39Z

Create a transfer

Courtney: /* Create a transfer */

2014-08-07T20:21:17Z

Create a transfer

Sromkey: /* General description */

2014-08-07T19:54:11Z

General description

Courtney: /* General description */

2014-08-04T22:03:59Z

General description

Courtney: /* Create a transfer */

2014-08-04T22:02:26Z

Create a transfer

@@ Line 59: / Line 59: @@
 #*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 and checksums to objects (assigns a unique universal identifier and sha-256 checksum to each file in the /objects directory)
-#*Verify transfer checksums (verifies any checksums included with the transfer in its metadata directory)
+#*Verify transfer checksums (verifies any checksums included with the transfer in its metadata directory, see [[UM_transfer_1.2_Include_checksums|Include checksums]]
 #*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)

@@ Line 63: / Line 63: @@
 #*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)
 #*Clean up file and directory names (removes prohibited characters from folder and filenames, such as ampersands)
 #*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.2#Format_identification|Format identification]] below for more information.

@@ Line 83: / Line 83: @@
 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.2#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.
+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 [[UM_FPR_1.2|Format Policy Registry]] (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.

@@ Line 71: / Line 71: @@
 #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.
 #Once the transfer micro-services are completed, a bell icon will appear next to the transfer. This means that the transfer is ready to be packaged into a SIP for ingest or sent to a backlog, indexed and stored to be retrieved for processing at a later date.
-#*Option 1: Select "Create single SIP and continue processing". (Note that Create SIP(s) manually is not currently functional. However, the ability to create one or more SIP(s) from one or more transfer(s) will return in Archivematica 1.1 with improved functionality in the web browser. See [File_Browser_Requirements|File browser requirements - Create SIP] and [Transfer_and_SIP_creation|Transfer and SIP creation workflows)
+#*Option 1: Select "Create single SIP and continue processing".
 #*Option 2: Select "Send transfer to backlog". In this case, your transfer will be stored in a backlog in the same location as your AIP store so that you can retrieve one or more transfers from the Ingest tab for processing at a later date. See [[UM_Transfer_backlog 1.2|Managing a backlog]]
 #*Option 3: Select "Reject the transfer".

@@ Line 52: / Line 52: @@
 == Process the transfer ==
-#In the dashboard transfer tab, the transfer will appear in the dashboard with a bell icon next to it. This means that it is awaiting a decision by the user. ('''figure 3''') [[Image:Approve1.png|600px|right|thumb|'''Figure 3'''  In the Actions drop-down menu, select "Approve transfer"]]
+#In the dashboard transfer tab, the transfer will appear in the dashboard with a bell icon next to it. This means that it is awaiting a decision by the user. [[Image:Approve1.png|600px|right|thumb|In the Actions drop-down menu, select "Approve transfer"]]
 #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.
+#In the Actions drop-down menu, select "Approve transfer" to begin processing the transfer. You may also "Reject transfer" and quit processing.
 #The transfer will now run through a series of [[Archivematica_1.2_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)
@@ Line 70: / Line 70: @@
 #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.
-#Once the transfer micro-services are completed, a bell icon will appear next to the transfer. This means that the transfer is ready to be packaged into a SIP for ingest or sent to a backlog, indexed and stored to be retrieved for processing at a later date ('''figure 4''').
+#Once the transfer micro-services are completed, a bell icon will appear next to the transfer. This means that the transfer is ready to be packaged into a SIP for ingest or sent to a backlog, indexed and stored to be retrieved for processing at a later date.
 #*Option 1: Select "Create single SIP and continue processing". (Note that Create SIP(s) manually is not currently functional. However, the ability to create one or more SIP(s) from one or more transfer(s) will return in Archivematica 1.1 with improved functionality in the web browser. See [File_Browser_Requirements|File browser requirements - Create SIP] and [Transfer_and_SIP_creation|Transfer and SIP creation workflows)
 #*Option 2: Select "Send transfer to backlog". In this case, your transfer will be stored in a backlog in the same location as your AIP store so that you can retrieve one or more transfers from the Ingest tab for processing at a later date. See [[UM_Transfer_backlog 1.2|Managing a backlog]]
 #*Option 3: Select "Reject the transfer".
 #See [[UM ingest 1.2|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|A transfer that is ready to be packaged into a SIP or stored in backlog]]
 </br>

@@ Line 31: / Line 31: @@
 *In transfer tab, select your transfer type in the dropdown menu. Types include standard, unzipped bag, zipped bag, DSpace, maildir and Disk image.
-*In transfer tab, name your transfer and browse to a source directory to select your object or set of objects for upload. You can concurrently upload multiple transfers composed of objects and directories from different sources. Repeat this step if your transfer is composed from multiple sources. ('''figure 1''') [[Image:Browse1.png|600px|right|thumb|'''Figure 1'''  Select transfer(s) from source directory(ies)]]
+*In transfer tab, name your transfer and browse to a source directory to select your object or set of objects for upload. You can concurrently upload multiple transfers composed of objects and directories from different sources. Repeat this step if your transfer is composed from multiple sources. [[Image:Browse1.png|600px|right|thumb|Select transfer(s) from source directory(ies)]]
 *If applicable, enter an accession number for the transfer. This is not a required field, but it will be indexed to allow for searching by accession number from the transfer backlog in the Ingest tab.
 *Once all of your digital object sources have been loaded, hit the Start Transfer button for the transfer processing to begin. Note that you can remove one or more of the loaded sources prior to Start Transfer by clicking on the red Delete icon beside the directory.

@@ Line 30: / Line 30: @@
 </br>
-#In transfer tab, select your transfer type in the dropdown menu. Types include standard, unzipped bag, zipped bag, DSpace, maildir and Disk image.
+*In transfer tab, select your transfer type in the dropdown menu. Types include standard, unzipped bag, zipped bag, DSpace, maildir and Disk image.
-#In transfer tab, name your transfer and browse to a source directory to select your object or set of objects for upload. Your transfer can be composed of multiple directories from different sources. Repeat this step if your transfer is composed from multiple sources. ('''figure 1''') [[Image:Browse1.png|600px|right|thumb|'''Figure 1'''  Select transfer(s) from source directory(ies)]]
+*In transfer tab, name your transfer and browse to a source directory to select your object or set of objects for upload. You can concurrently upload multiple transfers composed of objects and directories from different sources. Repeat this step if your transfer is composed from multiple sources. ('''figure 1''') [[Image:Browse1.png|600px|right|thumb|'''Figure 1'''  Select transfer(s) from source directory(ies)]]
-#If applicable, enter an accession number for the transfer.
+*If applicable, enter an accession number for the transfer. This is not a required field, but it will be indexed to allow for searching by accession number from the transfer backlog in the Ingest tab.
-#Once all of your digital object sources have been uploaded, hit the Start Transfer button for the transfer processing to begin. ('''figure 2''')[[Image:Start1.png|600px|right|thumb|'''Figure 2'''  Start transfer]]
+*Once all of your digital object sources have been loaded, hit the Start Transfer button for the transfer processing to begin. Note that you can remove one or more of the loaded sources prior to Start Transfer by clicking on the red Delete icon beside the directory.
 </br>

@@ Line 8: / Line 8: @@
 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.1#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 can be moved into ingest or send to a [[UM_Transfer_backlog_1.2|UM transfer backlog]] backlog for processing later.
+At the end of transfer, the user creates a SIP from one or more standard transfer(s). Once this is done, the SIP can be moved into ingest or sent to a [[UM_Transfer_backlog_1.2|UM transfer backlog]] backlog for processing later.
 If you would like to import lower-level metadata with your transfer (i.e. metadata to be attached to subdirectories and files within a SIP), see [[UM_Transfer_metadata_import_1.2|Metadata import]]

← Older revision		Revision as of 22:03, 4 August 2014
Line 17:		Line 17:

	If your transfer is composed of objects that are the result of digitization, please see [[UM digitization output 1.2\|Digitization output]].		If your transfer is composed of objects that are the result of digitization, please see [[UM digitization output 1.2\|Digitization output]].
		+
		+	If your transfer is composed of digital forensic disk images, please see [[UM_Forensic_image_transfer_1.2\|Forensic image processing]]

	If you would like to skip some of the default choices for dashboard decision points or make preconfigured choices for your desired workflow, see [[UM_administration_1.2#Processing_configuration\|User manual - User administration - Processing configuration]]		If you would like to skip some of the default choices for dashboard decision points or make preconfigured choices for your desired workflow, see [[UM_administration_1.2#Processing_configuration\|User manual - User administration - Processing configuration]]