2024-10-29 Consortia SIG Notes

5

Recap of Reporting Conversations

Lucy

Lucy and Noah have been talking to various folks about the Consortia reporting needs, and doc.  Met with Reporting SIG and Index Data about Metadb.  Conclusions are that there are so many differences between Consortia setup, it's hard to create anything that will work generally. Metadb looks like the best solution for most of the stuff on our list, for ECS/multi-tenant.  So we should work with Reporting SIG to create some Metadb "cookbooks."  There is potential that the Reports App and/or Lists App might work for our reporting needs.   It's all complicated, let's pivot to some other development needs, some low hanging fruit... 

5

ECS Product Manager Introduction

Lucy / Dennis

Started with discussions with MOBIUS Consortium, Acq features.  Dennis would like to contribute more as a PO with this group.  Start with cleaning up the Jira backlog. There are 80 open features that reference consortia in some way (15 labeled Consortia). Need to get all tickets labeled that need it.  Need to differentiate between single- and multi-tenant.  If we get all the topics we've discussed lately, Dennis can help with organization. Then others can comment on them, show interest, etc.... and that can drive development.

15

Consortial Models Overview

Dennis

ECS tried to align what implementing libraries with what others had discussed over time. Focused on a handful of models (cuz there are so many): National Library (LC), Diverse centralized consortium (MOBIUS - central administration for some but not all), Diverse decentralized consortium (granular/shared administration in single tenant), Complex library (central tenant - academic).

Out of scope for ECS:
Single tenant is not within the scope of ECS functionality.
One library as a member of multiple consortium doesn't fit in ECS
Connected consortia
Nested consortia

Phase 2 means Sunflower

30

Jira Issues Review

Dennis / Lucy

We will start reviewing the Jira issues related to consortia to determine a) is this a consortial feature or not? and b) does the issue contain all the needed information and details?  List is here. You may need to adjust / add/ remove columns using the option in the right right of the table in order to see all information.

Did we have different labels for any Jiras we created?

Get Jiras labeled, then Dennis/we will go through those, make them more ready for conversation and development.

Analysis completed means it's ready for development. In progress, In review means been developed and is being tested.  Asignee changes status.

Before next time, Noah and Lucy will look through all our documentation so we can make sure Jiras get made for them if not already.

5

Outstanding Issues/Announcements/Quick topics 

All

No meeting in two weeks (Nov 12) since many of us will be at the Charleston Conference. 

Ramsons bugfest is coming soon and there will be an ECS-enabled environment.  There will be a Eureka platform (role management) as well.  Please test if you have any time to help.

WOLFcon consortia-related session:
Enchanced Consortia Support: Meeting the needs of complex systems

Wilhelmina Randtke is going to work on consortial documentation! Thank you!