Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2) (UXPROD-4485)

[UXPROD-4230] Manage consortium record sharing Created: 19/Apr/23  Updated: 06/Dec/23

Status: In Refinement
Project: UX Product
Components: None
Affects versions: None
Fix versions: Sunflower (R3 2024)
Parent: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2)

Type: New Feature Priority: P2
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: LC2, ecs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-4059 Create tenant profile Closed
Release: Sunflower (R3 2024)
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2)
Front End Estimate: XXL < 30 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Thunderjet
PO Rank: 120

 Description   

Current situation or problem: Libraries in a consortium share specific workflows. In many consortium, the workflows that are shared will vary. It is also possible that not all members of the consortium will want to participate in sharing all possible workflows with other members of the consortium.

In scope

Allow administrators to control what members are participating in the sharing of bibliographic records

Out of scope

Allow administrators to control what members are participating in the sharing of other record types

Use case(s)

Certain members do not want/need to participate in sharing bibliographic data. They will only maintain local bibliographic data.

 

Links to additional info

see linked document for more details

Questions



 Comments   
Comment by Dennis Bridges [ 17/May/23 ]

I am moving this story out of the R release as all libraries in our initial implementation of ECS will be participating in Record sharing. Ie. there will be no need for administrators to be able to turn this off.

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