...
The data was sent through and is in the under-the-hood XML as shown below. However, it is not formattted formatted properly as a reference to a term list term, so the user interface does not display it.
...
| Code Block |
|---|
<inventoryStatus> urn:cspace:core.dev.collectionspace.org:vocabularies:name(inventorystatus):item:name(accessionstatusunclear)'accession status unclear' </inventoryStatus> |
Fields populated from static dropdown lists (option lists)
The Value Source in the CSV template will be a comma separated list of allowable values.
Sample CSV data:
| Code Block |
|---|
| VALUE SOURCE | | library-collection, permanent-collection, study-collection, teaching-collection |
| CSVHEADER | objectNumber | collection |
|--------------+--------------+---------------------------------------------------------------------------------|
| | 2020.10.14.2 | permanent-collection |
| | 2020.10.14.3 | Permanent-collection |
| | 2020.10.14.4 | permanent collection | |
The collection field value for 2020.10.14.2 will import as expected. The other two rows will not.
What you want to see
Click in the populated field in the imported record. The term list will drop down. You should see a check mark next to the term in the term list.
This is from the record imported for 2020.10.14.2:
...
XML for 2020.10.14.2:
| Code Block |
|---|
<collection>permanent-collection</collection> |
Problem signs
Apparently blank field
The data was sent through and is in the under-the-hood XML as shown below. However, it does not exactly match the key value for the option list, so the user interface does not display it.
XML for 2020.10.14.3:
| Code Block |
|---|
<collection>Permanent-collection</collection> |
XML for 2020.10.14.4:
| Code Block |
|---|
<collection>permanent collection</collection> |