Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To address the poor performance of the inventory search, the Technical Council recommended to investigate  investigate a possible Elasticsearch implementation.   The scope of the work was determined to include following deliverables for the Iris release: 

...

  • Add Elasticsearch cluster to CI/CD and setup it on environments (k8s conf)
  • Check configuration of existing Kafka cluster

In December 2020 it was determined that , source record storage (SRS) search is out of scope for the has been removed from the scope of Elasticsearch POC and it became a separate feature (UXPROD-2791)

...

The evaluation of the POC took place from April 5th to April 9th, 2021 and it was conducted in the the Bugfest environment (~8 millions records) by eight evaluators librarians representing:

  • Chicago University (2 participants)
  • Duke University
  • Missouri State University (2 participants)
  • Simmons University
  • EBSCO
  • Index Data

Almost all entire evaluation was conducted done trough UI and 75% of those who participate, found the POC successful but all participants saw the room for improvements. The team addressed following issues that were raisedreported:

Issue

Solution

Noisy search results

Implemented searches supporting keyword “all” or “any” limiting the number of matches: MSEARCH-91

Expected results not found

All provided examples were related to the special characters in the Title that were searched using ASCII representation.  The problem will be addressed in scope of  MSEARCH-67

Bug in sorting by title

MSEARCH-99

Support phrase search

MSEARCH-92

Ranking refinement

Refinement of the default ranking system will require further analysis to be in the scope of a separate feature

Discrepancy in saving UUIDs from Action menu

MSEARCH-93 and UISEES-58

UI enhancements and bugfixesbug fixes

UISEES-47, UISEES-57, UISEES-61, UISEES-62, UISEES-48, UISEES-49

...

  • Expected to perform complex queries of multiple fields and across record types (including MARC fields)
  • Expected a different UI more like a catalog or discovery system advanced search
  • Expected support for additional operators (not equal to, starts with, etc.)
  • UI not user friendly
  • Preferred a simple left-anchored search than the provided relevancy ranking

Proposed next steps

...

  • Redesign Inventory UI Search component so that it can include new UI components created by POC, especially filters and facets
  • Conduct usability study for advanced search textbox
  • Use mod-search endpoints for searching
  • Conduct analysis of ranking refinements (weights and boosts)
  • Conduct analysis of further search refinements
  • Define and prioritize work for cross app/cross record types searches
  • Define UI for cross app/cross record types searches
  • Define requirements for cross-tenant searches

...