Details
-
Type:
New Feature
-
Status: In Refinement (View Workflow)
-
Priority:
P3
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Template:
-
Epic Link:
-
Development Team:None
-
Calculated Total Rank:
-
Kiwi Planning Points (DO NOT CHANGE):15
-
PO Rank:10
-
PO Ranking Note:It would be the right thing to do (separate pwd from pin) in the long run
-
Rank: Chalmers (Impl Aut 2019):R2
-
Rank: Chicago (MVP Sum 2020):R5
-
Rank: Cornell (Full Sum 2021):R5
-
Rank: Duke (Full Sum 2021):R5
-
Rank: 5Colleges (Full Jul 2021):R5
-
Rank: GBV (MVP Sum 2020):R5
-
Rank: Grand Valley (Full Sum 2021):R4
-
Rank: Lehigh (MVP Summer 2020):R5
-
Rank: Leipzig (Full TBD):R1
-
Rank: MO State (MVP June 2020):R2
-
Rank: TAMU (MVP Jan 2021):R5
-
Rank: U of AL (MVP Oct 2020):R5
Description
Many libraries require PIN code as an additional patron validation. If the numeric PIN is stored in the password field and a patron attempts to change their PIN, password validation rules would not allow the password to be numeric only and would force the patron to make the PIN alphanumeric. PINs are often used as a validation in self-checkout kiosks. If the kiosk is configured to use numeric PIN, the patron after the change of their PIN will not be able to use the self-checkout kiosks.
TestRail: Results
Attachments
Issue Links
- blocks
-
-
- Blocked
-
- is defined by
-
MODUSERS-254
Implement back-end-only field to store patron PIN (for SIP2 integration)
-
- In QA
-
- relates to
-
SIP2-89
Implement patron PIN field instead of patron password field
-
- Draft
-
