Bug 19111 - Do not mess with kohafield in authority_subfield_structure
Summary: Do not mess with kohafield in authority_subfield_structure
Status: ASSIGNED
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Marcel de Rooy
QA Contact: Testopia
URL:
Keywords:
: 31704 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-08-15 13:52 UTC by Marcel de Rooy
Modified: 2023-06-11 15:50 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel de Rooy 2017-08-15 13:52:43 UTC 
Please see also bug 10306 and dependencies.
In Koha we are using kohafield in auth_subfield_structure only for the link between authid and 001, as well as authtypecode and 942a.
We do not have any further "kohafield functionality" as on the biblio side for additional fields like title, author, etc. (There is no authority counterpart for transform marc to koha, etc.)
Sub GetAuthMARCFromKohaField is only called a few times (once in AuthoritiesMarc.pm and twice in authorities.pl). In e.g. SearchAuthorities, GuessAuthid, AddAuthority, etc. 001 is hardcoded.

This actually means that you should really NEVER change the "kohafield" mapping in the Subfield structure of Admin/Authority types for 001 and 942a. 
I would propose here to disable the kohafield for editing on the subfield structure form (just as on bug 19096), and at least add some comments to GetAuthMARCFromKohaField.
Comment 1 Katrin Fischer 2023-06-11 15:50:50 UTC 
*** Bug 31704 has been marked as a duplicate of this bug. ***