Consortia (Cross Tenant) (UXPROD-794)

[UXPROD-798] Can load patron information from multiple sources (1+ per consortial member) with conflicts/errors (both across consortium members and with a single consortium member) reported for manual resolution Created: 05/Jun/18  Updated: 04/Nov/22

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

Type: New Feature Priority: P3
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)
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): R5
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): R4
Rank: Leipzig (ERM Aut 2019): R5
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

Description:
Can load patron information from multiple sources (1+ per consortial member) with conflicts/errors (both across consortium members and with a single consortium member) reported for manual resolution

Notes:
need to avoid ID conflicts and patron duplication in both pooled patrons (multi-libs-per-instance and in separated patron dbs) single-library-per-instance)

Central loading for system users:
1. IT lockdown requires some to load and update centrally.
2. Different from patrons (borrower update from student management system).
3. Super user access a need as well.
4. A cataloger might have access to multiple libraries.



 Comments   
Comment by Hkaplanian [ 04/Jun/19 ]

Can't Folio can do this today? If not, what issues make this not possible?

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