5 min

Welcome & Announcements

all

Tri- Council meeting next week

SIG Reports Due Today

WOLFCOn – Still time to register for Kansas City! Conference hotel group rates available. Shoulder meetings on Friday and being added to Sched once inverted timing (all councils in morning, individual councils in the afternoon) is confirmed with Council chairs.

SIG reports due today but reminder sent out late. Kristin Martin used to do SIG report reminders, but Jennifer will going forward. Maybe we want to halt reports in the summer or fewer? One for July and August? Every other month? TBD.

At the Community Council meeting on Aug 11, 2025there were presentations of three proposals designed to get the group to think about how we can gain a “Common understanding and agreement on core challenges facing FOLIO with regard to community-sustained software development.” After the presentations, everyone present added their top three problems and solutions to a shared doc. I suspect we will hear more about this at the Tri-Council meeting next week, but if not then, definitely at WOLFCon. (Alexis)

PC members should read documents in advance of Tri-Council meeting. Also, Jeremy and Caitlin are giving a status update on community prioritization and Community directed development efforts at Tri-Council meeting next week.

Housekeeping

5 min

Status of Mosaic Endorsement: overwhelmingly positive endorsement vote, Caitlin will follow up on decision log, etc.

New Template (Caitlin): I created a new meeting notes template. It’s called Product Council Agenda / Notes and I’m having a hard time getting it to surface in some of the places I’d like to see it (like the Create from Template macro) but it’s a step in the right direction! Does anyone have feedback on the template?

Charlotte suggested reducing to 3 columns, putting time next to agenda item to leave more room for notes. Caitlin will make that change.

Community Newsletter (Caitlin): The council chairs are exploring starting a newsletter to improve communication and lower barriers to engagement. over the next few weeks we’ll be gathering topics for newsletter so that we can put together a prototype and determine the frequency, means of distribution, etc. I have added a little purple box to the top of our notes page to flag topics that we might want to cover in such a newsletter.

Proposal - Turn on AI notes in Zoom

• Recently a few of our notetakers have used AI summary tools to assist with note- taking.

Discussion: Makes Alexis and Charlotte uncomfortable to rely on them too much. They can get things really wrong. We cam use it with caution and make sure to review what is generated. Text can look good but content is incorrect or missing important information. Synthesis is important. We will experiment by capturing info in two ways, both with AI and a human note taker.

5 min

Meeting Summary Page

Problem: It is difficult for community members to keep track of which groups meet when and get a sense of all the action happening in the community.

Proposal: Use Confluence Page properties report feature to create a single page where community members can find out when all the SIGs meet and understand what they currently working on.

What SIGs need to do:

• Add standard metadata their home page enclosed in the Page Properties macro - see https://folio-org.atlassian.net/wiki/x/AQDnQw

• Tag that page with a label - I’ve used “mtg_summary”

• Keep the “Upcoming Topics” field up to day for the new 2-3 meetings

Outcome: Meeting info will automatically propagate to a central report that we could link off the FOLIO homepage. Seehttps://folio-org.atlassian.net/wiki/spaces/PC/pages/1139179533

Questions:

• Is this doable?

• How do you feel about these fields - anything missing?

• Any other feedback

• Discussion:

  Can we leverage the SIG convener quarterly meeting to talk about this and see if SIGs are on board? Or use the SIG reports somehow? Charlotte suggested including info on most recent topics discussed, not just what is going to be discussed. Index of agenda topics from past meetings? Caitlin said this may or may not be possible with this feature. 

  Jennifer said sometimes SIGs just talk about JIRAs and add notes to the issues and nothing to actual notes. Maybe do prioritization first and then do this next? A lot of work to go back to older meeting notes, or maybe we just start this going forward.

  Conclusion: Start with MVP for Meeting Summary Page, be clear about what we are asking the SIGs to do, and not put too much on them at one time.

10 min

SIG Reports - Revisit goals

Updates on Active Initiatives

5 min

Check in on Community Priorities

Subgroup formed to create rubric and definitions to use in the rubric. Will circulate for feedback in the coming weeks. Need to coordinate with POs. Caitlin attending PO meeting next week to discuss.

10 min

Discuss Discovery SIG top 5

@Demian Katz

@Nicole Trujillo

1. UXPROD-4805: API endpoint for batch renewal
   Draft

2. Tell the Discovery system what item is holdable. UXPROD-2422: Discovery Integrations - Expose Circulation Rules Regarding Requests
   Draft

3. Tell the Discovery system what item is renewable

4. Ability to Sort Items in FOLIO so that the Discovery system does not have to sort 10,000+ items on the fly UXPROD-5257: Analysis: Re-order item records via API
   In Review

5. UXPROD-1625: Re-order Item records via UI
   In Progress

https://folio-org.atlassian.net/wiki/spaces/PC/pages/931070022

Nicole (SIG convener): Top 5 JIRAs. Many are for Requests. Damien talked through these. Mostly performance and functionality gaps. See above.

Sorting is also on the MM SIGs priority list.

Thomas had questions about #s 2 and 3. Are they for users already logged in? Damien: Yes. Complexity of request system is a factor. Batch renewals has come up a lot in RA SIG. What data is returned and in what format? Ticket has a proposal for what that would be, but may need to be refined.

Caitlin: A few of these UXPRODs are still in draft. Should these be out of draft before they go to the final list? Nicole: They are still trying to understand the JIRA process. There is no PO for the Discovery SIG. How does something go from Draft to Open and what role does the SIG play? Thomas: without a PO, could talk to the PO that is the most related to the area and ask if they think there is enough info in the Jira to be moved to Open status? Once there, dev teams can pick it up. Back and front end devs will refine more.

Charlotte (from chat): Generally, if a feature (UXPROD) does not have underlying Jira Item tickets (stories) written up, the the feature is still in Draft. A feature will move to Open, when all defining tickets are written up, and is dev ready for the Development teams. The more details, the better.

Nicole asked about an overview of the process with list of POs? Charlotte shared these links:

Directory of POs: https://folio-org.atlassian.net/wiki/spaces/PO/pages/2667876

FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility - FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrixPreview

Jira status - JIRA statusPreview

New Topics

15 min

PC vision workshop @ WOLFCon

What is a vision workshop?

What do we need to achieve?

How can we do this effectively?

@Jennifer Eustis and @Alexis Manheim will help plan this workshop

Kristin’s Vision doc:

Planning

5 min

Newsletter topics

Possible topics: Mosaic endorsement, what the PC is working on (high level) with new members and focus, updated liaisons, prioritization dashboard progress.

10 min

Define agendas for next 2 meetings

• Check Jira board

• Check Calendar

• Seehttps://folio-org.atlassian.net/wiki/x/koARJQ