Difference between revisions of "Resources/CSV templates"

From AtoM wiki
Line 100: Line 100:
  
  
−
==Accessions CSV templates==
+
==Accessions==
  
 
===AtoM 2.3 CSV templates===
 
===AtoM 2.3 CSV templates===
Line 161: Line 161:
  
  
−
==Authority record CSV templates==
+
==Authority records==
  
 
The AtoM authority record 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.
 
The AtoM authority record 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.
Line 175: Line 175:
 
* [[media:example_authority_record_relationships-2.0.csv|Authority record relationships CSV template]]
 
* [[media:example_authority_record_relationships-2.0.csv|Authority record relationships CSV template]]
  
−
==Events CSV 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.
 
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.
Line 187: Line 187:
 
* [[media:example_events-2.0.csv|Events CSV template]]
 
* [[media:example_events-2.0.csv|Events CSV template]]
  
−
==Digital object CSV template==
+
==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:
 
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:

Revision as of 14:07, 22 June 2017

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.

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, and creationDatesEnd columns removed
    • eventActors, eventActorHistories, eventTypes, eventDates, eventDatesStart, and eventDatesEnd columns added to replace previous columns
    • In RAD template, eventDescriptions replaces creationDateNotes, and eventPlaces 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

Seealso

See the 2.3 CSV import documentation here.

Templates

AtoM 2.2 CSV templates

Change log

  • Change creatorDates column header and related columns labels to creationDates - see issue #6526
  • Add new columns to allow import of alternativeIdentifiers and alternativeIdentifierLabels - see issue #7388

Seealso

See the 2.2 CSV import documentation here.

Templates

AtoM 2.1 CSV templates

Change log

  • digitalObjectURI and digitalObjectPath 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

Seealso

See the 2.1 CSV import documentation here.

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.

Seealso

See the 2.0 CSV import documentation here.

Templates

Accessions

AtoM 2.3 CSV templates

Change log

  • Changes to actor/event handling columns in Accessions CSV template:
    • Removed creationDates, creationDatesStart, creationDatesEnd and creationDatesType
    • Added eventDates, eventDatesStart, eventDatesEnd. and eventDatesEnd

Seealso

See the 2.3 CSV import documentation here.

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

Seealso

See the 2.2 CSV import documentation here.

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.

Seealso

See the 2.1 CSV import 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.

See Also

See the 2.0 CSV import documentation here.

Templates

Authority records

The AtoM authority record 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.

See Also

See the 2.0 CSV import documentation here.

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.

See Also

See the 2.0 CSV import documentation here.

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:


Retrieved from "http://wiki.accesstomemory.org/index.php?title=Resources/CSV_templates&oldid=1692"

Account

Page

Search