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

[UXPROD-2137] Agreements & Licenses | Support multiple teams for Agreements and Licenses within one FOLIO tenant Created: 29/Oct/19  Updated: 08/Nov/21

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

Type: New Feature Priority: TBD
Reporter: Owen Stephens Assignee: Owen Stephens
Resolution: Unresolved Votes: 0
Labels: agreements, erm, licenses, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by ERM-384 Tags | Agreement app | Single Tenant ... Open
is defined by ERM-378 Agreements App: Consortia Handling : ... Closed
is defined by ERM-379 Agreements App: Consortia Handling : ... Closed
is defined by ERM-380 Agreements App: Consortia Handling : ... Closed
is defined by ERM-381 Agreements App: Consortia Handling : ... Closed
is defined by ERM-383 Licenses App: Consortia Handling : De... Closed
Epic Link: Consortia/Multiple Libraries (Single Tenant)
Development Team: Bienenvolk
PO Rank: 18
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R1
Rank: 5Colleges (ERM Jun 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: MI State-Lib of MI (Sum 2021): R1
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

In a situation where multiple teams, libraries or institutions share a single Folio tenant, it maybe desirable to limit access to specific Agreements and Licenses to specific users or groups of users, similar to the Acquisition Units that can be applied to Orders & Invoices

A typical example of this situation could be a consortia of libraries/institutions sharing a single folio tenant. However it could also apply in other situations where permissions to view or edit specific agreements/licenses is limited to a subset of users



 Comments   
Comment by Cate Boerema (Inactive) [ 18/Nov/19 ]

Owen Stephens is there an epic this can be assigned to? Thanks

Comment by Khalilah Gambrell [ 20/Nov/19 ]

Owen Stephens, I assigned this Feature to UXPROD-872 Draft .

Comment by Molly Driscoll [ 15/Sep/21 ]

Owen Stephens do you have a sense of when this feature might be prioritized? We have a few current and several incoming consortia we are working with and this feature comes up fairly frequently in questions I'm asked.

Comment by Molly Driscoll [ 08/Nov/21 ]

Owen Stephens this question just came up again – any idea of where this is falling in terms of priority / dev timeline?

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