2025-07-15 FOLIO Implementers Meeting Notes

2025-07-15 FOLIO Implementers Meeting Notes

Date

Jun 17, 2025

Agenda

  • Housekeeping (5-min.)

  •  

Homework and Pre-Reads

  •  

Useful Resources

  •  

Recording

NOTE: IMPLEMENTERS SIG USES ZOOM’S AI NOTES FUNCTIONALITY. If you would prefer that we turn this off for any session you attend, we are happy to! Please alert the convener at the start of the meeting.

Link to Recording: https://recordings.openlibraryfoundation.org/folio/implementation-group/2025-07-15T11:00/

Attendees

  • @Thomas Trutt @Tara Barnett @Darsi Rueda @Kimberly Smith @Jenn Colt Valerie Sain

Notes

Time

Topic

Notes

Time

Topic

Notes

 

Housekeeping (do next time)

  • Data Import SIG on July 23rd will discuss authorities.

  • From this discussion, we would like to understand what is working currently and what could be better. If you have issues or enhancements that you'd like to share or discuss, please join us. Information about the Data Import SIG including zoom and meeting times can be found on our DI wiki page.

 

Privacy SIG

https://wolfcon2025.sched.com/event/25leB/operationalizing-privacy-in-folio-development

Jenn is looking for a co-convener! Please watch the recording and consider joining the Privacy SIG (or someone from your institution), and perhaps even co-convene!

Metadb has some privacy issues.
When new modules introduced, there’s a very cursory process around privacy, just what PII is used. But retention isn’t discussed.
When Privacy SIG existed before, white paper was created (above).

Jenn’s plan is to get the SIG going again, and slack, and get into PC’s prioritization process, so privacy issues can be visible. Keep an eye out for bugs, prioritize them, get them ticketed and to the Support SIG so they can be prioritized.

WOLFcon session will talk about putting some of the ideas in the white paper into place. Get privacy into the process, “privacy by design.” Make sure PC and TC consider privacy issues during evaluation process. Give PC/TC the questions that should be asked during evaluation… when new features are added to existing apps, only the relevant SIG looks at it, so they need more tools to consider privacy implications. Getting buy-in from the PO’s is also key. Really should have a rep from every SIG on the Privacy SIG. “Definition of done” needs to include privacy. Can add to “best practices for developers” documentation

GDPR has been getting more attention, but it’s open to interpretation and hard to implement. Hope to get good breadth of membership to represent needs across Europe and US.

It’s our ethical responsibility to maintain privacy and we are not meeting it.

 

 

PC Update by @Charlotte Whitt

 

Action items