Date
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/867230970
Or mobile phone one-tap (US Toll): +14086380968,867230970# or +16465588656,867230970#
Or Telephone:
Dial (for higher quality, dial a number based on your current location)
US Toll: +1 408 638 0968 or +1 646 558 8656
Meeting ID: 867 230 970
International numbers available: https://zoom.us/zoomconference?m=HFOYojqG6P0eOobNily-kmpgCrJ9eJQ_
Attendees
Jesse Koennecke Anya, Aaron Trehub, Axel Dörrer, Charlotte Whitt, Christopher Spalding, twliu, Alexis Manheim, John Ballestro, Gang Zhou, Hkaplanian, Ian Walls, Jana Freytag, James Fuller, Janet Ewing, Karen Newbery, Kristin Martin, Kirstin Kemner-Heek, Laura E Daniels, Marc Johnson, Martina Schildt, Martina Tumulla, Maura Byrne, Owen Stephens, Paul Moeller, Sharon Wiles-Young, Stephanie Buck, Tod Olson, Brooks Travis, Peter Murray,
Goals
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Announcements | Jesse |
| ||
| 25 min | Roadmap updates | Kristin |
| Roadmap Update Slides, which includes a link to the Roadmap Themes list. Some work has happened to bring these to a new Roadmap Jira project. UXPROD issues can get linked to themes and subthemes in this new project. Take note of the breadcrumb links near the top of the page to navigate through the hierarchy of the Roadmap project. A next step is working with the product owners to make sure that important work areas are covered. The roadmap group is working on a visualization of the themes. They have also set a completion deadline of November 18 to turn this to the Product Council for spreading to the rest of the project. | ||
| 25 min | Elastic Search in Inventory | Charlotte |
| Widget Connector | ||
|---|---|---|
|
Update about Elastic Search: Search in Inventory using Elasticsearch - Kiwi - Google Slides. As part of development, they included extensive work on facets, but during Bugfest found that libraries need the possibility to have the drop-down menus for the search box before using the facets. The development team went back to determine what could be done in the remaining time before the Kiwi release. The UI developers can do the drop-down menus for the search box with the static filters that the Inventory had under the Postgres search engine, but will not have the dynamic facets with the hit counts. The FOLIO Implementors group reached a consensus earlier this week that the slide 4 plan was the way to go. PC members today registered no objections to this plan. | |||
| 10 min | PC roles for review of significant functionality changes | Jesse | When a new major component is added to the platform...for instance, adding ElasticSearch...there are many downstream impacts to that (for the FOLIO operators, for instance). Adding these components have a cost, so it is important to convey the value of adding the new component. When trying to build the Kiwi release, it caught the devops people by surprise that mod-search was included and that the platform now needed ElasticSearch. What would be valuable to have? Advice from the developing team on how to deploy. Now that ElasticSearch is being used for Inventory, will the technology be used for other modules and apps? The implementation that is there now is quite specific to Inventory, so can it be used in—say—ERM. Can it be assumed to be there? What are the impacts of expanded memory needs, for instance? One role that PC has (in conjunction with TC), is determining whether the component should be used elsewhere. The ElasticSearch proof-of-concept was put in as a test with a separate UI. The intention was that ElasticSearch would be used by other apps as well (such as the Users app). It isn't as simple as a plug-and-play at this point; there is some work that a product owner and development team will need to do. The new components also add dollar costs to expansion...additional infrastructure required to run these components. |
| 15 min | Ranking and Community input group charter | Martina S. | Initially raised by the SysOps SIG and discussed in PC a few weeks ago. Martina, Tod, and others worked on this proposal. As priorities are set, it is important that they remain constant for a period of time, and the process should reflect that. It would be good to check in with the POs about the logistics of the transition period; they have been relying a great deal on the existing rankings. Might this be an annual process? It would be useful to invite SIG members to the working group since it will be SMEs that will have a large part in the ranking process. In the transition, it is also important to try to carry forward the existing rankings that libraries have made. The PC approves the charter as it is now. The working group should form in the next two weeks and come back to PC at that time with the roster of members and any changes to the charter. |
| 5 min | Agenda topic generation | Jesse |