Bug 27590 - Self-created MARC-Framework deletes content containing german special characters
Summary: Self-created MARC-Framework deletes content containing german special characters
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: 20.11
Hardware: PC Linux
: P2 normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-02 05:09 UTC by braun.kamilla
Modified: 2021-12-13 21:10 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:


Attachments
Self-created MARC-framework (16.62 KB, application/vnd.oasis.opendocument.spreadsheet)
2021-02-02 05:09 UTC, braun.kamilla
Details

Note You need to log in before you can comment on or make changes to this bug.
Description braun.kamilla 2021-02-02 05:09:32 UTC
Created attachment 116183 [details]
Self-created MARC-framework

For the purpose of fast manual cataloging, I created a small MARC-framework, containing only a few important fields. (see attachment)
Using this framework for cataloging (creating new records) all content containing german special characters (i.e. äöüÄÖÜß) will be deleted or somehow changed.
If the same record is beeing imported via the Z39.50-interface, the german special characters are accepted.
Comment 1 Katrin Fischer 2021-02-02 07:38:13 UTC
Usually this is a configuration issue. The LDR contains a position declaring the encoding of the record. If that is missing, things will go terribly wrong, like you describe.

It's LDR Pos. 9 - it needs to be set to a.
https://www.loc.gov/marc/bibliographic/bdleader.html

Maybe the default value in the framework doesn't work quite right.

Please note: Fields that are deleted from the framework will be lost in records imported from external sources once they are saved for the first time. Koha will delete all fields/subfields not declared in the framework. For this reason it can make sense to only hide, not remove, the fields unneded.
Comment 2 braun.kamilla 2021-02-04 08:40:48 UTC
Thank you for the hint. :-)
Comment 3 Katrin Fischer 2021-02-06 19:51:59 UTC
You are welcome :)