Archivematica @ Wellcome Collection
  • Introduction
  • High-level design
  • Storing born-digital files
    • Creating a transfer package
    • Upload a transfer package to S3
    • Check a package was stored successfully
    • Downloading a package from the storage service
    • Following a package in the dashboard
  • Service architecture
    • How does Archivematica work?
      • The Archivematica apps
      • Microservices, tasks and jobs
      • Gearman, ElastiCache, and the MCP server/client
    • How is our deployment unusual?
      • What are our extra services?
      • ECS containers on EC2, not Fargate
      • Why we forked Archivematica
    • How it fits into the wider platform
  • About our deployment
    • Using Wellcome catalogue identifiers
    • Different environments
    • Working storage: MySQL, Redis, and EBS
  • Administering Archivematica
    • Bootstrapping a new Archivematica stack
    • User management
      • How to add or remove users
      • Authentication with Azure AD
    • Upgrading to a new version of Archivematica
    • Running an end-to-end test
    • Clearing old transfers from the dashboard
  • Debugging Archivematica
    • Where to find application logs
    • Troubleshooting known errors
      • Timeout waiting for network interface provisioning to complete
      • 401 Unauthorized when the s3_start_transfer Lambda tries to run
      • "pull access denied" when running containers (and other ECS agent issues)
      • "Unauthorized for url" when logging in
      • "gearman.errors.ExceededConnectionAttempts: Exceeded 1 connection attempt(s)" in MCP server
      • NotADirectoryError in the Extract zipped transfer stage
    • Restarting services if a task is stuck
    • SSH into the Archivematica container hosts
Powered by GitBook
On this page
  • Metadata files
  • Compressing the package
  • See also
  1. Storing born-digital files

Creating a transfer package

PreviousHigh-level designNextUpload a transfer package to S3

Last updated 3 months ago

A transfer package is a zip file containing the born-digital files you want to store, plus some metadata.

The files can be in any structure, including folders and subfolders.

The metadata files must be stored in a top-level folder called metadata.

Metadata files

We use two metadata files in our transfer packages:

  • metadata.csv, which contains the identifier.

    If it's a catalogued package, the CSV should have two columns and the catalogue identifier in dc.identifier:

    filename,dc.identifier
    objects/,PP/MDM/A/3/1a

    If it's an accession, the CSV should have three columns and the accession number in accession_number:

    filename,collection_reference,accession_number
    objects/,SA/TIH,2314_2

    In both cases, the CSV only ever has objects/ as the filename.

Compressing the package

The files must be in the top-level of the zip; there can't be an enclosing folder.

❌
✅

See also

rights.csv, []

– we use the "zipped directory" transfer type.

Transfer in the Archivematica documentation
https://github.com/wellcomecollection/archivematica-infrastructure/issues/113
An example transfer package. There's a folder called "transfer_package", which contains three images and a folder called "metadata". The metadata folder contains a single file, metadata.csv.
Selecting the enclosing folder, then right-clicking and 'Compress folder', in the macOS Finder
Selecting all the top-level files, then right-clicking and 'Compress', in the macOS Finder.
which contains the rights information