The data library exports the website's reference records and their provenance. Choose the file that matches your question: current reading pages, original manuscript destinations, source documents, bibliography leads or bounded evidence mappings.
Choose the right dataset
The reference catalog describes the current reader collection. The original article index accounts for the 8,000 supplied manuscript records, including their original addresses and canonical destinations. These files answer different counting questions because repetitive companions have been consolidated.
For example, several original research manuscripts can now lead to one condition reference. Count canonical routes when asking how many reader pages the catalog describes. Count original source identifiers when auditing attachment coverage. Keep the distinction explicit in any chart or report built from the downloads.
Follow a record back to its source
The consolidation mapping identifies source IDs, original routes, destinations and consolidation actions. The source register identifies exact supporting documents and the scope of their use. Preserve those relationships when selecting a subset of the catalog.
An external publication lead is a separate record type. The bibliography export retains inherited citation metadata and its status. It should not be merged into the source register as though every publication had already been checked against every clinical statement.
What the evidence mapping covers
The section evidence file maps particular structured summaries to source IDs. Coverage is bounded to those mapped sections. Some long-form articles place source links directly in the prose and list documents at the end. An absent row in the section file should be interpreted according to that coverage, rather than as proof that a page has no references.
Read the scope fields before using the data to support a clinical or regulatory conclusion. A dataset can preserve a source statement accurately while leaving its suitability for a new question unresolved.
Verify and preserve an export
Download the relevant files and the checksum list together. A SHA-256 comparison can reveal whether the local bytes match the listed export. It does not assess the truth of the content. Preserve the download date and the checksum file with any analysis that needs to be reproduced.
The release reference explains how to describe a saved copy, and the download guide lists the formats. Check the reuse and provenance page before republishing material or carrying source content into another product.
Are private farm records included?
These exports describe public reference material. They do not contain individual farm submissions, a live case feed or licensed publisher full text. Illustrative examples in the articles show record structure without representing actual farm incidents.