CSV templates
Main Page > Resources > Resources/CSV templates
On this page you will find copies of the CSV templates we provide for use when importing data into AtoM. As the CSV files change over versions, we will add sections, so that you can be sure you are using the right template for your AtoM installation.
For more information on CSV import, see the Import/Export section of our User manual. Links directly to each major release's CSV import documentation are included in the relevant sections below.
Tip
Did you know you can also find all the CSV import templates inside AtoM? They are located in lib/task/import/example
.
See Also
Migrating data to AtoM? Check out the CSV transformation page for information on transformation scripting!
Page organization
This page has been divided first by type and then by release.
If there are no changes to the CSV templates for a major release, a link or section will not be included - you can then use the templates from the previous release. Be sure to review the CSV import documentation in the AtoM User manual for your release.
Contents
Archival descriptions
Below you'll find copies of the CSV template examples for archival descriptions, organized by each major release. A change log is included so that you can quickly determine what has changed.
At this time, we provide templates for the ISAD(G) and RAD descriptive templates in AtoM. If you are using a different content standard (e.g. DACS, DC, or MODS), we recommend using the ISAD(G) template and ignoring any fields that do not crosswalk. Information about crosswalk mappings can be found in the Data Entry / Templates section of the AtoM User manual.
AtoM 2.3 CSV templates
Important
The AtoM 2.3 release includes CSV export functionality. During roundtrip testing, it was discovered that events which were not "creation" were not properly roundtripping (e.g. exporting and re-importing properly). Consequently, to better support users importing and exporting data about events and actors who are not creators (but might be accumulators, manufacturers, broadcasters, etc), major changes have been made to the 2.3 CSV template relating to actors and events. This means that 2.2 and earlier CSV templates may no longer import properly. Please see the 2.3 CSV import documentation for further guidance.
Change log
- Changes to how Actors and events (e.g. creators, creation events, etc) are implemented to better support roundtripping of non-creation events (e.g. accumulation, broadcasting, etc)
-
creators
,creatorHistories
,creationDates
,creationDatesStart
, andcreationDatesEnd
columns removed -
eventActors
,eventActorHistories
,eventTypes
,eventDates
,eventDatesStart
, andeventDatesEnd
columns added to replace previous columns - In RAD template,
eventDescriptions
replacescreationDateNotes
, andeventPlaces
has been added
-
- Added new
genreAccessPoints
column to support genre access points - see issue #9390 - Removed duplicate column
radNoteOnPublishersSeries
- see issue #9762 - Updated the sample data for better mapping to related standards fields - see issue #10070
Templates
AtoM 2.2 CSV templates
Change log
- Change
creatorDates
column header and related columns labels tocreationDates
- see issue #6526 - Add new columns to allow import of
alternativeIdentifiers
andalternativeIdentifierLabels
- see issue #7388
Templates
AtoM 2.1 CSV templates
Change log
-
digitalObjectURI
anddigitalObjectPath
columns added for importing digital objects with archival descriptions - see issue #6525 - Cast, Credits, and Signatures columns added to RAD CSV template - see issue #7130
Templates
AtoM 2.0 and earlier CSV templates
These archival description CSV templates should work for AtoM 2.0.0, 2.0.1, 2.0.2, and any earlier version of ICA-AtoM that supports CSV import.
Templates
Accessions
AtoM 2.6 CSV templates
Change log
- new
donorNotes
column added - Other changes to import behavior:
- Previously, new terms in the
resourceType
oracquisitionType
columns would trigger an error and halt the import. Now, they will be added to the related taxonomy - When a duplicate accessionNumber is encountered during an import, the console log will now include the accession number of the conflict for reference
- Previously, new terms in the
Templates
AtoM 2.3 CSV templates
Change log
- Changes to actor/event handling columns in Accessions CSV template:
- Removed
creationDates
,creationDatesStart
,creationDatesEnd
andcreationDatesType
- Added
eventDates
,eventDatesStart
,eventDatesEnd
. andeventDatesEnd
- Removed
Templates
AtoM 2.2 CSV templates
Change log
- Add 4 new columns to Accessions CSV import template to allow for creation date imports - see issue #8463
Templates
AtoM 2.1 CSV templates
Change log
- Add
qubitParentSlug
to accessions CSV import to allow accessions import to link to existing descriptions - see issue #6752 - Add
identifier
as an option for the second column in the digital object CSV import task - see the related documentation here.
Templates
AtoM 2.0.0 and earlier CSV templates
The following CSV templates should work for AtoM 2.0.0, 2.0.1, and 2.0.2, as well as any previous ICA-AtoM release that supports CSV import.
Templates
Deaccession records
Below you'll find copies of the CSV template examples for deaccession records, organized by each major release. A change log is included so that you can quickly determine what has changed. The ability to import deaccession records via CSV was first introduced in the AtoM 2.5 release.
Templates
Authority records
In AtoM, there are 3 CSV templates for importing authority records - a primary template, as well as two optional secondary templates that can be imported at the same time (when using the command-line only) to add further forms of name (the Aliases CSV), or relationships between actors (the Relationships CSV).
These two supplementary AtoM authority record CSV templates have not changed since AtoM 2.0.0, and should work for any AtoM or ICA-AtoM release that supports CSV import. Note that currently the aliases and relationships CSV templates can only be imported via the command-line.
In the 2.4 release 2 new fields were added to the primary authority records CSV template, to support the import and export of Occupation access point data.
See Also
See the latest CSV import documentation here.
For instructions on importing the supplementary authority record CSVs, see the command-line import documentation here
AtoM 2.5 CSV template
Change log
- Add 2 new fields to the actor CSV import template for
subjectAccessPoints
andplaceAccessPoints
. For more details, see issue #12647.
Template
AtoM 2.4 CSV template
Change log
- Add 2 new fields to the actor CSV import template for occupations data:
actorOccupations
andactorOccupationNotes
. For more details, see issue #11081.
Template
AtoM 2.0 CSV templates
The primary authority record template found below should work with all releases up to version 2.3. The Aliases and Relationships CSV templates should work for command-line imports on all versions of AtoM.
Templates
- 2.0 Authority record CSV template
- 2.0 Authority record aliases CSV template
- 2.0 Authority record relationships CSV template
Archival Institutions
CSV import and export for archival institutions (aka repository records) was introduced in the 2.4 release.
Important
There was a bug in the 2.4.0 release that prevented some fields from importing and exporting in the archival institution CSV. This has been fixed in the 2.4.1 bug fix release. For more details, see issue #10853.
Templates
Events
The AtoM events CSV templates have not changed since AtoM 2.0.0. The following CSV templates should work for any AtoM or ICA-AtoM release that supports CSV import.
Templates
Digital objects
It is possible to link digital objects to existing descriptions using a CSV template, but we do not provide an example template because the format is very simple. For further information, please see the relevant section in the CSV import documentation: