Consortia (Cross Tenant) (UXPROD-794)

[UXPROD-805] Needs to support multiple IDs per patron, with at least one ID field not needing to be unique Created: 05/Jun/18  Updated: 08/May/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Consortia (Cross Tenant)

Type: New Feature Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: suppress-from-capplan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Requires
is required by UXPROD-795 Patrons can borrow/request/hold/recal... Open
Epic Link: Consortia (Cross Tenant)
Kiwi Planning Points (DO NOT CHANGE): 1
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R5
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R4

 Description   

Description:
Needs to support multiple IDs per patron, with at least one ID field not needing to be unique

Notes:
multiple is necessary, one being non-unique is nice to have? Ability to configure on at least one ID whether it needs to be unique or not a la Aleph



 Comments   
Comment by Kelly Drake [ 12/Jun/19 ]

Need clarification - might not even be necessary or covered by other patron features.

Comment by Tim Auger [ 08/May/23 ]

Dennis Bridges Interesting. I can see this becoming an issue with some consortia but I don't see a rush for our first couple of implementations. 

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