Introduction
This page provides instructions on how to transfer files into Archivematica.
A batch of files is known as a transfer package.
Types of transfer packages
There are several types of transfers:
Type of transfer packages | Description |
|---|---|
Standard transfer | Default |
Zipped directory | Variant of standard transfer. The internal structure of a zipped directory matches that of a standard transfer. Archivematica accepts .zip, .tgz, or .tar.gz formats. |
Unzipped bags | A directory that meets the requirements specified in the BagIt File Packaging Format (i.e., a “Bag”) |
Zipped bags | A zipped directory that meets the requirements specified in the BagIt File Packaging Format (i.e., a “Bag”). Archivematica accepts .zip, .tgz, or .tar.gz formats. |
DSpace | An export from a DSpace repository. DSpace exports are packaged with a METS file for the export as a whole as well as each individual item. Archivematica can reuse some of the data in these METS files. |
Disk images | Disk image transfer type provides an extra disk image-specific metadata form to record information about the imaging process. Disk images can also be transferred as part of standard transfers or bag transfers. |
Dataverse | An export from a Dataverse repository. Dataverse exports contain metadata that Archivematica can reuse. |
Standard transfer
Log into Archivematica and navigate to the Transfer tab.
Click on the “Browse” button. This will reveal a drop-down menu with available transfer source locations.
Select the transfer source location from the drop-down menu.
This will reveal the transfer source location’s directory structure.
Navigate to the transfer package. Select the folder and click the “Add” button.
The transfer package will appear above the drop-down menu. Give the transfer a name. Usually, this is the reference code.
If known, provide the accession number.
Select the desired configuration.
Receive a notification that the transfer started.
Monitor microservices. If a microservice fails, pause the transfer and investigate the failure.
Once the microservices are complete, a SIP will be available in the Ingest tab.
Navigate to the Ingest tab.
Click on the edit icon to add descriptive metadata and rights information.
Click on the link to add metadata. Complete the form.
At the bottom of the page, click on the “Create” button to save the metadata.
Review the saved metadata. Click on the “Add” button to edit the metadata.
Navigate back to the Ingest tab and view the SIP. The reminder to add metadata job includes an Actions drop-down menu. Select “Continue.”
The Ingest is complete when the Store AIP microservice finishes.
