> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchlake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fetchlake Research

> Your research library: collect papers, read them, pull out the key findings and see how they connect.

Fetchlake Research is where you keep the papers, reports and policy documents for a piece of research. You add PDFs (or sync them from Zotero or Google Drive), Fetchlake reads them, and you get a searchable library with extracted findings, citations and a map of how the papers relate.

## What's in it

> [card] [Library](https://docs.fetchlake.com/research/library.md)
>
> The main workspace. Add files, search and filter, read PDFs with notes, and check the AI-extracted details for each paper.

> [card] [Collections](https://docs.fetchlake.com/research/collections.md)
>
> Group papers by project or topic. Each collection has its own settings and can be private or public.

> [card] [Citations and Map](https://docs.fetchlake.com/research/citations-and-map.md)
>
> See which works your papers cite most, and a timeline or network of how your papers connect.

> [card] [Connectors](https://docs.fetchlake.com/research/connectors.md)
>
> Bring in PDFs from Zotero or a Google Drive folder and keep them in sync.

## How the pieces fit

```mermaid theme={null}
flowchart LR
  A[PDFs / Zotero / Google Drive] --> B[Collection]
  B --> C[Fetchlake reads each file]
  C --> D[Library: details, notes, extraction]
  C --> E[Citations & Map]
  B --> F[API queries]
```

1. **Add** files to a collection, by upload or through a connector.
2. **Processing** runs in the background: text is pulled out of each PDF, split into searchable passages, and the paper's details are filled in.
3. **Extraction** pulls the study details (design, sample, outcomes, findings) into a structured record you can check and correct.
4. **Use** the results in the Library, the citation views, or through the [API](https://docs.fetchlake.com/api-reference/introduction.md).

## Where to find things

| You want to… | Go to |
| - | - |
| Add or read papers | **Dashboard → Library** |
| Create or edit a collection | **Dashboard → Collections** |
| Connect Zotero or Google Drive | **Dashboard → Tools → Connectors** |
| Check credits and plan | **Dashboard → Usage** and **Manage Plan** |
| Create API keys | **Dashboard → API Keys** |
| Screen papers for a systematic review | **Dashboard → Systematic Review** (opens [Huxley](https://docs.fetchlake.com/huxley/overview.md)) |

## Getting the most out of it

> [accordion] One collection per question
>
> Keep a collection focused on one research question or project. Citation counts, the map and API answers are all worked out per collection, so a focused collection gives clearer results.

> [accordion] Check the extraction, don't just trust it
>
> AI extraction is a first draft. Open each paper's record, check the fields against the PDF in the reader, and fix anything wrong. Papers marked **Needs review** are the ones to look at first.

> [accordion] Use notes as you read
>
> The reader saves notes automatically next to each PDF. Writing a line or two per paper as you go makes writing up much faster later.

> [accordion] Screen first, then build the library
>
> For a systematic review, screen titles and abstracts in [Huxley](https://docs.fetchlake.com/huxley/overview.md) first, then add only the included papers to a collection here.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.