Dashboard administration tab¶

Name¶

The name of the processingMCP.xml that you are editing.

Assign UUIDs to directories¶

Directories are given an entry in the fileSec and assigned a unique universal identifier (UUID). Note that the digital objects in the transfer are always assigned a UUID.

Options:

1. None - the user is prompted for a decision.
2. Yes - UUIDs are assigned.
3. No - UUIDs are not assigned.*

Send transfer to quarantine¶

Transfers are sequestered until virus definitions can be updated.

Options:

1. None - the user is prompted for a decision.
2. Yes - transfers are automatically quarantined.
3. No - transfers are not sent to quarantine.*

Remove from quarantine after (days)¶

Transfers are automatically removed from quarantine after a defined number of days and made available for further processing.

Enter the number of days that transfers should remain in quarantine (i.e. 5).

The default value for this field is 28 days.

Generate transfer structure report¶

A text file is generated showing a directory tree of the original transfer structure.

Options:

1. None - the user is prompted for a decision.
2. Yes - structure report is created.*
3. No - structure report is not created.

Perform file identification (Transfer)¶

Choose whether or not to identify the format of the files in your transfer.

Options:

1. None - the user is prompted for a decision.*
2. Yes - use the enabled file identification command. See Identification for more information.
3. No - files will not be identified.

Extract packages¶

Packages (such as .zip files) are unzipped and extracted into a directory.

Options:

1. None - the user is prompted for a decision.*
2. Yes - the contents of the package are extracted.
3. No - package is left as-is.

Delete packages after extraction¶

Packages that have been extracted in the previous step can be deleted after extraction.

Options:

1. None - the user is prompted for a decision.*
2. Yes - the package is deleted.
3. No - the package is preserved along with the extracted content.

Perform policy checks on originals¶

If you have created policies using MediaConch, Archivematica runs the original transfer materials against the policies to assess conformance.

Options:

1. None - the user is prompted for a decision.
2. Yes - the transfer is checked against any policies.
3. No - policies are ignored.*

Examine contents¶

Run Bulk Extractor, a forensics tool that can recognize credit card numbers, social security numbers, and other patterns in data. For more information on reviewing Bulk Extractor logs, see the Analysis pane on the Appraisal tab.

Options:

1. None - the user is prompted for a decision.*
2. Skip examine contents - Bulk Extractor does not run.
3. Yes - Bulk Extractor scans content and creates log outputs of recognized patterns for review.

Create SIP(s)¶

Create a formal SIP out of the transfer or send it to the backlog.

Options:

1. None - the user is prompted for a decision.*
2. Send to backlog - transfer is sent to a backlog storage space for temporary storage or appraisal.
3. Create single SIP and continue processing - transfer becomes a SIP and is made available for further processing on the ingest tab.

Select file format identification command (Ingest)¶

Choose to identify the format of files in your SIP.

Options:

1. None - the user is prompted for a decision.
2. Yes - use the enabled file identification command. See Identification for more information.
3. No, use existing data - re-uses file identification data from the transfer tab.*

Normalize¶

Convert ingested digital objects to preservation and/or access formats. See Normalize for more information.

Options:

1. None - the user is prompted for a decision.*
2. Normalize for preservation and access - creates preservation copies of the objects plus access copies which will be used to generate the DIP.
3. Normalize for preservation - creates preservation copies only. No access copies are created and no DIP will be generated.
4. Normalize manually - see Manual Normalization for more information.
5. Do not normalize - the AIP will contain originals only. No preservation or access copies are generated and no DIP will be generated.
6. Normalize service files for access - see Transferring material with service (mezzanine) files for more information.
7. Normalize for access - the AIP will contain originals only. No preservation copies will be generated. Access copies will be created which will be used to generate the DIP.

Approve normalization¶

The dashboard allows users to review the normalization output and the normalization report.

Options:

1. None - the user has a chance to review and approve normalization.*
2. Yes - skip the review step and automatically continue processing.

Generate thumbnails¶

This gives the option of generating thumbnails for use in the AIP and DIP.

Options:

1. None - the user is prompted for a decision.
2. Yes, without default - thumbnails will be produced for any format which has a normalize for thumbnails rule in the FPR. Formats which do not have a rule will not have a thumbnail generated.
3. No - thumbnails will not be generated.
4. Yes - thumbnails will be generated according to the format rules in the FPR. Formats which do not have a rule will have a default thumbnail generated (grey document icon).*

Perform policy checks on preservation derivatives¶

If you create policies using MediaConch, run the policies against the newly-created preservation derivatives to ensure conformation.

Options:

1. None - the user is prompted for a decision.
2. Yes - the normalized files are checked against any policies.
3. No - policies are ignored.*

Perform policy checks on access derivatives¶

If you create policies using MediaConch, run the policies against the newly-created preservation derivatives to ensure conformation.

