| Summary: | Install by default a SRU server with Elasticsearch Koha | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Mathieu Saby <mathsabypro> |
| Component: | Documentation | Assignee: | David Nind <david> |
| Status: | Needs documenting --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | david, philip.orr |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Mathieu Saby
2025-08-25 11:26:58 UTC
Right now you only need to run one koha- command to activate with Elastic. That seems quite OK and as not every library needs it having the service run for nothing might not be what every one would like. I understand your point of view. I thought SRU as a "record search" Koha API, but maybe its use is more exotic. If we maintain the current situation, the need to launch a server command to run SRU should be make explicit on the manual. I was not aware of it before I asked Biblibre why SRU was not working on our Koha... I think it would be useful to add/update to the manual. The SRU page on the manual needs a serious cleanup or rewriting, but that's a larger subject... |