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

[UXPROD-4232] Protect certain settings from centralized batch management within a consortium Created: 20/Apr/23  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)

Type: New Feature Priority: P3
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Unresolved Votes: 0
Labels: LC2, consortium-manager, ecs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UICONSET-15 Protect certain settings from central... Draft
is defined by UICONSET-16 Prevent batch update of protected for... Draft
Relates
relates to UXPROD-4211 Manage settings for multiple member l... Closed
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)
Front End Estimate: XL < 15 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XL < 15 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Thunderjet
PO Rank: 0

 Description   

Current situation or problem: Libraries may want to prevent certain settings from being updated by consortium central office staff who are otherwise authorized to update settings and configurations. This level of control may require greater granularity than is currently offered with permissions (i.e., in general, the consortium office may save settings on behalf of the library, but certain very specific settings designated by the member should not be editable)

In scope

  • Consortium manager-controlled settings
  • Member "locking" of settings to prevent "save" modification from Consortium manager
  • Form and list-form type settings

Out of scope

  • "Shared" settings from Consortium manager
  • List type settings

Use case(s)

A library has developed a specific process for handling certain types of materials that differs from how the majority of consortium member libraries handle similar materials. This library wants to prevent the central consortium office from inadvertently changing those settings.

Proposed solution/stories

Links to additional info

Questions


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