|30 minutes (need to start with this agenda item because we have several guests here just for this issues)||End-user issues with Kiwi version of inventory search|
On Friday Michal Kuklisis planning to document what our options are and pass them on to Charlotte.
Matt Connolly, a member of Cornell's usability group, will be talking to folks at Cornell to learn more details about
1) Steps to move back to the previous search PostgreSQL implementation:
Option a: Rollback changes which introduced Elastic Search and facets:
Option b: Switch search endpoint to use mod-search
c: Integrate facets with the dropdown search input
2) Keep the Elastic Search work (Inventory: UIIN-1566, UIIN-1567, and the new work in the instance look up component) but in the interface we add an option to bring up a drop down menu listing all search options for each segment Instance, Holdings, and Item, and we add a <i> icon with link to more information on how to search using the Elasticsearch (this is easily fixed with a link to the tips and tricks page on the FOLIO Wiki: Search - using Elasticsearch (Kiwi and later releases).
Go with approach 2 will require a dialogue with Cornell (management of customer expectations) explaining all the advantages we achieve when Inventory is using Elasticsearch as search engine (fast performance, accurate result count, facets on the filtering, possibility to do searches using boolean operators).
Notice that during the past 1-1.5 months Cornell has filed several support tickets about searches taking too long, searches not returning results, searches timing out - when using postgreSQL
Time needed: Attempt to absorb into the Kiwi schedule without delays.
|15 minutes||Status update|