Options:

1. None - the user is prompted for a decision.
2. Yes - the normalized files are checked against any policies.
3. No - policies are ignored.*

Bind PIDs¶

Assign persistent identifiers and send the information to a Handle.Net server. See Bind PIDs for more information.

Options:

1. None - the user is prompted for a decision.
2. Yes - PIDs are created and a API call posts the PIDs to the Handle Server.
3. No - PIDs are not created.*

Document empty directories¶

By default, Archivematica removes empty directories and does not document that they existed.

Options:

1. None - the user is prompted for a decision.
2. Yes - an entry for the directory is created in the structmap.
3. No - the directory is not documented.*

Reminder: add metadata if desired¶

Archivematica allows users to see add metadata to a SIP through the user interface. This reminder occurs at the last moment that it is possible to add metadata; once the ingest proceeds past this point, it is no longer possible to add metadata to the SIP.

Options:

1. None - the user has a chance to add metadata.*
2. Continue - skip the reminder and automatically continue processing.

Transcribe files (OCR)¶

Users can elect to run Tesseract, an OCR tool that is included in Archivematica, to produce text files containing file transcripts. For more information, see (see Transcribe SIP contents).

Options:

1. None - the user is prompted for a decision.*
2. Yes - Tesseract runs on all OCR-able files.
3. No - Tesseract does not run.

Select file format identification command (Submission documentation & metadata)¶

Choose a tool to identify the format of any submission documentation and/or metadata files that were included in your transfer.

Options:

1. None - the user is prompted for a decision.
2. Yes - use the enabled file identification command. See Identification for more information.*
3. No - files will not be identified.

Select compression algorithm¶

AIPs created by Archivematica can be stored as compressed packages or uncompressed, depending on your storage requirements.

Options:

1. None - the user is prompted for a decision.
2. 7z using bzip2 - a 7Zip file is created using the bzip2 algorithm.*
3. 7z using LZMA - a 7Zip file is created using the LZMA algorithm.
4. 7z without compression - a 7Zip file is created but the contents are not compressed.
5. Gzipped tar - the AIP is created using the gzip algorithm.
6. Parallel bzip2 - a 7Zip file is created using the Parallel bzip2 (pbzip2) algorithm.
7. Uncompressed - the AIP is not compressed.

Select compression level¶

If you selected a compression choice in the step above, you can determine how compressed you would like your AIP to be. Selecting a higher compression level means that the resulting AIP is smaller, but compression also takes longer. Lower compression levels mean quicker compression, but a larger AIP.

Options:

1. None - the user is prompted for a decision.
2. 5 - normal compression mode - the compression tool will strike a balance between speed and compression to make a moderately-sized, moderately- compressed AIP.*
3. 7 - maximum compression - a smaller AIP that takes longer to compress.
4. 9 - ultra compression - the smallest possible AIP.
5. 3 - fast compression mode - a larger AIP that will be compressed quickly.
6. 1 - fastest mode - the AIP will be compressed as quickly as possible.

Store AIP¶

Pausing at the Store AIP microservice allows users to review the AIP contents prior to storage. If you do not want to manually review AIPs prior to storage, this can be set to bypass that review step.

Options:

1. None - the user is prompted for a decision.*
2. Yes - the AIP is marked for storage automatically.

Store AIP location¶

Once the previous step is approved, the AIP can be automatically sent to a specified storage location by setting the preferred location.

Options:

1. None - the user is prompted for a decision.*
2. Default location - the AIP is stored in the AIP storage location that has been defined as the default in the Storage Service.
3. [Other storage locations] - any other AIP storage locations that are available will also appear on this list.

Upload DIP¶

If a DIP was created, it can be automatically sent to an access system for which there is an Archivematica integration.

Options:

1. None - the user is prompted for a decision.*
2. Upload DIP to CONTENTdm - see CONTENTdm DIP upload documentation.
3. Upload DIP to AtoM - see AtoM DIP upload documentation.
4. Do not upload - the DIP will not be uploaded to an access system.
5. Upload DIP to ArchivesSpace - see ArchivesSpace DIP upload documentation.

Store DIP¶

If a DIP was created, it can be stored without interrupting the workflow in the dashboard. Note that DIP storage is not required, and that DIPs can be created on demand by re-ingesting the AIP.

Options:

1. None - the user is prompted for a decision.*
2. Yes - the DIP is marked for storage automatically.

Store DIP location¶

If the previous step and this step are configured, all DIPs will be sent to the selected storage location (unless you have included a custom processing configuration with the transfer that defines another location).

Options:

1. None - the user is prompted for a decision.*
2. Default location - the DIP is stored in the DIP storage location that has been defined as the default in the Storage Service.
3. [Other storage locations] - any other DIP storage locations that are available will also appear on this list.