![]() ![]() We also use third-party cookies that help us analyze and understand how you use this website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. Mais la désactivation de certains de ces cookies peut affecter votre expérience de navigation./ This website uses cookies to improve your experience while you navigate through the website. Vous avez également la possibilité de désactiver ces cookies. Ces cookies ne seront stockés dans votre navigateur qu'avec votre consentement. Nous utilisons également des cookies tiers qui nous aident à analyser et à comprendre comment vous utilisez ce site Web. Parmi ceux-ci, les cookies classés comme nécessaires sont stockés sur votre navigateur car ils sont essentiels au fonctionnement des fonctionnalités de base du site Web. Feel free to request the access to edit then – please – add items that could make move forward.Ĭe site Web utilise des cookies pour améliorer votre expérience pendant que vous naviguez sur le site Web. I began to list the advantages for ElasticSearch in Koha I see in the tab “Pros”. You can add your questions in the tab “Questions” or send a mail on koha-devel, it could be used as a faq maybe. You will find a tab called “Way to 18.05”: the idea is to list features missing or incomplete to have a 18.05 clean with no big error and minimal service to search authorities, biblio, making configuration. Depending your feedback I can make it better. I could have put everything in bugzilla or wiki but it wasn’t ideal to me at this time. I integrated the items identified by Nick (kidclamp) in the wiki page (Elastisearch_status). I began a document where I list the gap to this version, it is a work in progress. If you want it, you will have to work for it □ But this work cannot be done only with some developpers in the community. We are planning to fix bugs and enhance actual work for the next months. Then, we would be able to deploy ElasticSearch in 18.11 in the next major update. People could test the search engine with their database and write bugzilla issues to improve the implementation. In a BibLibre point of view, we could imagine 2 customers with their Koha in a testing environment and a 18.05 version. It seems there is some work to do but it would be great to have a more solid version for 18.05 if we test and fix more things, a version for early adopters who want to try it in production. ![]() I explored with some BibLibre guys what we can really do, if we can propose this feature to our users. I knew we can now switch SearchEngine syspref to ElasticSearch in Koha community version, but I didn’t know a lot more. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |