> For the complete documentation index, see [llms.txt](https://help.cabi.org/cabi-digital-library-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cabi.org/cabi-digital-library-help/search/word-stemming.md). # Word Stemming {% embed url="" fullWidth="false" %} Short video illustrating how word stemming works {% endembed %} *** Stemming involves reducing query terms to their most basic form, or stem, and using this to identify all the derivatives of that word such a plurals which should be considered a match. For example, searching for > *initialization* will also return results for *initialize*, *initials*, etc. Results matching the exact query term searched *initialization* will rank higher than its derivatives in the search results list. Stemming can be disabled by using double quotes around words or phrases. Thus it is possible to search for a precise variant of a word including plurals or singular variants of words, for example > *“dog” NOT dogs.* Word Stemming is enabled by default for all publication text fields, such as full-text and abstract. {% hint style="info" %} Note that [wildcards ](/cabi-digital-library-help/search/truncation-or-using-wildcards-for-searching-with-partial-search-terms.md)are not automatically stemmed. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.cabi.org/cabi-digital-library-help/search/word-stemming.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.