Bug 33669 - Adding options to ApplyFrameworkDefaults preference
Summary: Adding options to ApplyFrameworkDefaults preference
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 22.05
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-03 18:40 UTC by Noémie Labine
Modified: 2023-11-09 12:08 UTC (History)
4 users (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 Noémie Labine 2023-05-03 18:40:40 UTC
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 !
Comment 1 Mark Hofstetter 2023-11-09 12:08:28 UTC
please see

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

if this would help you