2024-5-14 Consortia SIG Notes

ECS Development – Dashboard in Jira listing tickets related to ECS functionality

Very much still a work in progress and involves lots of different teams.

Tickets/features are heavily influenced by the MOBIUS consortium's needs.  

Ramsons can be considered Phase 2 of this work.

• Encouraged to review the Ramsons related tickets and leave comments/suggestions/questions in a ticket
• UXPROD-4577 : related to MARVA particularly
• UXPROD-4756 : Consortium Manager (allows Settings configuration in member tenants)
  • Supports shared elements (inventory, users, circulation, etc.) that impact reference data
  • Can view Data Import & Data Export logs (not Settings)
  • Ticket outlines expanded functionalities of the Consortium Manager app
• UXPROD-4581 : creating a central reporting outlet
• UXPROD-4566, UXPROD-4751 : enable cross-tenant Lists app functionality
• UXPROD-4573 : enable a user to change the 'ownership' of shared inventory from one tenant to another
  • ECS version of 'dragging' inventory from one tenant to another (like is available now in FOLIO Inventory app)
  • Use cases could be 1) moving materials between branches, if they are separate tenants, or 2) between libraries in a larger consortium between tenants when they ultimately share a collection, or 3) to fix errors in a shared inventory environment 
  • Requires configurations and can be enabled/disabled
• UXPROD-4549 : MARC21 record validation support, Phase 2
• UXPROD-4082 : How to apply mapping rules in a multi-tenant environment
• UXPROD-4708, UXPROD-4707 :
  • Enables the comparison of roles and/or users in a consortium 
  • A feature allows a user to 'compare' as a function the permissions of roles and users
  • Currently can only compare permissions sets to each other; adding the ability to compare users is an expansion
• UXPROD-4553 : 
  • Relates to the ability to enable central ordering for an ECS system
  • Can create orders in the central tenant, but the holdings/items/instances created in underlying member tenants; supports a centralized order workflow
  • Setting must be enabled
• UXPROD-4559, UXPROD-4578 :
  • Expands requesting options in ECS
  • Allows title-level-requests (TLR) between tenants

Questions : 

• Why do some tickets say 'ECS' and others don't?
  • Usually depends on the PO as to whether ECS is stated outright
  • Compressed timeline to rollout development, so it's a work in progress on how/when features & tickets are labeled or scaled up 
  • ECS is not a fork, just a scaled version of non-ECS 
  • Still working on consistency within community of ECS developers, POs, etc on process

Discussion : 

• ECS considers various use-cases in development including the needs for Library of Congress, MOBIUS
• Concerns about the name 'ECS' and if it is useful long-term
  
  • What is the perception of ECS as a label?  
  • Is it helpful for everyone?
  • 'Enhanced' implies there is an original version, but what was that?