Administrator manual 1.1 - Revision history

Mjordan: /* Approving a transfer */

2014-07-01T15:58:53Z

Approving a transfer

Mjordan: /* How to Configure a Location */

2014-06-24T23:32:11Z

How to Configure a Location

Courtney: /* Processing configuration */

2014-04-28T17:22:12Z

Processing configuration

Courtney: Created page with "Main Page > Documentation > Administrator manual This manual covers administrator-specific instructions for Archivematica. It will also provide help for using forms i..."

2014-03-28T23:03:27Z

Created page with "Main Page > Documentation > Administrator manual This manual covers administrator-specific instructions for Archivematica. It will also provide help for using forms i..."

Show changes

@@ Line 359: / Line 359: @@
 === Approving a transfer ===
-The REST API can be used to approve a transfer. The transfer must first be copied into the appropriate watch directory. To determine the location of the appropriate watch directory, first figure out where the shared directory is from the <code>sharedDirectory</code> value of <code>/etc/archivematica/MCPServer/serverConfig.conf</code>. Within that directory is a subdirectory <code>activeTransfers</code>. In this subdirectory are watch directories for the various transfer types.
+The REST API can be used to approve a transfer. The transfer must first be copied into the appropriate watch directory. To determine the location of the appropriate watch directory, first figure out where the shared directory is from the <code>watchDirectoryPath</code> value of <code>/etc/archivematica/MCPServer/serverConfig.conf</code>. Within that directory is a subdirectory <code>activeTransfers</code>. In this subdirectory are watch directories for the various transfer types.
 When using the REST API to approve a transfer, if a transfer type isn't specified, the transfer will be deemed a standard transfer.

@@ Line 139: / Line 139: @@
 == How to Configure a Location ==
-TODO
+For Spaces of the type "Local Filesystem," Locations are basically directories (or more accurately, paths to directories). You can create Locations for Transfer Source, Currently Processing, or AIP Storage directories.
 = Dashboard administration tab =

@@ Line 154: / Line 154: @@
 <pre><processingMCP>
    <preconfiguredChoices>
      <preconfiguredChoice>
-       <appliesTo>Workflow decision - create transfer backup</appliesTo>
+       <appliesTo>755b4177-c587-41a7-8c52-015277568302</appliesTo>
-       <goToChain>Do not backup transfer</goToChain>
+       <goToChain>d4404ab1-dc7f-4e9e-b1f8-aa861e766b8e</goToChain>
      </preconfiguredChoice>
      <preconfiguredChoice>
-       <appliesTo>Workflow decision - send transfer to quarantine</appliesTo>
+       <appliesTo>eeb23509-57e2-4529-8857-9d62525db048</appliesTo>
-       <goToChain>Skip quarantine</goToChain>
+       <goToChain>5727faac-88af-40e8-8c10-268644b0142d</goToChain>
      </preconfiguredChoice>
      <preconfiguredChoice>
-       <appliesTo>Remove from quarantine</appliesTo>
+       <appliesTo>19adb668-b19a-4fcb-8938-f49d7485eaf3</appliesTo>
-       <goToChain>Unquarantine</goToChain>
+       <goToChain>333643b7-122a-4019-8bef-996443f3ecc5</goToChain>
-       <delay unitCtime="yes">50</delay>
+       <delay unitCtime="yes">2419200.0</delay>
      </preconfiguredChoice>
    </preconfiguredChoices>
@@ Line 171: / Line 199: @@
 </pre>
-Where appliesTo is the name of the job presented in the dashboard, and goToChain is the desired selection. Note: these are case sensitive. The default processingMCP.xml file is located at '/var/archivematica/sharedDirectory/sharedMicroServiceTasksConfigs/processingMCPConfigs/defaultProcessingMCP.xml'.
+Where appliesTo is the UUID associated with the micro-service job presented in the dashboard, and goToChain is the UUID of the desired selection. The default processingMCP.xml file is located at '/var/archivematica/sharedDirectory/sharedMicroServiceTasksConfigs/processingMCPConfigs/defaultProcessingMCP.xml'.
 The processing configuration administration page of the dashboard provides you with an easy form to configure the default 'processingMCP.xml' that's added to a SIP or transfer if it doesn't already contain one. When you change the options using the web interface the necessary XML will be written behind the scenes.
-[[File:ProcessingConf-1.png|1000px|center|thumb|Processing configuration form in Administration tab of the dashboard]]
+</br>
 *For the approval (yes/no) steps, the user ticks the box on the left-hand side to make a choice. If the box is not ticked, the approval step will appear in the dashboard.
 *For the other steps, if no actions are selected the choices appear in the dashboard
 *You can select whether or not to send transfers to quarantine (yes/no) and decide how long you'd like them to stay there.
 *You can approve normalization, sending the AIP to storage, and uploading the DIP without interrupting the workflow in the dashboard.
-*You can pre-select which format identification tool to run in both transfer and ingest to base your normalization upon.
+*You can pre-select which format identification tool and command to run in both/either transfer and/or ingest to base your normalization upon.
 *You can choose to send a transfer to backlog or to create a SIP every time.
 *You can select between 7z using lzma and 7zip using bzip or parallel bzip2 algorithms for AIP compression.
 *For select compression level, the options are as follows: