https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41221 Bug ID: 41221 Summary: Ability to choose or disable the populated 773 data when creating a child record Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: angela.berrett@familysearch.org QA Contact: testopia@bugs.koha-community.org CC: m.de.rooy@rijksmuseum.nl Depends on: 39545 Created attachment 189367 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189367&action=edit 773$w generated data: 003+001 Bug 39545 improved data population from the Parent serial record into the 773 field when a new child record was created. Some of this data is not needed for some libraries, some is in a format that does not work. Can this be a feature that can be fully turned off using a SysPref? A more specific request: Whether intentional or not with that enhancement, the 773$w field is populated not only with the 001 of the parent record, but also with the 003. The 003 (an alphabetical code) messes up the export of the 773$w data via OAI-PMH, as only a number (001) is expected, and throws errors. Can we use a SysPref to decide which exact parent fields will populate in each 773 child field? Or at least remove the 003 from the 773$w right now? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39545 [Bug 39545] Construct more complete 773 content when creating a child record -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.