Bug 30795 - Configure unwanted and mandatory borrower fields based on patron category
Summary: Configure unwanted and mandatory borrower fields based on patron category
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement with 2 votes (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-17 23:16 UTC by David Cook
Modified: 2022-05-19 03:24 UTC (History)
3 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 David Cook 2022-05-17 23:16:03 UTC
It would be nice if there were a way to specify different unwanted and mandatory fields based on patron category (rather than enforcing 1 rule for all different patron categories).

At the moment, I see libraries putting in junk data (like '-' or 'N/A') to get around mandatory field requirements where it doesn't make sense for certain patron categories.

It makes sense to have a default rule for these fields, and then individual patron categories could be overwritten with more specific rules. 

--

I suppose the difficulty at the moment is that we don't choose a patron category until we're already on the add patron screen. 

Maybe we should be making it a multi-step process. That would have its pros and cons of course. 

Actually, this reminds me of another thought I've had where we could standardize CRUD forms... but I'll open another bug for that...
Comment 1 Fridolin Somers 2022-05-19 03:24:58 UTC
+1
Makes sens