2025-10-28 Consortia SIG Notes

5

Housekeeping/Updates/Updates

All

GALILEO voting this Friday on whether they are a go for go-live in December.

50

Our top 5 priorities for PC

All

Summary from 10/14 meeting:
The team reviewed the top vote getters from the Consortia-related tickets page (VOTE HERE! Consortia-related Issues - Consortia SIG - FOLIO Wiki)

The number one priority (bulk edit of instances) is related to another ticket that must get done first (Build a framework for bulk edit forms) so we decided to make that one #1. We will associate other bulk edit tickets with that one.

The number two priority will be [UXPROD-4839] Allow user to "unshare" or demote a shared Instance to be a local instance - FOLIO Jira

The number three priority will be [UXPROD-4713] Enhanced inventory record suppression for Consortia - FOLIO Jira.

Today discussed what our number four and five priorities will be:

In consideration of this ticket, Owen joined to discuss background on this, and the work that’s being done. [UXPROD-4807] Ability to share publication patterns between tenants - FOLIO Jira. Ability to share publication patterns for serials in the same tenant is a precursor. Theory was the same pattern could be used for many titles, but actually doing it didn’t really happen because patterns always differed slightly (days published even if both monthly, enum, etc.) Deprioritized pattern reuse. Feedback after release was that too much work being done to create very similar patterns, needed a shortcut. So for Sunflower, introducing templates. Ability to create new patterns quickly, based on template, then make whatever modifications needed. Can create unlimited templates (uploaded via API call only for now – editing interface planned for Trillium), then choose from dropdown when creating a New publication pattern. There’s a space in the wiki to download template sets (or contribute more). Would need to load to each tenant or subtenant individually. Own suggests we consider if it’s the patterns or templates we would want to share amongst tenants/subtenants. Purpose of these is to generate expected pieces for a period of time.

Hedda says shared piece templates aren’t working that well at BSZ. Scott wants a limited set so staff aren’t overwhelmed, can’t find their pattern, and make their own. Lucy says folks aren’t bothering with patterns right now (e.g., GSU doesn’t have much print to check in anymore).

Owen thinks maybe what we’d want would be for, given a set of templates that exist on the central tenant, have the ability to load to a subtenant (either push or pull). Copying from tenant to tenant is another option. Copying the pattern templates, not the patterns themselves. Owen suggests making a new Jira ticket to go forward (and Dennis agrees). We will discuss in a future meeting. Perhaps there is no longer as strong of a need for this.

We will keep [UXPROD-4798] Ability to create centrally managed import profiles - FOLIO Jira) as our number four priority.

[UXPROD-4825] Cooperative Collection Development notifications for last copy and subscription gets the number five priority. This would be a really cool feature.