> 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/searching-by-publication-and-article-titles.md).

# Searching by Publication and Article Titles

### **Searching for Publication Titles (e.g. a journal or book)**

You can search for a full publication title in two ways:

1. **Using the "Publication Title" field** in **Advanced Search**
   * Just enter the full title (e.g. *Journal of Dairy Science*).
   * No need for quotation marks – the system treats it as an exact phrase automatically.
2. **Using the field abbreviation `DO:` (Document Origin)**
   * Use this in a standard search (outside Advanced Search).
   * You **must** enclose the title in **quotation marks** or **parentheses** to search as a phrase.
     * ✅ `do: "Journal of Dairy Science"`
     * ✅ `do: (Journal of Dairy Science)`
     * ❌ `do: Dairy Science` → *This will not return correct results.*

> 🔔 **Important**: Only **complete publication titles** are indexed in this field.\
> Partial titles or individual words (e.g. `do: "Dairy Science"`) will **not** return results for *Journal of Dairy Science*.

***

### **Searching for Article Titles**

To search for individual article titles, you can use:

1. **The "Title" field** in **Advanced Search**
2. **The field abbreviation `Title:`** in a keyword search
   * Example: `Title: (zoonotic outbreak)`
   * This will return articles with both words in the title, such as:\
     *"A One Health Zoonotic Vector-Borne Infectious Disease Family Outbreak Investigation"*

✅ **Good to know**:

* All words in article titles are indexed **separately**. You can search for **single words** or **phrases**.
* The **"Title" field** is a combined field that searches across three different metadata fields:

| Field                      | Description                                                                                                                                    |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **ET:** *Article Title*    | Original title of the article (in English or another language). If not in English, both the original and the English translation are included. |
| **AT:** *Additional Title* | Includes titles of special journal issues or series statements for books.                                                                      |
| **CT:** *Conference Title* | Title of the conference (often in original language), along with date and location.                                                            |

You can search each of these fields separately using their abbreviations:

* `et: "agrifood systems"`
* `at: "agrifood systems"`
* `ct: "agrifood systems"`

***


---

# 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/searching-by-publication-and-article-titles.md?ask=<question>&goal=<user_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.