Releases: collectionspace/collectionspace-mapper
Implement "the bomb"
If a field has a blank value, no node for that field exists in the XML document
returned by collectionspace-mapper. When this XML is uploaded to
update an existing record, only nodes present in the XML affect the
existin record. That is: uploading a CSV without a value for a given
field will NOT cause that field to be blank in existing CSpace
records.
If a field consists of the bomb emoji (https://emojipedia.org/bomb/)
then a blank-value node for that field will be in the XML document
produced by collectionspace-mapper. When this XML is sent to
CSpace to update a record, any existing value(s) in that field will be
replaced with a blank. That is: using the bomb will destroy any
existing content in a field.
Bugfix for mapping many records with same DataHandler
[2.2.5] - 2021-04-22
Added
- CHANGELOG.md
Changed
- BUGFIX: Fixes an issue where, when many records are mapped using the same
DataHandler, some XML records were missing expected elements.
Deleted
- Tests for UCB-specific mapping. These tests had served their purpose, were no longer needed, and were not worth fixing when they started to fail because the dev instance on UCB's end changed or went away.
Details: v2.2.3...v2.2.5
[2.2.4 (Unreleased)] - 2021-03-25
- Updated values in fixtures causing test failures due to records being deleted from CollectionSpace dev instance
Bugfix to stop returning spurious subgroup overflow warnings
Bugfix for errors/warnings in special rectypes
Merge default data in before any validation or processing
For special recordtypes, required fields are provided in defaults hardcoded in the DataHandler. Calling handler.validate on the raw data resulted in errors about missing required fields. Merging any default data in as soon as the data is first prepped into a Response ensures this doesn't happen any more.
See #98
Add mapping for relationships
Adds mapping capability for three relationship types:
- objecthierarchy
- authorityhierarchy
- nonhierarchicalrelationship
More warnings, fewer failures
Warn instead of failing when...
- a Client term search returns more than one record matching the term.
- when incorrect delimiting in repeating field subgroups causes
overflow (more subgroups than there are parent groups)
Also warn when subgroup values are uneven
Bugfix for refName wellformedness check
Skips wellformedness check if refname value = %NULLVALUE%
Yet another bug fix for non-cached term search
Merge pull request #93 from collectionspace/client-search-fix use client search directly when term is not cached
Bugfix for TermHandler
Merge pull request #92 from collectionspace/term-handler-search Term handler search fix