Merge and Overlay Functions should use Merge Profiles
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Wishlist
Evergreen 2.2.5
Postgress 9.1.7
OS: Ubuntu Precise
Currently when merging multiple records within Evergreen or overlaying existing records with new records from a Z39.50 search the lead record is chosen and nothing from the non-lead record(s) is preserved. It would be very useful to have ability to preserve and/or replace certain fields in the MARC record (like when importing MARC records) so that a true merge is performed.
Ideally when you merge or overlay a record you should have to chose a merge profile. These merge profiles would be the same as used in the MARC batch Import/Export (Vandelay).
Existing workflow for merging with modification:
1. Add records to record bucket (http://
2. Click Merge All Records
3. Select the lead record
4. **Select the Merge Profile to be used from the drop down menu (new functionality)**
5. Click Merge
Changed in evergreen: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
tags: | added: cataloging wishlist |
Changed in evergreen: | |
assignee: | nobody → Liam Whalen (whalen-ld) |
Changed in evergreen: | |
assignee: | Liam Whalen (whalen-ld) → nobody |
Changed in evergreen: | |
milestone: | none → 2.12-beta |
Changed in evergreen: | |
status: | Triaged → Confirmed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
I agree that being able to merge fields of the MARC would be really useful, and the Vandelay profiles would be a great starting place. To take it another step it would also be useful if you could select fields from the records not selected as the lead record on a case by case basis for fields where you may not always want to retain them.