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
  1. Storing born-digital files

Upload a transfer package to S3

PreviousCreating a transfer packageNextCheck a package was stored successfully

Last updated 2 years ago

Once you have as a zip file, you need to upload it to S3 for processing.

Where you upload it depends on what sort of package this is:

  • Does this contain real files, or is it just for testing?

    • If real files, then use the bucket wellcomecollection-archivematica-transfer-source

    • If you're just testing, then use the bucket wellcomecollection-archivematica-staging-transfer-source

  • Does this contain catalogued data, or is it an uncatalogued accession?

    • If catalogued, then upload into the prefix born-digital

    • If uncatalogued, then upload into the prefix born-digital-accessions

Pick a descriptive name for your transfer package, then upload it to S3.

For example, if you were using the AWS CLI and you had an uncatalogued accession to upload in prod:

aws s3 cp 1234.zip s3://wellcomecollection-archivematica-transfer-source/born-digital-accessions/1234.zip

A few seconds after you upload, you should see a log file appear in the bucket, with either "success" or "failed" in the name.

  • If it says "success" – your package has been accepted and is being sent to Archivematica

  • If it says "failed" – your package has not been accepted; it's structured incorrectly. Download the log file for instructions on how to fix it.

created your transfer package