Clarify why we need ElasticSearch
Open
@tcouch is already working on this.
Since Sep 22, 2021.
end stage
Search
Technical
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Estimate: 3 days
Most of the search requirements can be satisfied by Postgres (partial search, search by similarity, etc.). Perhaps we can get rid of ElasticSearch altogether?
From the Reqs doc:
| Search mechanism for ancient texts, summaries and comments, to accept terms in English, Latin and Greek. |
|---|
| Search should account for different spelling variations, symbols and grammatical forms, whether by use of wildcards ("*"), automatic substitution (e.g. v ↔ u) or more sophisticated rules |
| Search should not be affected by editorial symbols and other non-textual characters. |
| Option to restrict search to text in particular fields (e.g. fragment text, testimonia text, antiquarian essay), or to search across all content |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.