...
Jesse Koennecke, Philip Schreur, Tod Olson, Anton Emelianov (Deactivated), Aaron Trehub, Gang Zhou, egerman, Maura Byrne, Ingolf Kuss, Jana Freytag, Karen Newbery, Laura E Daniels, Mark Veksler, Martina Schildt, Martina Tumulla, Sharon Wiles-Young, twliu, Brooks Travis
Goals
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5min | Announcements | None. | |
| 10min | BugFest Update | Anton | Bugfest is finished and we are waiting for the release to be made. Bugfest did better this time with Juniper versus Iris release (after 2 weeks of testing 90% passed for Juniper versus 75% for Iris and 100 more test cases). After bug fixes, 98% passed versus 96% passed; the test cases that didn't pass are for low-priority bugs that were deferred to the next release. At the moment, there are no plans for a hotfix for Juniper (unlike Iris). New for this bugfest, 6 people were added from the EPAM team, and they completed 30% of the test cases. For the next bugfest, Anton will ask EPAM to wait for community members to select test cases before picking up the rest. Overall, this bugfest had fewer participants and fewer institutions. The number of defects found by bugfest is down 45%: 76 versus 139. Smoke test results were better: 87% of test cases passed versus 38% for Iris. If one thing could be changed, Anton would like to automate the smoke test so it runs every day. There is a lot of effort going into automated tests now. folio-api-tests-karate tracks the results of automated tests of the Okapi modules. A similar effort is underway for automated tests for Stripes modules. |
| 30min | SIG Convener Updates | See SIG Updates heading below. | |
| 10min | FOLIO at WOLFcon |
SIG Updates
...
- The App Interaction SIG is discussing how “Create orders and link order lines to materials in the Knowledge Base” is envisioned and can work without creating unnecessary dependencies
- The Roadmap Group discussed with AI the current list of themes and approach
- File storage across apps was discussed. AI favors a general approach. Proposal is to use S3-API and and to implement storage using min.io client. The topic was brought to TC for decision making.
...
- Thanks to quick mobilization, the LDP app seems to be moving toward inclusion in the Kiwi release. The Reporting SIG is working with PO Charlotte Whitt to provide Bug Fest testers.
- Reporting SIG will have a presentation on the 16th of August from members of the ERM reporting subteam on what we can expect from the upcoming upgrade of the LDP to a new software platform called metadb. Metadb has helpful new features like access to even more FOLIO data and streaming data updates. On August 9th the SIG also had a long demonstration of how to use Postman and KNIME to query FOLIO APIs (recording).
- The RA/UM reporting subteam is partnering with the RA SIG to improve communication between the two groups. Angela will join the RA SIG meetings twice a month so the groups can share information of mutual interest. Other subteams seem to have members who attend both SIGs, but let Angela know if your group would like closer ties with the reporting community.
- Development status FOLIO Analytics Report Repository:
- At this time, over 100 report queries have been written, reviewed, and posted on the FOLIO Analytics report repository
- Our next release includes queries on missing and overdue items, HathiTrust reports, vouchers, agreements, and more.
- LDP app:
- Version 1.3 of the LDP app includes UI testing and will hopefully be included in Kiwi release
- FOLIO Analytics Report Repository:
- LDP app:
- Ongoing reminders for all FOLIO Participating Institutions
- Action =>> Please review Reporting SIG-All Report Clusters (60 issues) in JIRA and RANK each report cluster for your institution (R1-R5); the SIG uses these ranks to prioritize report development
- Reporting SIG is always recruiting new subject matter experts and report developers. Please contact Angela if you have staff who would be a good fit for reporting.
...
- Consortia met once this month, cancelling canceling one call due to availability.
- Currently the group is finishing an initial discussion and ideation around addressing consortia administrator needs. The group is exploring two possibilities which may be developed separately or together, but increasingly likely to need both:
- Consortia Admin User
- Consortia Admin Tool
- We are also beginning to develop a Consortia Data Statement which will articulate the needs of consortia to have control over data within the system - sharing certain things but not others. The hope is that this would be useful to consider as new features/functionality is being developed in each area of FOLIO
- Our docket also includes beginning to create an outline of needs related to Security and Privacy building on the statement above and including unique needs of consoria consortia related to security and privacy between institutions in a shared environment
- Two items that I am wanting to improve upon and am also seeking input or advice on how to approach
- Tying our efforts more closely in with the roadmap - timing of discussions where to send input/feedback and understanding how to get input from the consortia group to those that need it in time for consideration as features are being developed
- Working more closely with other SIGs to align consortia input with their efforts. It seems it would be a better use of our time to connect with efforts as they are occurring in other SIGs with those having subject expertise than the consortia SIG approaching each topic entirely independently. Perhaps this document will assist with that process and enable more timey outreach between groups.
...
P2 - are supposed to be fixed in the next upgrade. This issues is painful and their there might be a workaround, but is it should take president over new features.
...