Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1811

Implement patron PIN number as separate password field (authentication token) for circulation

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Development Team:
      None
    • Calculated Total Rank:
      21
    • 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

            New Feature - New feature requests UXPROD-3040 INN-Reach: Support PIN-based verification for Patrons

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Blocked
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODUSERS-254 Implement back-end-only field to store patron PIN (for SIP2 integration)

            • TBD - To be determined
            • Open
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-89 Implement patron PIN field instead of patron password field

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Draft
            mentioned in

            Page Loading...

            Page Loading...

              Activity

                People

                Assignee:
                pwanninger Patty Wanninger
                Reporter:
                magdaz Magda Zacharska
                Votes:
                0 Vote for this issue
                Watchers:
                14 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases