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

Following a package in the dashboard

PreviousDownloading a package from the storage serviceNextHow does Archivematica work?

Last updated 2 years ago

The Archivematica dashboard is a web app that allows you to monitor the progress of a transfer package. You can find it at one of these URLs:

  • prod is https://archivematica.wellcomecollection.org/

  • staging is https://archivematica-stage.wellcomecollection.org/

If you have access to Archivematica, you should be able to log in using your Azure AD credentials. If not, ask in the #wc-preservation channel in Slack for help logging in.

This is what it looks like:

A new transfer package will start in the Transfer tab, and go through various processing steps. If those steps succeed and it comples the Create SIP from Transfer task, then it moves to the Ingest tab.

In the Ingest tab, it goes through more processing steps, and eventually gets to Store AIP. This is the step where the package gets uploaded to the Wellcome storage service; if this step completes successfully, then the package has been correctly stored.

[The terms SIP and AIP come from the OAIS model.]