2024-08-15 Product Council Agenda and Meeting Notes

5 min

Announcements

all

Lucy - Consortia SIG released survey. They have received 11 responses and would like more. Please let Lucy know if you have any suggestions to get more responses.

45 min

Ideas for tracking, maintaining, and supporting the roadmap, prioritization, SIG connections, and other processes established by the PC and working groups

all

• Continuing the discussion from last week (2024-08-08 Product Council Agenda & Meeting Notes

• We do not have the functionality to create a calendar in the Wiki - tested by Caitlin and Charlotte. We may want to consider paying or look for a different function.

• Kristin - Calendar options, Kristin spoke with Peter Murray about perhaps using paid wiki version, Google Calendar may be an option. Peter explained that the wiki calendar is at a higher tier - cost is approx $20,000 / month. We could use Atlassian free plugins from the Atlassian marketplace. The foundation has a free subscription to Google Workspace.

• Members will explore options. Alexis - what would go on the calendar? SIG Convener updates, What else? Suggestions:

  • Tri-Council Updates

  • Roadmap review regular cycle

  • Major Holidays

  • Color code calendar based on responsibilities and expectations.

  • We could reference calendar for weekly planning meeting

  • Frequency of liaison update? Has been ad hoc, but could be more formal and put on calendar. Formalize? - No need to update if there is not update, but we will make this reporting a regular occurrence.

• Google Calendar? - Downside “account confusion” Kristin asked how could we best set this calendar up so it is part of FOLIO, accessible. Peter, “We probably want to make one of the Open Library Foundation's accounts the "owner" of the calendar.” Peter said he would facilitate the creation of this calendar. Once that is complete group will start using.

• Dashboards - new or existing that we want to highlight more often? Charlotte commented that the Dashboards are not necessarily consistent with each other, so maybe we could help make them more in sync with each other.

• Charlotte - do we want to work with different SIGs to make different roadmaps

• Jennifer - May be worth talking with POs about consistency with filters and labelling. Suggested a “Jira 101” - how SIGs organize them and how dashboards are created.

• Votes or endorsement votes on prioritization. Documentation for implementing this has been written. May want another subgroup for the next step. Data Import uses “Topic Trackers” - bulk edit and list app has been doing this as well. Roles are not clear. Do we need to work on with POs

• Alexis - would it be helpful to have a group that has never done the process to start and see how it goes? Kristin - good to do. Concern about workload for POs. Roadmap Prioritization Group or PC? Jennifer referred to “supporting enhancements and improvements” working group that will be discussed at upcoming WolfCon meeting. To be discussed - how do we roll out prioritization feature? Should we have a cross council participation from CC and maybe TC?

• Charlotte - on wiki some working groups maintain their own roadmap.

• PC was going to check in with POs to see if they wanted to try the prioritization process. Note that having assistant POs makes this easier.

• Charlotte suggested assembling a smaller group from the PC to look at the dashboards and compare. Alexis - find a dashboard as a model to follow. Charlotte would participate. This can begin after WolfCon.

  Assemble group to look at dashboards after WOLFCon @Alexis Manheim

• Prioritization feedback would help POs. Visualization and way to track what is going on thank

• Goal: Best Practices for dashboard.

• Fourth subgroup will be discussed

5 min

Future topics

all

WolfCon Planning:

• Shoulder meeting

• Retro Board - https://easyretro.io/publicboard/0ALmBRbRDFgKpGdILQIAZio6Nvq1/b6e034ab-1d4c-4524-bbbe-6aedbc6f1003

Reading Room App - Questions about. Jeremy suggested broadening the focus to include any type of reservation. Reference: https://folio-org.atlassian.net/browse/UXPROD-1835.

Jana posted in chat:
Reading Room Features:  
UXPROD-1835 - Reading Room Circulation Draft
 ( different to  Reading Room Access:  UXPROD-4070 - Reading Room Access In Review )
 find more info here: RA-Reading Room Circulation Functionality

Tod via chat, “Maybe can ask for a module name change, to allow for better future coordination? (And less user confusion...)”

Brooks (via chat) - Materials reservation should probably be a more fundamental component of the circulation behavior (it should be able to be layered on top of existing functionality through a combination of pages/holds, loans, and recalls) that is managed by a back-end module that other components (reading room, equipment booking, room reservation, etc.) could utilize.

Martin - How does the PC evaluate new modules? Is it similar to the TC? What is our process? Alexis answered that we have a presentation from the PO, we have a discussion and then vote.

Jenn Colt in chat, “The TC review requires successful PC review”

Jeremy - Is this too focus to build an app for a single entity - worth asking, can we build a general reservation system that would work for the reading room but other entities that need to be reserved as well.

Aim with PC review: Kristin - we do not have a set of exacting standards, however the the PC is a good coordinating/communicating venue to bring up new ideas and to make sure that the POs and developers are thinking holistically. PC can give feedback that improves.

Jenn stated that her understanding the PC approval is for a flower release.