Page Comparison

...

• Housekeeping:
  • No meeting July 26th
• Update from dev:
  • Issues with Kafka configuration prevent Elasticsearch completing re-index.  It is being addressed but until it is resolved there are problems with ES indexing
  • MSEARCH-116 Instance - support full text search notes field
  • MSEARCH-117 Holdings - support full text search notes field
  • MSEARCH-118 Items - support full text search notes field
• Continue reviewing Inventory search use cases: Inventory Search Use Cases
  • Electronic access - currently implemented  - are they any gaps we need to discuss?
    • MSEARCH-109
    • MSEARCH-110
    • MSEARCH-22
  • Revisit holdings and items call numbers (normalized and eye readable)
  • Revisit contributor exact match search

Notes:

1. Issues with Kafka configuration prevent Elasticsearch completing re-index.  It is being addressed but until it is resolved there are problems with ES indexing
   1. In the Bugfest environment, 2 million records were indexed out of the 8 million. This is why records in Inventory that were searched for in the last meeting were not returned.
   2. The configuration uses the same instance of Kafka that is used in other environments. Messages between Inventory and other modules, among them Elasticsearch, are not transmitting because there is no identifier in place to verify destination.
   3. Hot fix for Iris released to handle this issue.
   4. Will be released in Juniper as well.
2. MSEARCH-116Instance - support full text search notes field
   1. Separate search for HRID, search for identifier (all) in place.
3. MSEARCH-117Holdings - support full text search notes field
   1. Public notes already searchable; staff notes separately searchable in development. Should be done by the end of sprint (backend only—functionality not currently available through UI)
4. MSEARCH-118 Items - support full text search notes field
   1. Charlotte checked with UI WG on circulation notes and was told they would like for check in/check out notes to be searchable as well.
5. MSEARCH-22, MSEARCH-109, MSEARCH-110 Instance, Holdings, Item - support keyword search within electronic access fields
   1. Instance level support available through UI; holdings and item level support finished on backend (not currently available through UI)
6. Keyword all = search all indexes at the instance record level. Holdings/items would be nice to have.
   1. Will come back to this to make sure we are all in agreement. Magda will reach out to dev team to talk about details.
7. Holdings and items call numbers (normalized and eye readable)
   1. https://docs.google.com/spreadsheets/d/1Yi4jhnqv9MytlyR-xahTfijWbM8JMomAyW7Q9PpqRt0/edit#gid=0 (call number spreadsheet from Charlotte)
   2. Normalized search = may not be formatted correctly (spaces/punctuation added/omitted)
   3. Eye readable = matches call number exactly
   4. Shelving order = machine sortable. Unlikely to ever search by shelving order.