Compatibility

Exports into the systems the sector already runs.

Archivers.ai is not a repository, a collections management system or a preservation platform. It sits in front of them and exports into them.

The profile for your instance is tuned during onboarding

Current profiles

Three families of downstream system.

Each one is a profile you pick from a menu in the app, not a one-off build.

Archives and finding aids

ISAD(G) fields, hierarchy and access conditions preserved through the mapping.

  • AtoM description template CSV
  • ArchivesSpace resource and object CSV
  • EAD3 XML for standards-based services
  • CALM CSV with former-reference concordance

Museums and mixed collections

Spectrum-mapped CSV, tuned to your institution’s own field conventions.

  • Axiell Collections and EMu
  • Modes-compatible field layouts
  • Adlib and Mimsy XG deployments
  • Plain CSV for anything else

Preservation and packaging

BagIt packages with checksum manifests and PREMIS provenance for ingest.

  • Preservica ingest workflows
  • Archivematica transfer metadata
  • Generic BagIt to RFC 8493
  • SHA-256 manifests and bag-info provenance
A completed Archivers.ai accession listing reviewed items above an export panel offering a PDF report, BagIt, and catalogue exports for EAD3 XML, AtoM CSV, ArchivesSpace CSV and Archivematica CSV
In the product

Picked from a menu, not built to order.

The systems on this page correspond to export options in the app. Your instance is tuned during onboarding, then tested.

  • Round-trip tested on a staging instance
  • Profile documented for audit and handover
  • Open formats only, so nothing is stranded
All export formats
Common questions

If your system is not listed.

Our downstream system is not on the list.

If it ingests EAD3, Dublin Core, BagIt or CSV, a profile can be agreed during onboarding. If it is bespoke, tell us what it expects and we will work out the mapping.

Can we harvest the catalogue directly?

Published collections are harvestable over OAI-PMH, which serves Dublin Core, and viewable in any IIIF Presentation v3 viewer. The Standards page states where each has a limit.

Do you migrate us off our current system?

No. Archivers.ai works alongside your system of record. The one migration workflow we do run is from CALM, using CALM’s own CSV and EAD exports.

Tell us which system you need to feed.

We will walk through the mapping with you. Or start free and try an export on your own material first.