Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems (UXPROD-2598)

[UXPROD-3040] INN-Reach: Support PIN-based verification for Patrons Created: 12/Apr/21  Updated: 23/Feb/23  Resolved: 23/Feb/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems

Type: New Feature Priority: P4
Reporter: Brooks Travis Assignee: Tim Auger
Resolution: Won't Do Votes: 0
Labels: consortia, inn-reach
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-1811 Implement patron PIN number as separa... In Refinement
Defines
is defined by MODINREACH-31 Add PIN Support to Patron Verificatio... Draft
Epic Link: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems
Front End Estimate: Out of scope
Back End Estimate: Large < 10 days
Development Team: Volaris
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R5
Rank: MO State (MVP June 2020): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem:
The INN-Reach specification support the option to verify patrons using an optional PIN/Password. This setup should be supported in FOLIO using a PIN field on the user record ( UXPROD-1811 In Refinement )

In scope

  • Verify PIN provided by patron via INN-Reach verify patron call matches PIN for the user matching the provided name and publicId values.

Out of scope

  • Adding a PIN field to Users

Use case(s)

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Tim Auger [ 02/Jan/23 ]

Until we know the extent of our contractual obligation, putting this on ice.

Generated at Fri Feb 09 00:28:52 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.