https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22728
--- Comment #17 from Christopher Brannon <[email protected]> --- I'm not seeing this point here, so I will just add to the mix. It DOES seem like it is currently a side-effect. The one problem with implementing this is that it is based off field names, and those names vary, depending on whether some of the patron attributes are used for all libraries. This can cause problems with those libraries that don't use a certain attribute, as it offsets the attribute names. I haven't tested, but this could also be complicated by those attributes that allow more than one instance of the field. Seems like a mandatory setting that can stick to the specific field would be better than trying to make it mandatory through the field name. I would suggest that the mandatory option be unavailable to those fields that can be duplicated, or only make the first instance mandatory? Just some thoughts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
