5 min

Welcome & Announcements

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?

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.

Housekeeping

5 min

SIG Reports Due Aug 21, 2025

Review SIG assignments + expectations for report

5 min

Meeting Summary Page Idea

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?

Updates on Active Initiatives

10 min

skip today

New Topics

20 min

Mosaic order integration settings app

• Feature: https://folio-org.atlassian.net/browse/UXPROD-4716

• PC Endorsement ticket: https://folio-org.atlassian.net/browse/PCE-11

@Dennis Bridges

The backend has been through TC review process and the UI will soon go through that process. This Mosaic doesn’t change any of the architecture and works in a similar fashion to GOBI. Unlike GOBI, Mosaic uses json rather than xml. For the UI, Mosaic integration can be found in Settings>Mosaic integration which includes the ability to select a default order template.

What is being sent to API? There is additional functionality through edge orders for Mosaic integration. There is the ability to get data for the creation of order records. Now you can get a list of order templates. A user could potentially use an order template. You can also get custom fields, locations, acquisitions methods.

mod-mosaic allows for the submission of a post request and will use the default template for order creation if an order template isn’t specified in the post request.

Questions:

Alexis: Will it handle print orders or is it only electronic? Not sure. Right now this is just ebooks. yes it will be both print and electronic and eventually replace GOBI. Both integrations (mod gobi and mod mosiac) can work at the same time.

Jennifer: To select the template, will this happen in Mosaic? This can be done in Mosaic.

Kristin: There are a couple of libraries that are using Harrassowitz. How does this affect this? harrassowitz might be using the GOBI model with something that looks like GOBI or maybe they created they own model. This shouldn’t be an issue since this offers more options. For any vendors that want to supply orders, should there be their own mod - api module? The decision to have a mods orders through another one was to provide more flexibility and to be less affected by changes. How do we keep this scalable and for what libraries want? Spoke with Harrassowitz, and they were interested in using mod-gobi or creating their own module. This gives them the choice.

Thomas: The edge API isn’t changing. It is just being extended. So anyone using this won’t affect them but will extend. This might be a good case for a more general module later on. Mod-mosaic is very simple on purpose.

Martin: You only made changes to mods-orders. This extension is only of interest to libraries hosted by EBSCO. This is available to anyone. Any library could use it. If you are an EBSCO customer, you could use this. With this integration, Mosaic offers custom fields and the template on FOLIO side, you should be able to satisfy any workflow by touching order in one place.

Kristin: Kristin could follow up with the Acquisitions SIG to have a demo of what Harrassowitz does with its process.

Alexis: This can be adapted by other vendors.

Thomas: The expansion of the edge API means going to one source rather than many. Because this is accepting json, you can use an external platform to feed it into this platform.

Tod: With mod-mosaic and these enhancements, the process is simplier. You have a choice to deal with xml or json.

Action: The vote will be in slack. More details will be posted in Slack.

Planning

5 min

Newsletter topics

Did any come up today? If so add to the purple box above.

10 min

Define agendas for next 2 meetings

We will do this via Slack this week

• Check Jira board

• Check Calendar

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