Date
Attendees
~ 32 SME's (including guests Vince Bareau and Craig McNally)
Note taker: Laura Daniels (05/19/23), Lynne Fors, Alissa Hafele, Natascha Owens
...
Announcements | Bugfest testrail tickets. As of today 37% testcases are unclaimed. So please, please claim test cases if you are involved in the Bugfest test. Bugfest test will start on Monday 10/23/2023 - 11/3/2023 (Friday). Poppy UAT for the following features:
The form is open until the end of 10/19/23 (TODAY!) | |
overview of the re-architecting proposal | Craig and Vince will attend the meeting to discuss and answer any questions that may arise. All: Please watch the recording in advance:
Related WolfCon23 slidedecks My unsorted questions (Felix):
Questions by Former user (Deleted) Who will decide in general (not only when in dispute) which Apps are "common sense" and must be included in "Functional"? What will be the criteria for this decision? commonality of usage will likely drive which applications belong in "functional" breaking up Inventory will likely be guided by logical purpose, scope of material being managed
| |
to be incorporated into the above? | As Inventory is central, what are potential impacts? How will we in the future be able to trouble shoot bugs which we first identify in the local implementations - if we don’t have a well understood release like the flower release, and can compare with the reference environment for that given release. | |
Charlotte: re slide 9 – thinking about permissions, right now very granular how would permissions management change? still have modules, but creating a layer above that (hierarchically), so module permissions would still exist the application is comprised of a set of modules with same granularity of permissions variety of types of libraries that have implemented thus far, with different models for "source of truth" in Inventory; how does this model impact, for example, the current model for those libraries using a union catalog as source of truth? source record storage would be a separate application from Inventory, so no one would be forced to use it as source of truth dependencies between existing modules make combination into applications very obvious in some cases (e.g., Acquisitions); but Inventory is a different animal – it's not a question of combining as it's already "a monster" application; Inventory needs to be broken up into smaller applications Inventory currently both manages cataloging and serves a more literal inventory role Breaking it up would allow institutions to be more selective about which aspects of Inventory they use (e.g., could choose not to use the cataloging aspects) | ||
PC update | 2023-10-19 Product Council Agenda and Meeting Notes Announcements: New procedure for SIG reporting - SIG Reports 2023-10-19 (note: this places more of a burden on liaisons) CC (The Community Council) will reduce it's number of members. Now: The council will have 15 members but can operate with a minimum of 9. The council will seek to have a diverse membership. Current state of FOLIO Quality Assurance testing - presenter: Yogesh Kumar, and Oleksii Petrenko. Link to slidedeck here (when available) Testing methodology: In Sprint Testing by development teams and Release testing (Bugfest - 3000+ testrail cases)
Example on of a UAT survey (Poppy, 2023) Definitions of Smoke test, Critical path, and Extended Release planning: Release roadmap/time line - e.g. Poppy. Follow up on Re-architecting Impact on the Product Council report: Link to the report here. And then this topic is the main topic here at today's MM-SIG meeting. The PC recognise recognises that the current flower releases are problematic, and the PC are endorsing that the community is going ahead discussing how to implement new definiton definition of applications and platforms, but a further discussion in the tri-council group is necessary, and the PC will suggest check ins around mile stones, to make sure that that stakeholders are being involved, and that re-definition of applications and platforms are not causing new problems. |
...