Skip to main content

Export Formats

Settings → Exports → Formats lists the export formats your organisation can produce. You can toggle individual formats on or off, and customise the mapping between your data model fields and each format's elements. A format switched off here is not offered anywhere in the workspace — but a complete copy of your own material can never be switched off.

Exports settings


Available formats​

FormatStandardTierBest for
CSV—Community+Spreadsheet review, simple data extracts
PDF—Community+Formatted catalogue, researcher-facing finding aid
JSON—Starter+Programmatic consumption, custom workflows
Markdown—Starter+Quick human-readable export, GitHub Pages publishing
EAD3EAD3Starter+National archival aggregators, archives-to-archives transfer
EAD 2002 XMLEAD 2002Starter+The Archives Hub and other UK archival catalogues
Archives Hub sheetArchives Hub spreadsheetStarter+The Archives Hub as a ready-to-upload Excel file
Dublin Core XMLDublin CoreStarter+Libraries, repositories, Europeana
MODS XMLMODSStarter+A rich single-object description, offered on an individual item
AtoM CSVAtoMStarter+AtoM (Access to Memory) installations
ArchivesSpace CSVArchivesSpaceStarter+ArchivesSpace import
Archivematica CSVArchivematicaStarter+Preservation workflows feeding Archivematica
Spectrum CSVSpectrum 5.1Starter+UK museum collections management systems
CALM CSVAxiell CALM (tabular)Starter+Flat one-row-per-record sheet for CALM's tabular import, with a former-reference concordance column so old references survive alongside newly minted ones
BagItBagItStarter+Digital preservation transfers, OAIS submission
Package listBagItStarter+Every file in a collection with its details, its fingerprint and a link that opens it

Alongside these, the collections tree offers the TNA Discovery workbook (.xlsx) — a guided, checked export for Manage Your Collections at The National Archives. It has its own route and its own permission: Reviewers can produce it as well as Admins and Members.

CSV and PDF are available on all plans. Everything else needs Starter or above; on Community those buttons are disabled and say so rather than failing when pressed.


Validation and mandatory fields​

Some destinations require certain fields to be present. Check before you send — on the accession export panel, and in the export dialogs — runs the records you've selected against the destination's own rules and names the ones that would arrive incomplete. It describes; it never blocks.

If gaps are found, the check lists which records and fields are missing, with the line "Fix these and check again, or send anyway — the gaps stay blank."

  • Fix the gaps first — edit the records in Archivers.ai to fill in the missing data, then check again
  • Send anyway — proceed with the export and leave the gaps blank in the file. Downstream systems (like TNA Discovery) may then flag the missing data, or you can fill it in directly in the exported spreadsheet.

Missing fields are blank in the exported file — the system never invents values. Use the "Export anyway" option when you want to export a work-in-progress or when you prefer to complete the spreadsheet offline.

Archives Hub (EAD 2002) requirements​

The Archives Hub requires your workspace to be configured with an ARCHON code (your archive's national code) and a country code before you can export an EAD 2002 file. Set these under Settings → Numbering → Your archive's code.

When exporting to the Archives Hub, the check also verifies that the collection record itself has the nine fields the Hub requires at the top level: a reference, title, dates, level of description, extent, repository name, scope and content, access conditions, and language. The check will list any that are missing and link you to the collection's description page to fill them in.


Where to export from​

FromWhat's exported
An accession — the Accession export · transfer manifest panel at the foot of the accession pageWhat arrived in this accession — the records-management view. PDF Report and BagIt sit at the top; EAD3, AtoM, ArchivesSpace, Archivematica and Spectrum under Catalogue; CSV, JSON, Dublin Core XML and Markdown under Other formats
A collection — the collections treeA multilevel finding aid across the whole fonds, with items at their actual placement, from every accession. You choose the format and how deep to go
A dossier — Export button on the dossier detail pageThe dossier's items, with analysis if present
An item — Export on the item recordDublin Core XML, MODS XML, or a single CSV row
Search results — Select + ExportJust the selected items
Settings → Exports → DownloadsA finding aid, or a complete copy of the whole workspace

The accession register has its own Export CSV button above the table, next to Choose columns and Import register.

The statutory accession register with the Export CSV button in the toolbar above the table

Small exports download straight away. The large ones — a finding aid, or a complete copy of the workspace — are made in the background and appear on Settings → Exports → Downloads when ready, with the download link also emailed to you. Links last seven days.

Removing an export​

A Remove button sits next to each finished export on the Downloads panel. Use it to delete an export immediately — you don't need to wait for the seven-day link expiry. This is most useful when:

  • An export contains personal data that has since been erased or anonymised elsewhere
  • You've exported a sensitive query you want to take away from the downloads list at once
  • A download is no longer needed and you'd rather not wait

Removing an export deletes the download link and the stored file both; it is instant and cannot be undone. The removal is recorded in Settings → Exports → Activity.

A complete copy takes everything out of the platform in a re-importable form — all records, all levels, all files, all authorities. It's admin-only, and it's the one export that can never be switched off.

Note on public destinations​

EAD 2002 (Archives Hub) and Archives Hub sheet are public destinations — the files go onto a searchable national catalogue. For this reason, the exports filter out:

  • Collections, accessions and records marked as closed or restricted
  • Anything not published on your public portal
  • Any material whose accession has a draft status

If your collection contains material you want to keep private, publish only the open items to the Archives Hub by marking sensitive records and collections appropriately before export. The check will show you how many items will be withheld. Both formats require your workspace to have an ARCHON code and country code configured under Settings → Numbering → Your archive's code.


Mappings — customising the field map​

Every format ships with a default mapping from your Data Model fields to the format's elements. Admins can override these per-organisation.

  1. Settings → Exports → Formats.
  2. Click Mappings next to a format. A drawer opens listing every mapping as a pair: your field key on one side, the format's target element (and namespace) on the other.
  3. Edit a row, or add one, setting the field key, the target element, an optional namespace, and a render hint for fields that can hold more than one value — repeat, join_pipe, join_semicolon_nospace or first_only.
  4. Save. Rows you've changed are marked as your organisation's overrides, and Reset to defaults puts the whole format back the way it shipped.

The mapping applies to every subsequent export in that format.


Round-tripping​

Records exported from Archivers.ai can be brought back in through the import wizard, and the complete copy is designed for exactly that — it is a re-importable copy of everything.

Import Profiles, on its own tab in Settings → Exports, lets an admin name and keep a profile against a format — useful when you repeatedly import the same shape of spreadsheet. A profile has a name and a format; the header mappings behind it aren't editable from this screen yet.

PDF, Markdown, the package list and CALM CSV are export-only — they're presentation or one-way handoff formats, not ingestion formats. For bringing data in from a CALM system, use the import wizard — it recognises common CALM-ish column names (reference, old reference, depositor, accession number, and similar), but this is header auto-detection, not a validated canonical CALM field mapping. Check every mapped column before applying an import from CALM.


Toggle formats on or off​

Not every organisation needs every format. The On toggle next to each format in Settings → Exports controls whether it is offered anywhere in the workspace. Turning a format off doesn't delete past exports; it just removes it from the pickers. A complete copy of your own material is never affected.


Who exported what​

Settings → Exports → Activity (admins only) shows everything that has happened in the workspace, including every export taken — who took it, and when. Entries by people who have since left are kept.


What's next?​