Bug 34239 - Koha-to-MARC mappings silently fails if mapped field/subfield is missing from default framework
Summary: Koha-to-MARC mappings silently fails if mapped field/subfield is missing from...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-09 13:24 UTC by Katrin Fischer
Modified: 2023-07-09 13:29 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

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2023-07-09 13:24:39 UTC
I am a little late noticing maybe, but:

Before we made the default framework authoritative for Koha-to-MARC mappings and removed the option to map in the framework configuratoin pages, you could map uppercase subfields to database fields with no issue.

But now forced to use the Koha-to-MARC mappings page, this is no longer possible. There will be no error, just the mapping is not daved.

Tested with 952 C trying to map to items.permanent_location.
Comment 1 Katrin Fischer 2023-07-09 13:24:54 UTC
There is nothing in the logs afaikt.
Comment 2 Katrin Fischer 2023-07-09 13:29:32 UTC
I was mistaken: the problem appears when the field is only in some frameworks, but not in the default framework. We should not fail silently.