# The datasheet corpus lifecycle (admin)

> For administrators: how Probe fetches datasheets, why some are missing, and how to close the gaps so device facts are there to cite.

_Source: E-Sharp (esharp.se) · Probe guide_


*This page is for the administrator who runs the Probe server.*

Probe's device facts always come from **datasheets** — never guessed from connectivity. The datasheets are collected in a **global corpus** shared across all boards. This page describes how the corpus is filled, why it sometimes has holes, and how to close them.

## Automatic enrichment

When a board is ingested, Probe starts enrichment per component: for each part on the board it tries to fetch the datasheet from the catalogues. The facts are then read out of the document and stored globally, page-cited, so the next board with the same part already has them.

## Why a datasheet is missing

Distinguish two cases:

- **Empty corpus = never fetched.** If no board carrying a part has ever been ingested, no enrichment has been triggered for it. Empty then means "never fetched", not "fetched and came back empty".
- **Fetch failed.** A datasheet behind a form wall, a 404 or a "not found" can't be fetched automatically.

The fleet overview shows datasheet gaps and enrichment status so you can see where the holes are.

## Upload it yourself

Datasheets that couldn't be fetched automatically you upload straight to the corpus. That's the normal route for form-walled or hard-to-reach documents.

## Unreadable or wrong documents

A document that can't be read by machine, or that doesn't name the part it concerns, should be flagged so it isn't wrongly tied to a component. Facts must be attachable to the right base part with a page citation.

## New revision: supersede

When a datasheet gets a new revision you **supersede** the old one, and the facts that rested on the old revision must be re-read. That keeps the citations correct against the document that actually applies.

## Tables, register maps and device models

Beyond body text, structured data can be read from the datasheets: **parametric tables** and **register maps** (address, reset, bitfields, R/W), plus device models like BSDL and IBIS. These are the basis for component selection and firmware questions (see [component selection and firmware data](/en/probe/support/component-selection-and-firmware-data)) and for signal-integrity checks.

---

*Probe is E-Sharp's design-review engine. Device facts are cited from datasheets, never from connectivity — cite or abstain.*
