should remove legacy 852s during bib+holdings export

Bug #528424 reported by Galen Charlton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Undecided
Unassigned

Bug Description

When exporting bib records with the option to embed items or retrieving bibs with holdings via SRU & Z39.50, any legacy 852 fields should be removed so that the consumer of the bib records does not have to try to distinguish between legacy or randomly-copy-catalogued 852 fields and those representing current items.

Attached patch implements this. Of course, there could be workflows where the library does want to pass any legacy 852s on to the consumer, in which case we could consider options to retain the legacy 852s or move them to a different field, but that would be better handled by a more general system for specifying export profiles that allow for arbitrary MARC record transformations.

Revision history for this message
Galen Charlton (gmc) wrote :
Revision history for this message
Dan Scott (denials) wrote :

Thanks Galen - applied to trunk. Let's give it a kick in trunk and backport it if all seems well there.

Changed in evergreen:
status: New → Fix Committed
James Fournie (jfournie)
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.