\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
Alexis ManheimCharlotte Whitt Alexis Manheim Kristin Martin Jeremy Huff Martina Schildt Gang Zhou Todd Goatley Brooks Travis Jana Freytag Jesse Koennecke Peter Murray Ian Walls
Note taker: Jennifer Eustis
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
5 min | Announcements | all | Reminder to add items to the PC calendar spreadsheet . The plan was to add individual items to the spreadsheet. Jesse was going to check to see which calendar we could use out of the 3 available. Jesse will raise it this week. Next Thursday is the community update session at the regular PC meeting time. Yogesh needs to reschedule. TC update: Review of mod marc migrations: There were some technical issues identified which will be addressed. The issue at play was the mod was accessing data in other modules. No time frame has been identified. SIG Updates: Liaisons - please remind your SIGs to provide an update. |
10 min (Postponed to Oct. 31st) | Recruiting Bugfest volunteers | ||
40 min | Follow up from WOLFCon, pt. 2 | Review high level goals and prioritize DRAFT Goals coming out of WOLFCon 2024 Alexis and Caitlin worked on this draft of high level goals. Look at the high level goals, discuss them, and decide if they work as high level goals. Goals drafted:
Charlotte: For number 5, linked data is separate. We need to work with the linked data SIG and MM SIG. Maybe number 7 is more appropriate. Brooks: Reporting should go in number 7. Martina: It would be helpful if the PC would recommend and ask for some alignment across apps where ever possible. Kristin: I don’t know how much work PC needs to do for this. We had this conversation and having a stronger push might be helpful. Where does reporting belong? Can linked data go into number 7? It doesn’t look like it belongs there. So where would it go? We don’t want to exclude 3rd party tools. Tod: If number 7 as written leans towards UI consistency, is there a similar priority/goal around back end functionality? Maybe there is no difference between front and back end consistency. Jeremy: When it comes to UI consistency, this is something that is looked at during the TC review process to some degree. Kristin: Is there reporting and linked data on here now? Both are in number 5. Does the PC need to be better informed about linked data. Will there be options? Charlotte: This is about supporting the flexibility of what libraries are using for linked data. It should be possible to select an option for linked data. The linked data open SIG will come up with these options. We can ask Laura and Chris to provide an update. Alexis: Linked Data open SIG. What part should the SIG play? Can PC work with the SIG to support them? Tod: Stepping back from specific issue of reporting and talking about consistency, given the distributed nature of development, it would seem that we walk to cultivate buy in POs and funding agencies. Kristin: I was thinking of expectations not being met. Have “What is reporting in FOLIO and options”. Can we get information from users? Can we do that in ways that are concrete? Jeremy: Have anyone talked about ordering and prioritizing these bullet points? It would be great to see a ranked choice across PC members. Charlotte: There is also some misunderstanding of what is possible with solutions. Can the reporting SIG do presentations about Panorama? Maura: When it comes to communication, only reporting SIG knows about it. If they have presentations in a SIG meeting, we can take that segment and put it in a more accessible place such as YouTube. Jeremy: We’re trying to answer what reporting should do in FOLIO. The reporting SIG is already doing great work. If there are only 3rd party options, then PC needs to be explicit about it. Kristin: We’re trying to providing support for external linked data editors but there’s also a FOLIO team building an internal solution. If we list external options, that doesn’t mean FOLIO shouldn’t have any solutions. Alexis: We should do a ranking. We need to take into consideration our time and availability. First we can clean up the page, rank it, and then work on the priorities. Charlotte: Reporting then has a connection to linked data because there is a need for flexibility. Tod: The distinction between operational and analytic is important. There should be some existing material from the reporting SIG on that topic. There is a difference in the indexing structures that ones uses for the transactions and for reporting. At a small scale it doesn’t matter but at scale it does. There isn’t one database that can satisfy all needs. Kay Dates: Draft page, https://folio-org.atlassian.net/wiki/spaces/PC/pages/536281116/DRAFT+Key+Dates+for+PC+Goal+Planning?atl_f=content-tree . These are things that we can put in the calendar. Martina: For number 2, the group on prioritizing doesn’t exist anymore. Jeremy: Can help with deriving a final ranking from all rankings? | |
5 min | Future topics | all |
✅ Action items
- Jesse Koennecke will check on which OLF calendar to use with OLF
- Alexis Manheim and Caitlin Stewart will clean up draft goals prioritizing, send out ranking prioritizing to PC.
- Alexis Manheim will reach out to Jeremy on how to finalize rankings for goals prioritization