Bug 28335 - Making patron attributes required can cause issues in multi branch systems
Summary: Making patron attributes required can cause issues in multi branch systems
Status: RESOLVED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-12 16:46 UTC by Lisette Scheer
Modified: 2023-07-01 09:17 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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lisette Scheer 2021-05-12 16:46:15 UTC
Patron attributes can be marked as required using patron_attr_2 etc. 
The problem with this is in a multi branch system where there are different attributes at different branches, making specific attributes required behave differently on different patron entries. 

Currently my branch has 4 patron attributes, 2 of which we'd like to make required. 

Some branches in the system only have 3 attributes and no one wants the last attribute to be required. 

We can't change the order without replacing the auth value since they sort by code. 

It would be better if we could force requirement based on the code rather than the patron_attr_2.
Comment 1 Katrin Fischer 2023-07-01 09:17:07 UTC
Patron attributes can now be marked as required on their own configuration page. As we no longer rely on the order this should resolve the issue.