Give documents stable identities
Create a source ID that remains the same when an article title or website layout changes. Record the title, publisher, exact URL and any persistent publication identifier. A general publisher homepage can be a discovery link, but it cannot identify the particular page supporting a disease-specific statement.
Retain the source’s original identity when combining imported bibliographies. A local inventory ID and a DOI or PMID are related identifiers, not interchangeable evidence of what was inspected. If two entries appear to describe the same paper, resolve their metadata before merging away differences.
Keep dates and status separate
Use distinct fields for the publisher’s date, the date the source was accessed and the date a particular statement was checked. Leave an unknown publisher date unknown. A successful page fetch today does not prove a source was updated today or that every claim in it was assessed.
| Register field | Question it answers |
|---|---|
| Source ID | Which document is being referenced consistently? |
| Exact location | Which page, section, table or figure supports the statement? |
| Source date | When did the publisher issue or update it, if known? |
| Check date and scope | What was compared with the source, and when? |
| Rights note | What may be retained or reproduced? |
| Reviewer field | Who actually reviewed it, if anyone? |
Do not fill a reviewer field with the name of a paper’s author, a publisher or a veterinarian mentioned in an article. Those people have not thereby reviewed the reference website.
Map bounded statements
Write the statement in plain language and connect it to the relevant source section. Name the host, place, period or test context when those limits matter. A source may support one part of a paragraph while the worked example is original explanatory material; the mapping should make that distinction clear.
In an illustrative register, a paper title mentions a disease and a country. That entry is a useful lead. It does not yet support a prevalence percentage, a treatment recommendation or current occurrence. The status should remain bibliographic until the necessary contents are obtained and checked.
Preserve revisions and conflicts
If a source changes, record the new access event and determine whether the supported statement needs revision. Keep the earlier claim and correction history where appropriate. Do not silently replace an older citation with a newer page that has not been checked for the same assertion.
When sources disagree, store the disagreement and the relevant context. Different species, methods or case definitions may explain the apparent conflict. Do not average incompatible results or select whichever sentence best fits a planned conclusion.
Make the register useful to the reader
Display readable titles and source scope rather than a wall of unexplained IDs. Let readers move from an article to its references and from a source to the statements it supports. Keep private working notes and licensed content outside public downloads unless their release is appropriate.
The source register shows document-level records, and read a source explains interpretation. Pair those views with the data downloads so exported metadata preserves the same distinctions as the visible pages.
For a machine-readable evidence ledger, give each mapped statement an ID and retain its article revision, source ID, relevant location and bounded supported wording. Export that relationship separately from bibliography rows. A source appearing in the register is not, by itself, evidence that every sentence in the article was compared with it.
Questions when maintaining the register
Does a source title establish its findings?
Keep it as a bibliographic lead until the relevant contents are inspected. A title can identify a useful document without supporting a prevalence estimate, intervention claim or current event statement.
Can a working link earn a new claim-check date?
Record the check actually performed. Availability, document identity and statement support are different scopes. A successful fetch should not imply that an entire article or paper was scientifically reviewed.
What should happen when a source supports only part of a section?
Narrow the mapping to the actual supported statement and retain the relevant limitation. Label original fictional examples as explanatory material rather than attributing their invented details to the source.
In a second fictional register, two records share a title but refer to different editions. An automatic deduplication merges them and leaves the earlier claim attached to the newer edition without inspection. Preserving edition identity and the claim relationship exposes the unsupported transfer. The source register should make such differences visible while allowing confirmed duplicate metadata to be reconciled. Its value is a traceable statement-to-document relationship, not an impressive count of links or an invented reviewer name.
Cite this reference
LivestockDefense. “Build a source register that connects statements to documents.” Updated 2026-11-03. https://livestockdefense.com/guides/building-a-veterinary-source-register-for-a-reference-website/
Add the date you accessed the page. This identifies the current reference; keep a permitted saved copy if your work depends on its exact wording. A citation alone does not establish support for a claim.
How to cite a page and its revision ↗