| Table of Contents |
|---|
Background:
In October of 2020, during the Technical Council meeting it was decided to look into Elasticsearch as a possible alternative for the existing Inventory search due to its poor performance and inability to provide exact count of records matching search criteria.
...
- Back-end:
- Sending add/update/delete notification messages from Inventory
- Built Search APIs for searching and faceting
- Combined instances + holding + items into a single index
- Implemented reindex process for existing inventory DB
- Front-end
- Built UI for alternate Inventory search app that represents searching capabilities of Elasticsearch
- Infrastructure:
- Added Elasticsearch cluster to CI/CD and set it up on reference environments
- Updated existing Kafka cluster configuration
- Introduced option of setting up performance testing environment in the community
Instance | Holdings | Items |
Keyword search (title, contributor, identifier) | Keyword search (title, contributor, identifier) | Keyword search (title, contributor, identifier) |
Contributors | ISBN | Barcode |
Title (all) | ISSN | ISBN |
Identifiers (all) | Call Number | ISSN |
ISBN | Holdings HRID | Material type |
ISSN | Call Number | |
Subject | Item HRID | |
Instance HRID | ||
Instance UUID | ||
Electronic access (all fields) |
Instance | Holdings | Items |
Effective location | Effective location (item) | Item Status |
Language | Holdings permanent location | Effective location |
Resource type | Suppress from discovery | Holdings permanent location |
Format* | Tags | Material type |
Mode of issuance | Suppress from discovery | |
Nature of content | Tags | |
Staff suppress | ||
Suppress from discovery | ||
Date created (from, to)* | ||
Date updated (from, to)* | ||
Source | ||
Tags |
POC evaluation:
Proposed next steps:
...