Bug 20577 - Script to go through catalogue removing the 998 MARC tag data
Summary: Script to go through catalogue removing the 998 MARC tag data
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-13 02:29 UTC by Alex Buckley
Modified: 2018-12-03 20:04 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
WR: 289187 - Script to loop through catalog removing 998 tag data (2.74 KB, patch)
2018-04-13 02:33 UTC, Alex Buckley
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Buckley 2018-04-13 02:29:05 UTC

    
Comment 1 Alex Buckley 2018-04-13 02:33:44 UTC
Created attachment 74122 [details] [review]
WR: 289187 - Script to loop through catalog removing 998 tag data
Comment 2 Katrin Fischer 2018-04-13 07:03:40 UTC
Hi Alex,

this appears to be very specific, as 998 is a user defined custom field. Can you explain the use case?
Comment 3 Alex Buckley 2018-04-15 06:42:02 UTC
Hi Katrin

Yes I think you're right this patch is not upstreamable as it is too specific. 

The use case that prompted me to write this script is that one of our clients had migrated data across to Koha, and in this migrated data the marcxml contained barcodes in the 998$a MARC subfield. 

As the 998 MARC field is not updated when moving an item from one biblio to another the old biblio (as well as the new biblio) continued to be displayed in search results for the moved items barcode.

Therefore running this script to remove the 998 field stopped this indexing bug from happening. This script could be useful if it was made more generic so a MARC subfield in migrated data could be specified to be removed where it is not necessary or it is causing indexing errors. However I will park this at the moment.

A patch that would be useful to get your feedback on is https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20346 which is fixing the broken patron filtering on the patron page in the intranet as that is quite a major bug. 

Cheers,
Alex