[Koha-bugs] [Bug 35135] New: Koha still needs certain leader tags despite removing them from the framework

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35135

            Bug ID: 35135
           Summary: Koha still needs certain leader tags despite removing
                    them from the framework
 Change sponsored?: ---
           Product: Koha
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Cataloging
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: esther.melander at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org
                CC: m.de.rooy at rijksmuseum.nl

Created attachment 157680
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=157680&action=edit
Example records to use with the CSV2MARC plugin

This is perhaps a unique set of circumstances, discovered while utilizing the
CSV2MARC plugin. I have not tried to replicate this outside of the plugin.

To recreate:
1. Create a framework called CSV2MARC by duplicating the Default framework but
remove 000, 001, 003, 005, and 008 tags.
2. Create the CSV file.
3. Configure the plugin, matching the columns in the CSV file.
4. Stage and import the file selecting CSV as the format and CSV2MARC as the
Framework.
5. Look at the detail view of the imported record and see that it has imported
correctly.
6. Edit the record (do a minor edit like adding punctuation to a field) and
save.
7. Look at the detail view of the imported record again and see that there is
data loss.

Now import the same record via z39.50. See that it imports correctly. Edit and
save the record and see that all of the data for the record is retained. The
z39.50 import uses the Default framework with the tags referenced above.

The workaround was to correct the CSV2MARC framework and add back the 000, 001,
003, 005, and 008 tags, but mark the tag and subfields as not required. The
CSV2MARC configuration and import works better by not trying to bring in the
leaders (iow, its easier not to).

If the ability exists to delete the tags in the framework and import a record
with that framework, then there should not be data loss when editing and
saving. Since these leader tags are important, at least as a space holder, then
the ability to delete them in the framework should be disabled or a warning
provided.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.