Consortia (Cross Tenant) (UXPROD-794)

[UXPROD-293] Union Catalog support Created: 03/Mar/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: consortia, post-v1, suppress-from-capplan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-1434 Cross-tenant union catalog support Open
Relates
relates to UXPROD-592 Multiple Language and Localization se... Open
relates to UXPROD-592 Multiple Language and Localization se... Open
Epic Link: Consortia (Cross Tenant)
Analysis Estimate: XXL < 30 days
Analysis Estimator: Cate Boerema (Inactive)
Front End Estimate: XXL < 30 days
Front End Estimator: Jakub Skoczen
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Jakub Skoczen
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): R5
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R5
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

Configure a single catalog that allows holdings/items that contain library identifiers that represent all libraries in the collective. The catalog allows libraries and patrons to borrow and transact from each organization and borrowers to determine status in each of the libraries. By default each library can view their own sub-catalog with the option to see holding/item for parts or the entire union.

One option (planned for v1):

  • Multi-institution tenant. Not a cross-tenant feature.
  • Would want to scope permissions to location - current understanding is that permissions are scoped to processing center, but maybe we can change that...
  • What about other metadata elements that might need to differ based on location (e.g. patron group)
  • Workaround might be to give them different logins could even do a kludgey linking of records by extending the proxy linking capabilities
  • First version, patron group will not be location-specific
  • Need to be able to filter inventory and codex by institution location - but location filter is already planned

Option two:

  • Cross-tenant functionality

Per WOLFcon discussion on single-tenant consortia implementation, permission scoping is not required for v1. No other data needs to differ based on location (with the exception of loan policies and patron notices which are both tied to location via loan rules). Some users may have to have >1 user record, but this is okay. Given that, I am marking this feature post-v1. NOTE: It was deemed important, though, that each institution support >1 time zone. I have created a separate feature for this UXPROD-592 Open



 Comments   
Comment by Peter Murray [ 12/Oct/18 ]

Connection to APPIDEAS-13 made during the Consortia SIG call on 10-Oct-2018.

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