Consortia (Cross Tenant) (UXPROD-794)

[UXPROD-818] Possibility for restricted cataloguing (just locally usable, e.g. grey literature, internal documents) besides shared cataloguing 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: P4
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

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): R5
Rank: hbz (TBD): R5
Rank: Hungary (MVP End 2020): R4
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:
Possibility for restricted cataloguing (just locally usable, e.g. grey literature, internal documents) besides shared cataloguing

Notes:
is this about a library "owning" a bib record? vs holding or item? Being able to connect multiple KBs would help with this because each library could "own" one of the KBs

HK - Does this imply that there are records a library does not want to share with the consortia or union, or something else? If this is the case, adding a "share" flag in inventory that the cross tenant apps follow could prove simple.


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