[Koha-bugs] [Bug 33669] New: Adding options to ApplyFrameworkDefaults preference

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed May 3 20:40:40 CEST 2023


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

            Bug ID: 33669
           Summary: Adding options to ApplyFrameworkDefaults preference
 Change sponsored?: ---
           Product: Koha
           Version: 22.05
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Cataloging
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: noemie.labine at collecto.ca
        QA Contact: testopia at bugs.koha-community.org
                CC: m.de.rooy at rijksmuseum.nl

Hi ! 

>From bz29146 and bz30250, a few changes have been made to enhance the way
framework default values are applied in a record. But the changes made makes it
impossible for someone to add quickly default values to a record they are
editing since default values are applied only when a record is created.

Before, when we saved a record, every empty field and/or subfield that had
default values in the framework would get populated. Of course that was not
ideal as someone could want to keep one of those field empty. But right now, if
we edit a record, there is no way to populate those field...

So I think a great way to keep the inhancement from 29146/30250 but to also
have the option to add default values when editing a record (not only when
creating one) would be to add two more options to ApplyFrameworkDefaults
preference :

 - When repeating a field
 - When repeating a subfield


This way, if my framework has a default value in field 336, for exemple, and I
edit a record that has an empty 336 field, I could only use the "repeat this
field" button to have a 336 field populated with my default values. The empty
336 would simply disappear when saving my record.

And it would be the same for the subfield option, but having the two separated
allows a bit more flexibility if a library wants to have default values when
adding a complete field but not if they only repeat a subfield and vice versa.

Thank you !

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


More information about the Koha-bugs mailing list