https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23532
Andreas Roussos <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|19.05 |master CC| |[email protected] --- Comment #1 from Andreas Roussos <[email protected]> --- I managed to reproduce this: the current master I used was aa178bc. In C4/Heading/MARC21.pm, the variable $bib_heading_fields is hardcoded. Under the 'DATA STRUCTURES' heading there's actually a comment that reads: "FIXME - this should be moved to a configuration file." C4/Heading/UNIMARC.pm uses a different approach, where the same variable is populated from the results of a SELECT statement on the marc_subfield_structure table. In my case, to work around this problem, I had to do the following: 1) modify C4/Heading/UNIMARC.pm as per below: - '650' => { auth_type => 'TOPIC_TERM', subfields => 'abvxyz', subject => 1 }, + '650' => { auth_type => 'TOPIC_TERM', subfields => 'abcdegvxyz', subject => 1 }, 2) add subfields $c/$d/$e to the MARC framework subfield structure of field 150 for the TOPIC_TERM authority type. Then, all subfields entered in tag 650 while adding a biblio in the Cataloging module were copied to tag 150 of the new authority that was created automatically. But, what should we do to fix this issue for the general case? Could we follow the same approach as for UNIMARC, and populate the $bib_heading_fields variable from SQL data? Or do we need a separate configuration file for this? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
