search

collectionspace / collectionspace-mapper

MIT License
0 stars 0 forks source link

Data containing terms not in CS should block ability to transfer #133

Closed kspurgin closed 2 years ago

kspurgin commented 2 years ago

Currently, if I import publishTo: all, I will get a warning that this term does not exist in CollectionSpace, but I can still import the data.

If I import the data ignoring that warning, the refname used will be: 

urn:cspace:core.collectionspace.org:vocabularies:name(publishto):item:name(all)'all'

The refname for the All term that already exists is: 

urn:cspace:core.collectionspace.org:vocabularies:name(publishto):item:name(all)'All'

If user later tries to create the term all in the UI, the shortID assigned will not be all, so there can never be a refname match.

This situation should block me from importing data that will create problems in my CS instance