Archivematica's 1,061 title matches make preservation control planes worth inventorying
Archivematica manages digital preservation workflows: transfers, ingest, normalization, storage and archival packages. A dashboard that controls those workflows can approve transfers, expose metadata and connect to a separate Storage Service. The system is not a passive archive viewer. It is a control plane over the evidence and files an institution has promised to preserve.
On 2026-10-31, a count-only ZoomEye query returned zero matches for app="Archivematica" and 1,061 for title="Archivematica". The title query ran at 23:44:58 UTC and the application query at 23:44:57 UTC. Both used sub_type=all, page 1 and page size 1. The zero application result is a fingerprint miss, not a claim that no dashboard exists. The 1,061 title matches can include project pages, training material and user portals.
The documentation distinguishes the Dashboard from the Storage Service API. Both require authentication, and the Dashboard uses Django's cookie-based user authentication for its web session. API calls can use a username and API key, with an Authorization header carrying the key or, in the older documented pattern, query parameters. The query-parameter form creates a logging risk. Prefer the header form, enforce TLS, and make sure reverse-proxy logs do not retain credentials.
Inventory both services. The Dashboard may be used by archivists and preservation staff. The Storage Service may have its own API and credentials and may connect to object storage, network filesystems or remote locations. A dashboard that is private does not automatically make a storage endpoint private. A storage service that is reachable from an application network should still authenticate callers and restrict administrative operations.
Test roles with a low-privilege account. Confirm who can create a transfer, approve an ingest, change processing configuration, download a package or delete an object. The documented API is designed for automation, so a CI job or preservation integrator may hold a powerful key. Give that key a named owner, store it outside the repository, rotate it on staff or vendor changes, and review recent actions. Avoid sharing one key across scripts.
Preservation systems often hold restricted material. Accession records, donor agreements, personal information and embargoed files may not belong in a public finding aid. Review the metadata export paths and the object download URLs, not only the Dashboard page. A public preservation index or thumbnail can disclose the existence of a collection even when the package itself is protected.
Availability is a security property for preservation. A dashboard exposed to the internet increases the chance of credential attacks, automated scanning and accidental configuration changes. Restrict administrative access to a trusted network or identity-aware proxy, monitor failed logins, and test restoration of the configuration as well as the content. An outage in the control plane may stop preservation processing even when the stored packages remain intact.
The 1,061 title matches are a candidate set, not a list of exposed archives. An owning organization should confirm the service, map Dashboard and Storage Service endpoints, and compare anonymous, staff and administrator behavior. Archivematica protects digital material over long periods. Its own administrative path needs the same care as the collections it preserves.
Top comments (0)