Skip to main content

Assigning Accessions to Fonds

Accessions arrive Unassigned by default — they sit in your archive but aren't placed in the hierarchy. Assigning them to a fond, sub-fond, series, or sub-series gives them their permanent home.

Requires the Fonds feature — Professional plans and above.

The single-accession way​

From the accession page, find the fond assignment dropdown directly under the title. By default it shows Unassigned.

  1. Click the dropdown.
  2. Pick a fond, sub-fond, series, or sub-series from the cascading menu.
  3. The accession is moved. The change is instant — no save button.

The new location shows in the dropdown immediately; the accession also appears under that node when you next open the fond.

The bulk way​

From the Accessions list (either card view or table view):

  1. Click Select (card view) or tick the checkboxes (table view) to enter multi-select mode.
  2. Select every accession you want to assign.
  3. Click Assign to fond in the action bar that appears.
  4. A modal opens showing your fonds hierarchy as a tree. Use the filter box to narrow by title or reference code if you have many fonds.
  5. Click the destination fond, series, or sub-series in the tree. The level and reference code appear below the tree to confirm your choice.
  6. Click Assign N accessions.

All selected accessions move together in one operation. Useful when you've been ingesting for a while and want to slot a batch into the hierarchy at once.

To unassign a batch (remove from any fond without assigning elsewhere), select the accessions and click the Unassign from any fond link at the bottom of the modal.

The drag-and-drop way​

From a fond's detail page, when you have its structure open on the left and unassigned accessions on the right, you can drag accessions directly into structure nodes. This is the fastest way when you have an existing hierarchy and a batch of new accessions all destined for different places.

Reassigning​

Same flow as assigning. The dropdown always reflects the current location; pick a new one to move.

Reassignment doesn't lose any item-level metadata — only the accession's position in the hierarchy changes.

What if I haven't built a hierarchy yet?​

Either:

  1. Skip it. Leave accessions Unassigned. Search still works; exports still work. The trade-off is that hierarchical exports (EAD3 finding aids) show your accessions at the top level with no structure around them.
  2. Use AI Organise. The platform can propose a structure based on the accessions you've already ingested. See AI organisation.

Why unassigned accessions still appear in exports​

Unassigned accessions export with parent: null in JSON / CSV exports and as top-level <archdesc> children in EAD3. They're not invisible — they're just unplaced. That's fine for early-stage archives; less fine for finished finding aids.

See also​