Preserve specification in Merge/Overlay Profiles not working as expected
Bug #1878984 reported by
Dale Rigney
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.12 |
Fix Released
|
High
|
Unassigned |
Bug Description
Tested in Evergreen 3.3 and Evergreen 3.4
When using the MARC Batch Import interface the Preserve Specification field in the Merge profile is not being applied on merged records.
In our test we used a Merge profile that would preserve tag 490. Our marc record in the database had a tag 490$a and the incoming record did not have any 490 tags. We expected the 490$a tag to remain after the merge. The record was merged but tag 490$a was removed.
The Preserve Specification field does work in Evergreen 3.2 (which uses the old style vandelay interface). Evergreen 3.3 and 3.4 uses the new Angular vandelay interface.
tags: | added: van |
tags: |
added: cataloging vandelay removed: van |
Changed in evergreen: | |
assignee: | nobody → Andrea Neiman (aneiman) |
Changed in evergreen: | |
assignee: | Andrea Neiman (aneiman) → nobody |
Changed in evergreen: | |
assignee: | nobody → Jennifer Weston (jweston) |
tags: |
added: needsrepatch removed: pullrequest signedoff |
tags: |
added: needswork removed: needsrepatch |
tags: |
added: cat-batchedit removed: cataloging vandelay |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Confirmed in 3.4