...
Technical documentation for the tool can be found on GitHub: https://github.com/collectionspace/cspace-converter in the tool’s Github repository landing page (scroll down) and wiki.
How to Format CSV Files
Please note that the tool is not forgiving. Your data must be formatted as noted, or the row will fail.
...
Templates and sample data for procedures and authorities can be found in on the Configuration and Data Maps - Cataloging, Procedures, and Vocabularies page on the wiki, or in the Data folder on Github.
| Note |
|---|
The CollectionSpace Converter Tool currently supports only some profiles, record types, and fields. The tool was being developed as-needed to support data migration and batch update work. The spreadsheets in Configuration and Data Maps on this wiki include fields not yet supported by the Converter Tool. For details on field types, appropriate values used in fields, etc., refer to the spreadsheets in the Configuration and Data Maps page on this wiki. |
If you’re not familiar with Github, no problem! It’s a few steps to get the data into a template you can use:
...
Use “Schema Field ID” row as your CSV header. If you’re using the templates from the Data map page linked above, delete the rows above it unless you need them as a guide while editing.
For fields populated by an option list (UI Field Type = Controlled list; static), you must use the values exactly as they appear in the “Schema Option List Default Contents” row. For example, in Object Cataloging - Common, the collection value “permanent-collection” will import as expected. The following would not: “permanent collection” or “Permanent-collection”.
For fields populated by a vocabulary (UI Field Type = Controlled list; dynamic), the CSV value needs to exactly match the value in the “Name” field of the vocabulary. This includes capitalization, spacing, and any included punctuation. (Variations will be imported and will display, but they will not be matched up with/reconciled against the vocabulary, introducing inconsistency in your data)
For fields populated by an authority (UI Field Type will mention authority), the CSV value should exactly match the Display value field of the appropriate authority. If there is a mismatch, the term used in your record will not be connected to the authority as expected and a new term will be created.
Please test a few rows of your data carefully before proceeding with an entire batch! Tips and examples of how to test are available at: Testing your import.
| Info |
|---|
A new version of a CSV import tool is in development, which will support nearly all fields in all record types in all community profiles. For reference, there are CSV templates for this tool currently available here. These templates include columns for data not currently supported by the Converter Tool. |
How to Import and Transfer CSV Files
...