Bug 41221

Summary: Ability to choose or disable the populated 773 data when creating a child record
Product: Koha Reporter: Angela Berrett <angela.berrett>
Component: CatalogingAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: esther.melander, m.de.rooy
Version: 25.05   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Bug Depends on: 39545    
Bug Blocks:    
Attachments: 773$w generated data: 003+001

Description Angela Berrett 2025-11-07 18:04:53 UTC
Created attachment 189367 [details]
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?