Cross-tenant union catalog support
Description
Priority
P3Fix versions
None
Development Team
None
Assignee
Unassigned
UnassignedSolution Architect
None
None
Parent Field Value
None
Parent Status
None
Checklist
hideTestRail: Results
Activity
Show:
Details
Details
Reporter
Cate BoeremaAnalysis Estimate
XXL < 30 days
Analysis Estimator
Cate BoeremaFront End Estimate
XXL < 30 days
Front End Estimator
Jakub SkoczenFront-End Confidence factor
Low
Back End Estimate
XXL < 30 days
Back End Estimator
Jakub SkoczenRank: FLO (MVP Sum 2020)
R4
Rank: 5Colleges (Full Jul 2021)
R5
Rank: Cornell (Full Sum 2021)
R5
Rank: Chalmers (Impl Aut 2019)
R5
Rank: GBV (MVP Sum 2020)
R5
Rank: hbz (TBD)
R5
Rank: Hungary (MVP End 2020)
R1
Rank: TAMU (MVP Jan 2021)
R5
Rank: Chicago (MVP Sum 2020)
R5
Rank: Leipzig (ERM Aut 2019)
R5
Rank: MO State (MVP June 2020)
R4
Rank: U of AL (MVP Oct 2020)
R5
Rank: Lehigh (MVP Summer 2020)
R4
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created January 16, 2019 at 1:53 PM
Updated November 4, 2022 at 8:23 PM
TestRail: Cases
TestRail: Runs
This feature is to define cross-tenant functionality specifically
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.
Cross-tenant functionality
ToDo:
Look into ReShare. Review ReShare plans and how this fits in.
V1 ReShare, tenants push to Union.
How does OAI-PMH fit into this?