Consortia/Multiple Libraries (Single Tenant) (UXPROD-872)

[UXPROD-921] Consortia (Single Tenant) Created: 13/Jun/18  Updated: 16/Sep/20  Resolved: 11/Sep/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Consortia/Multiple Libraries (Single Tenant)

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: consortia
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Consortia/Multiple Libraries (Single 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): R1
Rank: FLO (MVP Sum 2020): R5
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R5
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   

The ability to set up a consortium in the context of a single folio tenant. Leverages the location hierarchy (institution, campus, library, location) to model the consortium. This is distinct from the cross-tenant consortia model which is defined in UXPROD-794 Open .

Note: any additional work needed to support a single-tenant consortium will likely be done within other apps (e.g. users), but this epic makes it clear that analysis work is being done to ensure we have what we need for single-tenant consortia.



 Comments   
Comment by Anya [ 17/May/19 ]

Cate Boerema I do not believe I need to do anything else with this one, correct? also not sure how it was assigned to me...

Comment by Cate Boerema (Inactive) [ 20/May/19 ]

Anya, you agreed to PO this feature over a year ago. The idea was that you'd analyze what was needed for a single-tenant consortia implementation to ensure we had what we needed. I think you transitioned roles without getting very far. That said, I also think we have what we need with the possible exception of Teams ( UXPROD-1147 In Progress ). I will unassign this from you.

Comment by Cate Boerema (Inactive) [ 11/Sep/19 ]

Closing this feature as it doesn't specify what needs to be done aside from what is already there. It is already possible to represent a consortia within a single tenant using the location hierarchy assuming members are willing/able to share a single user repository and inventory. The new Acquisition units feature ( UXPROD-1687 Closed ) provides some additional control around financials. There may be other work to be done, but it should be defined more specifically in other UXPROD features.

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