The Value Source Type and Value Source for your field are noted in Rows 6 & 7 of the GitHub-generated import template. If the Value Source Type and Value Source fields have values in them other than N/A, the data in the field comes from a controlled source such as a pick list or authority. Option lists are static pick lists in CollectionSpace - those that cannot be edited via the UI. For fields populated by an option list, you must use the values exactly as they appear in Row 7 of the GitHub-generated template, Value Source. For example, in Object Cataloging - Common, the collection value “permanent-collection” will import as expected. The following would not: “permanent collection” or “Permanent-collection”. Vocabularies are dynamic pick lists in Collection - those that can be edited via the UI. For fields populated by a vocabulary, you must use the values exactly as they appear 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). Tip: As every museum may have different terms in dynamic lists, these values are not included in the templates on GitHub. You may wish to add these values to your locally saved version of the template. Critical Tip: You must create new terms in a given vocabulary before importing other records that use those terms. If you use a vocabulary term in a record, and that vocabulary term does not exist in the vocabulary, the CSV Importer will not import the record that uses the missing term. The Processing step will prepare a report of all unique missing terms in a given batch. This report includes the term and what authority or vocabulary the term must be added to.
Authority fields pull data from one or more authorities. For fields populated by an authority , the CSV value should exactly match the Display value field of the term in 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. Tip: If a field is linked to more than one authority, the GitHub-generated template will include multiple columns for that field; for example, acquisitionSourcePerson and acquisitionSourceOrganization. Critical Tip: You must create new terms in a given authority before importing other records that use those terms. If you use an authority term in a record, and that authority term does not exist in the authority, the CSV Importer will not import the record that uses the missing term. The Processing step will prepare a report of all unique missing terms in a given batch. This report includes the term and what authority or vocabulary the term must be added to.
Fields with N/A in the value source type can be formatted according to your local practice.
|