2024-06-20 Product Council Meeting Notes

10 min

Announcements

All

• Don’t forget to vote! Contact @Boaz Nadav Manes if you have not got your voting details.

• Next PC meeting will be July 11 and we will welcome new members and send off old ones

• WolfCon updates (@Jesse Koennecke ). Most session submitters have been contacted. If you submitted a session and have not heard any feedback by 21st June, contact @Jesse Koennecke

  • Registration for WolfCon and pre-conference workshops is open at https://openlibraryfoundation.org/about/wolfcon/upcoming/

  • Pre-conference workshops are extra charge but tried to keep this low. Early bird registration ($100) for these open until August 1st

  • Online attendance at WolfCon also needs registration and there is a small fee ($50)

• SIG updates for JuneSIG Report 2024-06-20

• July 18 will be Asia/Pacific meeting-friendly time. Start time to be agreed.

• Better Sample Data Working Group

  • Small working group of 5 (lead by @Charlotte Whitt)

  • Will meet for first time next Wednesday 26th June

  • More attendees welcome. Contact @Charlotte Whitt if you are interested

45 min

SIG Discussion: Conversation with SIG on PC action items from Things that could be better about FOLIO survey

What are the biggest (not currently resourced enough) areas of FOLIO we want to recommend focus on - do you agree?

1. Search - improvements to inventory search, both basic and advanced,

2. Courses - no PO for four years, no funding, some requirements work underway by Implementer’s SIG: 2024-01-30 FOLIO Implementers Meeting Notes and review to happen in August at Cornell

   1. Labeled Jira tickets for Courses

3. Data import - less about new functionality and more about performance, stability, reliability

4. Reporting - options for reporting are distributed and inconsistently available to different FOLIO libraries - how can we come up with a general reporting strategy to ensure all libraries have options available?

SIG process review - as product has matured, SIGs still “stuck in loop” of providing feedback and bringing issues to PO

1. Does this make sense?

2. What is a reasonable amount of effort from libraries and engagement with SIGs?

3. How could PC provide a better framework and structure for SIGs?

4. How can we keep people engaged when needed, but not schedule meetings just to keep people engaged?

@Martina Schildt : Sometimes difficult to say something is important “for the whole project” - e.g. c.200 GBV libraries currently have no use cases for data import even though maybe highly prioritised by other parts of the community

@Maura Byrne : There are multiple ways to report. Is the issue outreach? What does “inconsistently available” mean?

• @Kristin Martin as long as there are libraries lacking reports they need we (PC) will hear from the community that they are lacking reporting solutions

• @Charlotte Whitt need to make sure there is no misunderstanding - reporting solutions exist for Folio. But maybe the PC can document clearly what options are available and what different libraries are using. Also promote the Reporting SIG

• @Owen Stephens SIG members may not have a very strategic/high level understanding of what options are available in their library or available to the product generally. There is an inherent tension here.

• @Martina Schildt agree we can improve documentation around reporting

• Several major reporting options exist

  • MetaDB/LDP

  • LDLite

  • direct API access with other tools

  • Lists app (early in development)

  • ByWater partner libraries use an option, which creates Views on the FOLIO Postgres DB to access remotely

  • EBSCO Panorama

  • See also List of Integrations

Actions as regards Reporting discussion

1. @Kristin Martin follow up with@Jennifer Eustis to ask how the issues of documenting and promoting reporting SIG and reporting solutions could be brought up with the reporting SIG

2. Scope of FOLIO in relation to reporting topic that the PC should discuss again in future (add to Future topics list)

3. SIG Conveners to take back “List of integrations” page to their SIGs to see if these are useful and should be updated

4. @Kristin Martin to ask @Ingolf Kuss (Sys Ops SIG Convener) about the Integrations page and its use

SIG meeting health check:

• @Maura Byrne number of meetings of User Management SIG cut to 2 per month (and only happen if needed)

  • PO is a Jira wrangler

  • Meetings tend to be focussed and quick

  • Considering setting up a “gripe” session to surface issues

• @Martina Schildt ERM SIG now meets once per month, but two subgroups (Local KB, eHoldings) - so 3 meetings a month total. Meetings cancelled where no topics

  • Still big interest and good participation

  • Split of topics into subgroups (where not all libraries use all functionality) has re-invigorated the group as we are more focussed and people don’t need to attend all meetings

Actions re SIG health:

1. Add Future discussion topic : PC to discuss how they can support SIGs feeling they have a good sense of purpose, looking at and sharing best practice

5 min

Future topics

1. Scope of FOLIO in relation to reporting topic that the PC should discuss again in future

2. PC to discuss how they can support SIGs feeling they have a good sense of purpose, looking at and sharing best practice