2023-3-07 - Consortia SIG Notes

Link to recording

Announcements

Dennis Bridges will be attending a future meeting to discuss updates on his work for consortial requirements.  Date: TBD

Attendees

Noah Brubaker  Darsi Rueda Martina Tumulla Peter Sbrzesny Former user (Deleted) Bernd Oberknapp Elena OMalley Joe  Peter Böhm Hedda.Kuban 

Notes

None

Discussion items

TimeItemWhoNotes

Dennis had to postpone his presentation to us today.  We’ll reschedule.

10Consortia-related Jira ticketsCorrie

Has gathered them here Consortia-related FOLIO Jira Tickets

Feedback:

  • Maybe useful to add category column (acq, circ, metadata)
  • Keep single- and cross-tenant distinction

Corrie will add “consortia” label to some tickets that don’t have it but are relevant to us, and see if someone raises a problem with that.

15How to get our work scheduledNoah

We don’t have a PO, don’t have a dev team.  Noah wants to hear from Dennis about how to get some work done. We have some work written up but isn’t yet in a Jira.  We should review, agree, “put SIG stamp of approval” on it, get them in Jira.  Then how can we get someone to work on these.  Go to other related SIG for certain Jiras and advocate for our tickets, then can get the development work done through their SIG.

Other ideas on how to do this?

Agreement that partnering with other SIGs should be the first approach.  All of our work does tie in with the main areas/modules/SIGs.

Martina thinks going to Product Council not necessary.  Can contact the conveners of the other SIGs to get on their agenda. Reporting to PC through the monthly SIG convener update. 

Let’s see what EBSCO work entails (and keep fingers crossed).

20
Bernd

Working through their requirements, want to merge them into the documents our SIG has been working on (instead of adding their document as a stand-alone), link them to Jira tickets.  Also waiting on EBSCO’s presentation, are they focusing on single- or cross-tenant. Need that info to move forward.

Priorities: how have they changed?  How to communicate now that Jira tickets aren't continuing past practices?  

Is there a standard way to collect priorities?  (that other SIGS might use). There is discussion going on within the PC about a new ranking process.  Likely to be by SIG as well, not only by institution or consortium like in the past.

Do other SIGs have an implementers list of issues like the Acquisitions SIG?  

Discussion of how to move the data we've collected on cross-tenant mediated lending forward?  (not lose the valuable data we've collected?)

Which priorities are most important to us?  How do we communicate priorities until a formal process is identified?  

Revisit discussion on priorities after Dennis presents his findings and process for addressing consortial issues.  

Action items

  • Noah & Corrie will reschedule with Dennis