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

[UXPROD-4211] Manage settings for multiple member libraries within a consortium Created: 17/Apr/23  Updated: 30/Nov/23  Resolved: 13/Oct/23

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

Type: New Feature Priority: P2
Reporter: Dennis Bridges Assignee: Joseph Reimers
Resolution: Done Votes: 0
Labels: LC1, consortium-manager, ecs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UICIRC-962 Prevent editing of shared settings fr... Closed
is defined by UICONSET-7 Create consortium manager interface Closed
is defined by UICONSET-8 Limit access to consortium management... Closed
is defined by UICONSET-10 Select member institutions for consor... Closed
is defined by UICONSET-11 Set default institutions for a given... Closed
is defined by UICONSET-13 Confirm member institutions to be upd... Closed
is defined by UICONSET-19 Allow user to share list and list-for... Closed
is defined by UICONSET-21 Prevent editing of Shared list or lis... Closed
is defined by UICONSET-26 Add Circulation to Consortium manager Closed
is defined by UICONSET-27 Add Data Export to Consortium manager Closed
is defined by UICONSET-28 Add Data Import to Consortium manager Closed
is defined by UICONSET-29 Add Inventory to Consortium manager Closed
is defined by UICONSET-31 Add Users (settings) to Consortium ma... Closed
is defined by UICONSET-49 Create message for user when not uniq... Closed
is defined by UICONSET-50 Workflow handling for user when not a... Closed
is defined by UICONSET-126 Merge/Review Consortium manager Q pro... Closed
is defined by UIIN-2482 Prevent editing of shared settings fr... Closed
is defined by UIU-2914 Prevent editing of shared settings fr... Closed
is defined by UXPROD-4153 Manage List type settings for multipl... Closed
is defined by MODCON-46 [PC] Implement initial version of POS... Closed
is defined by MODCON-48 [PC] Save general PC request state in... Closed
is defined by MODCON-49 [PC] Implement Get endpoint for retri... Closed
is defined by MODCON-56 [PC] Implement Get endpoint for retri... Closed
is defined by MODCON-57 [PC] Implement Delete endpoint for pu... Closed
is defined by MODCON-58 [PC] Implement Scheduling Cleanup Job... Closed
is defined by UICONSET-9 View settings defined in Consortium m... Closed
is defined by UICONSET-14 Header display when modifying setting... Closed
is defined by UICONSET-125 Add app icon Closed
is defined by RANCHER-815 Redeploy Rancher with enabling R/W split Closed
Duplicate
is duplicated by UXPROD-809 Network/central office systems staff ... Open
is duplicated by UXPROD-810 Network/central office systems staff ... Open
Relates
relates to UXPROD-4232 Protect certain settings from central... Draft
Release: Poppy (R2 2023)
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)
Back End Estimate: XXL < 30 days
Back End Estimator: Serhii_Nosko
Back-End Confidence factor: 80%
Estimation Notes and Assumptions: Estimating higher because the work done here would also be used for related features (List-form and list-type). Unclear if a new module is needed in consortia tenant to make this possible, if not estimate could be lower.
Development Team: Thunderjet
PO Rank: 0

 Description   

Current situation or problem: Consortium central offices or other other authorized consortia managers need an interface for managing settings, defaults and other configuration pieces for many or all member libraries within a consortium in batch in order to improve efficiency.

In scope

  • Creation of interface or application appropriate for centralized consortium configuration and management
  • Concurrent management of multiple member institutions
  • Batch configuration of default settings for multiple member institutions
  • User selection of which member institutions to manage
  • Creation of appropriate permissions
  • Limit access to multiple member/multi-tenant configuration to the central consortium tenant

Out of scope

  • Member institution-managed configuration (i.e. anything normally controlled via Settings for a given institution)

Use case(s)

  • Consortium office wants to standardize fixed vocabularies for configuration pieces across the consortium (e.g. status codes, reasons for specific actions, etc.)
  • Consortium office manages certain functions on behalf of Member libraries and wants to set default behaviors for those libraries in batch rather than individually in order to maximize central office efficiency
  • Consortium office wants to standardize certain templates used consortium-wide to standardize certain processes (e.g. intra-consortium borrowing/lending, consortium-led purchasing, etc.)
  • Consortium office wants to standardize import/export jobs for specific groups of libraries (e.g. standardizing rules across multiple Bugfest tenants)

Proposed solution/stories

Identify relevant configuration pieces
Identify appropriate configuration formats: "List", "Form" and "List-Form Hybrid" types
Design interface for management of "list"-type settings for multiple tenants UXPROD-4153 Closed
Design interface for management of "form"-type settings for multiple tenants UXPROD-4151 In Refinement
Design interface for management of hybrid list-form-type settings for multiple tenants UXPROD-4152 In Refinement

Links to additional info

https://miro.com/app/board/uXjVP9HDWqw=/

Questions

Are there any settings, configuration pieces or similar that we want "protected" such that they can ONLY be changed via consortium "push"? That is, do we want a consortium-controlled "canonical" list of valid Formats, User groups, etc. in order to minimize dependency issues?


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