 |
 |
Thanks everyone for all the helpful hints! Much appreciated :) On Thu, Aug 3, 2023 at 10:35 PM Mike Rylander <[log in to unmask]> wrote: > Hi Thomas, > > The Evergreen ILS's search grammar is fairly well documented at > > https://wiki.evergreen-ils.org/doku.php?id=documentation:technical:search_grammar > and, while the fine details and stock configuration are out of date, > that should serve to explain how we treat different parts of a > complicated search query. For a bit of backend detail on how > Evergreen goes about indexing bib data you can look at > https://wiki.evergreen-ils.org/doku.php?id=documentation:indexing but > that is only a very small part of search indexing these days, as many > new features and functionality have been added since that was written. > > HTH, > > -- > Mike Rylander > Research and Development Manager > Equinox Open Library Initiative > 1-877-OPEN-ILS (673-6457) > work: [log in to unmask] > personal: [log in to unmask] > https://equinoxOLI.org > > On Tue, Aug 1, 2023 at 8:58 AM Thomas Guignard > <[log in to unmask]> wrote: > > > > Hello > > > > I'm looking for examples of functional requirements/specifications for > > search engines for a project that I'm working on. The aim is to provide > web > > developers with a reference as to how search should function, what fields > > in a database should be queried, how to handle wildcards, stop words, > > operators, etc. > > > > If someone has examples of something like this that they've used in the > > past, or of general specs that can be used as a starting point for our > > project, that would be much appreciated. > > > > Many thanks in advance! > > Thomas >