Archivematica 1.15.1 is an old release, and the documentation is in maintenance mode.


During ingest, Archivematica can generate access copies of digital objects and package them into a Dissemination Information Package (DIP). DIPs can be uploaded to an access system or stored for future use. As a general rule, we recommend only creating DIPs when you need them to save on storage space - you can create DIPs on demand by re-ingesting your AIP at a later date.

After a DIP has been uploaded and/or stored it is moved to the uploadedDIPs directory. If this data is no longer needed, the uploadedDIPs directory can be cleared out. See Processing storage usage for more information.

Archivematica’s Access tab displays DIPs that have been uploaded to AtoM. It does not display DIPs that have been sent to other access systems, like ArchivesSpace.

On this page:

Access systems

If you have chosen to create a Dissemination Information Package (DIP) by selecting either Normalize for preservation and access or Normalize for access at the Normalization microservice, you can upload it to a content management tool as a way of providing access to your archival material. For more information on normalization options in Archivematica, please see Normalize.

The DIP includes access copies of the original digital objects in the transfer, created through either Archivematica’s normalization rules or a manual normalization process. The DIP also includes a DIP METS file and, optionally, a thumbnail for each digital object.

A content management tool called AtoM is Archivematica’s default access system. AtoM is a web-based, open source application for standards-based archival description and access in a multilingual, multi-repository environment. Access integration workflows also exist for ArchivesSpace and CONTENTdm.

Upload a DIP to AtoM

To upload DIPs to AtoM, you must first have a working AtoM instance. An administrator will need to configure the AtoM instance to talk to Archivematica. For more information about setting up an integration with AtoM, see Using AtoM 2.x with Archivematica.


You must create the target description in AtoM before uploading the DIP. You will need to indicate part of the description’s URL or a target collection in order to send the DIP to the appropriate place during DIP upload.

Digital objects uploaded to AtoM are added as children of the target description and are, by default, given the level of description of item. You can assign other levels of description by sending your transfer to backlog and adding AtoM levels of description on the Appraisal tab.

It is possible to arrange your transfer to create a hierarchy that AtoM will recognize by using the arrangement feature on Appraisal tab.

You can also add descriptive metadata to your transfer using either the metadata form or the metadata CSV file. This descriptive metadata will be passed to AtoM. Note that the AtoM DIP upload integration supports Dublin Core descriptive metadata only. The following Dublin Core fields are mapped to the ISAD(G) template in AtoM:

Dublin Core ISAD(G)
title title
identifier identifier
creator name of creator
date date of creation
type subject access point
provenance immediate source of acquisition or transfer
description scope and content
extent extent and medium
format extent and medium
source location of originals
language language of material
rights conditions governing access
coverage place access point
subject subject access point


Adding metadata through the form in Archivematica will create an intermediary descripton in AtoM. However, if the transfer is sent to the backlog and AtoM descriptions are applied (see Adding AtoM levels of description), then any metadata added through the form will not be present in AtoM. There will also be no intermediary description, but the levels of description you applied will be present in AtoM.

There are two ways to provide the target description to Archivematica. The first is by providing the slug during the Upload DIP microservice.

  1. Process your transfer. You must select Normalize for preservation and access or Normalize for access at the Normalization microservice. When you reach the Upload DIP microservice, select “Upload DIP to AtoM/Binder” from the drop-down menu.
  2. A dialogue box will appear. Enter the permalink of the description in the dialogue box. For example, if the URL of the archival description is, enter my-target-description. See slug in the AtoM glossary for more information.
Image shows a popup window where a user can enter the slug for an AtoM description
  1. Click the blue “Upload” button. Digital objects will be uploaded as child items within the target description.
  2. When the DIP has finished uploading, open the Access tab in the dashboard. This tab shows the AIP and the uploaded DIP. Note that due to a known issue, if you want to navigate to the uploaded DIP using the link provided, you must manually edit the URL to remove /sword/deposit.
  3. Check the target description in AtoM. The digital object(s) should be displayed as child objects of the record.

In a more automated environment, you can add the slug to the Access system ID box when you are setting up your transfer. Archivematica will automatically grab this value when it reaches the Upload DIP microservice.

  1. Create a new transfer. In the Access system ID box, enter the permalink of the description in the dialogue box. For example, if the URL of the archival description is, enter my-target-description. See slug in the AtoM glossary for more information.
Image shows new transfer with an AtoM slug defined as the access system identifier
  1. Process your transfer. You must select Normalize for preservation and access or Normalize for access at the Normalization microservice. When you reach the Upload DIP microservice, select “Upload DIP to AtoM/Binder” from the drop-down menu (or set this as the preconfigured choice in the processing configuration).
  2. Check the target description in AtoM. The digital object(s) should be displayed as child objects of the record.

Metadata-only upload to AtoM

In Archivematica 1.6 and higher, you can send AIP object metadata to AtoM without uploading access copies of the files. This may be a helpful workflow if you have digital objects which you wish to make discoverable but you can’t display online for copyright or privacy reasons.


AtoM 2.4 or higher is required to use this workflow.


The following AtoM-Archivematica workflows are not currently supported with this workflow:

  • Descriptive metadata: if descriptive metadata is included by csv or entering in the user interface, the metadata will not display in AtoM in this workflow.
  • SIPs with levels of description assigned using the arranging for AtoM workflow - the levels of description will be ignored in this workflow.
  1. Navigate to Archival Storage and search or browse for the AIP. Click on the name of the AIP, or “View”.
  2. Under “Actions,” in the Upload DIP tab enter the slug of the AtoM description you wish to upload to.
Entering the slug of the AtoM description to upload metadata to
  1. Upon successful upload, AtoM will have created a File level description for the AIP and an Item level description for each object.
AtoM description showing uploaded content

Each item will have a generic thumbnail associated with it and digital object metadata about the original object, including filename, filesize, date uploaded, object and AIP UUIDs, format name, format version, format registry and key.

AtoM description showing uploaded item with digital object metadata

Upload a DIP to ArchivesSpace

To upload DIPs to your ArchivesSpace instance, you must enter your ArchivesSpace information and credentials in the Administration tab. See ArchivesSpace dashboard configuration for more information.

Create a SIP using the Transfer process as normal. During Normalization, choose one of the options that normalizes the package for access. During the Upload DIP microservice, select Upload DIP to Archives Space. The Match page should automatically open.

  1. Find the ArchivesSpace collection to which you would like to upload the DIP. By clicking on the name of the resource, you can drill down into the collection to upload the DIP at a lower level of description.
  2. When you have navigated to the level of description where you want to store the DIP, select Assign DIP objects to this resource.
  3. On the Assign Objects screen, select which objects you would like to assign to which resources. Using the filter boxes in the top right allow you to search for specific objects or resources by name.
  4. Once you have selected the objects and the resource you would like to pair them with, click Pair in the top right corner. Repeat steps 2-4 as needed.
  5. When you are done pairing objects and resources, click on Review matches.
  6. To remove all pairs and restart, click on Restart matching.
  7. If everything is correct, click on Finish matching.

This will take you back to the Ingest tab, where you can finish ingesting the AIP.

Alternatively, you can manually create the matches and place them in the metadata folder of the transfer in a file named archivesspaceids.csv. For example, given the following transfer tree:

├── extra
│   └── oakland03.jp2
├── Landing zone.jpg
└── metadata
  └── archivesspaceids.csv

The CSV file needs two columns, one with a relative path to the original file in the transfer directory and the other with the Ref ID from the ArchivesSpace Archival Object, which can be obtained from the “Basic information” section in the Archival Object view page. E.g.:

"Landing zone.jpg",49807e9587de87dbafb459b34bd20b78

If the Upload DIP to ArchivesSpace option is selected in the working processing configuration, the CSV file will be used to create the matches in the upload. Otherwise, after selecting Upload DIP to ArchivesSpace in the ingest tab you will be taken to the Match page and, to check the matches created from the CSV file instead of creating new ones, you can click directly on Review matches and finalize or restart the matching.

Store DIP

Archivematica also provides the option to store the DIP to a location that you have configured via the Storage Service. This can be configured to be a local server, NFS-mounted or another storage protocol such as DuraCloud.

To store a DIP:

  1. Ensure that at least one DIP storage location has been configured in the Storage Service.
  2. At the Store DIP job at the Upload DIP microservice on the Archival Storage tab, choose Store DIP.
  3. At Store DIP location, select the DIP storage location from the configured options.

Review and download DIPs

All DIPs that have been stored are available for download through the Packages tab in the Storage Service. This is the default method for downloading DIPs.

If you have used the Upload DIP functionality to send your DIP to AtoM, ArchivesSpace, or CONTENTdm, you will have the option to review the DIP from the Archivematica user interface. When the Upload DIP microservice is complete, a “review” link will appear:

Click on the "review" link in the Upload DIP microservice

This will open the uploadedDIPs directory in a new tab. You can navigate the directory by clicking on the yellow folder icons. Click on the the individual DIP object, thumbnail, or METS file to view it.

Download DIP screen showing a DIP directory expanded.

Depending on the type and size of the file, it may either open in another tab or it may be downloaded to your computer.

Access tab

By clicking the Access tab in the Dashboard, you can see a table showing all DIPs upload to AtoM including the URL, the associated AIP, the upload date and status, and the option to delete from the Access tab. Note that this link will delete the record of the DIP in the Access tab, not the actual DIP.

At this time, the Access tab only provides links to DIPs uploaded to AtoM, not to other access systems or DIPs that have been stored.

Back to the top