Name

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

Digitization

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.

Yes

Generate transfer structure report

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

Yes

Perform file format identification (Transfer)

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

Yes

Extract packages

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

No

Delete packages after extraction

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

No

Perform policy checks on originals

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

No

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.

Skip examine contents

Create SIP(s)

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

Create single SIP and continue processing

Perform file format identification (Ingest)

Choose to identify the format of files in your SIP.

Yes

Normalize

Convert ingested digital objects to preservation and/or access formats.

Do not normalize

Approve normalization

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

Yes

Generate thumbnails

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

Yes

Perform policy checks on preservation derivatives

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

No

Perform policy checks on access derivatives

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

No

Bind PIDs

Assign persistent identifiers and send the information to a Handle.Net server.

No

Document empty directories

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

No

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.

Continue

Transcribe files (OCR)

Users can elect to run Tesseract, an OCR tool that is included in Archivematica, to produce text files containing file transcripts.

No

Perform file format identification (Submission documentation & metadata)

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

Yes

Select compression algorithm

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

7z using bzip2

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.

5 - normal compression

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.

Yes

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.

Store AIP in standard Archivematica directory

Upload DIP

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

Upload DIP to AtoM/Binder

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.

Do not store

Store DIP location

None