2025-01-09 Product Council Agenda & Meeting Notes

5 min

Announcements

all

• Tri-council meeting, Monday January 13, 10-11am ET, short council updates and then discussion of Eureka transition process and timeline https://folio-org.atlassian.net/wiki/x/DwCRJg  using CC zoom: Join our Cloud HD Video Meeting  Report on the timeline for adoption of the Eureka platform

• Review https://folio-org.atlassian.net/l/cp/UvYkLD9Q and Incomplete tasks from meetings

50 min

More on evaluating the PC process for evaluating new functionality

@Jennifer Eustis

Slides

• Subgroup formed to look into a mechanims for the review process

• important: use standard tools for tracking

• review as early as possible

• approach is a 2 part process - TC’s review approach and checklist

  • 1st step: evaluation process

    • overview, what is new, motivation

  • 2nd step: communication and engagement

    • communicate and engage with POs frequently

• there is a description of how to submit a review for PC: https://folio-org.atlassian.net/wiki/x/hgB7Jw

  • with a list of criteria

• new mechanism will be via JIRA

• there will be a Jira template to be answered for the PC

• in future PC will “endorse” functionality instead of “approve” it

• The process definitely should not be a “burden” - feedback is always welcome

• Open questions:

  • what is new functionality? how to define “new functionality”?

• PC would like to test the updated mechanism > therefore the Jira template is needed

  • possible pilot: Reading room functionality

  • possible pilot: Workflow SIG

• Discussion on why the PC is endorsing new functionality

  • Question: why does new functionality need to be presented in PC, as it is presented in the SIG meetings

    • argument: funding institutions would not develop somehting that is not needed

  • The PC is looking at the big picture while the SIGs have a specific focus.

  • The PC is doing this, by keeping the big picture view of the FOLIO project

  • Not all functionality is discussed in SIGs but in Working groups

• Next steps:

  • get Jira set up

  • pilot process with “Reading Room functionality” and “Workflow app”

  • get feedback

• Exception: we may vote on the Reading Room functionality sooner to not hold them up and use them as a test for the new jira after the fact > TBD

  • What needs to be clarified is the terminology for the Reading Room functionality

  • there are still discussions around whether it is too specific, because it can be used to support other workflows as well

  • The SIG would like to keep the name though

5 min

Future topics

all

• Visit to OA SIG to talk about Prioritization resulted in an invitation to attend a future PC meeting

• Discovery Working group would like to transition to SIG status