https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42508
--- Comment #3 from Katrin Fischer <[email protected]> --- Putting patron data on another server with other data if you are using a separate Elasticsearch cluster raises questions at least for privacy documentation but also for other means: is the connection secure/encrypted, is the data kept separate, who can access it etc. I think it's not "could" - it's _must_, because as you say, Elasticsearch is not mandatory. But if we have to maintain another option anyway, I think it makes sense to also have a switch for libraries using Elasticsearch to opt-out of patron search via Elasticsearch. Maintaining 2 separate ways of doing things not always serves us well, because there will be feature differences and extra work included. I wonder if we should not thoroughly investigate improving the SQL based search first. I believe Mark had already identified some of the issues with it. It could turn out some simpler tweaks can already get us a long way. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
