2024-10-31 Product Council Meeting Notes

Ā Date

Oct 31, 2024

Ā Participants

  • @Alexis Manheim Lisa McColl, @Jeremy Huff , @Dung-Lan Chen , @Charlotte Whitt , @Jennifer Eustis , @Yogesh Kumar , @Brooks Travis , @Peter Murray , @Caitlin Stewart , @Christopher Spalding , @Kristin Martin , @Martina Tumulla , Joe Reimers , @Gang Zhou

  • Note taker: @Lisa McColl

Ā Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 min

Announcements

all

No announcements

10 min

Call for Bugfest testers

@Yogesh Kumar

Yogesh is asking for extended support for this coming bugfest. If the community can contribute more than the average amount it would be helpful. The number of test cases have more than doubled this time around.

Ramsons (R2 2024 testing). Asking PC to push to get more people involved in testing.
https://folio-org.atlassian.net/wiki/spaces/DQA/pages/514359326/Ramsons+R2+2024+Testing+activities

How can we recruit more people to do more testing? There are enough licenses for 500 testers - many of these are open.

Charlotte requested a table that shows how many test cases a day each tester is signing up for so each tester has a goal. Yogesh agreed and will add that to this wiki. He suggested reaching out to people who signed up for testing to ask them to participate: https://folio-org.atlassian.net/wiki/spaces/DQA/pages/514359326/Ramsons+R2+2024+Testing+activities

Jeremy suggested a direct message to bugfest volunteers. Yogesh will summarize the particular need and Jeremy will draft a letter. Caitlin suggested appealing to the implementation leads and reaching out to institution leaders. There is an increase in test cases - highlight the fact that this is a very important bugfest.

Action item:

  • Jeremy will draft a message and PC will look over

Ransom testing activities: https://folio-org.atlassian.net/wiki/spaces/DQA/pages/514359326/Ramsons+R2+2024+Testing

40 min

New claiming functionality for Sunflower

@Joseph Reimers

Presentation given: https://ebscoind-my.sharepoint.com/:p:/g/personal/jreimers_corp_epnet_com/EUIfbZy8aLZOtEfj64YBIbgBLwdGuXp2qRCHUGqefs8iKw?e=cEPVSk

Claiming app demonstrated.

Why a new app? : The receiving app was designed specifically for receiving. This type of app has different requirements and modifications of APIs.

While late pieces can be identified the functionality is minimal. There has been a lot of feedback that claiming needs to be more robust and automation.

This app intends to simplify identification of late pieces.

Discussion - (Lisa will look at recording/transcript - laptop rebooted while taking minutes at this point)

Kristin: Where does the status come from? Late comes from a piece receiving status, POL Claim active comes from PO app. What will happen with messy data? Will cleanup be needed? A piece will only become late if POL Claim active is set to True. Also needed is an expected date to push data into ā€œlateā€ status and therefore to the Claim app. Expected dates need to be added to receiving piece when you are creating the receiving piece. This is in Quesnalia. Also, relationship with serials app was mentioned.

Alexis: Noted the specificity of this app and others causing a large proliferation of apps. How does the addition of new apps impact the product in general? Joe mentioned that they did think about including this as part of the Receiving app, but it did not work out.

PC will have an internal vote and get back to Joe.

Jeremy - Expressed the concern about the proliferation of apps is important. Alexis will add to future topics.

5 min

Future topics

Ā 

Ā 

Ā Action items

Ā Decisions