This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.
Use three linked records
Start with an animal record, a birth-litter relationship and a sequence of group assignments. Give each animal one stable working key. Keep the original identifier wording alongside it rather than replacing the source document with a newly formatted label.
The birth relationship answers which litter the original record assigns to that animal. An assignment event answers which foster group the later record places it in, and from when. Those fields serve different questions. A single editable column called “dam” cannot reliably preserve both.
| Record | Fields that make the relationship inspectable |
|---|---|
| Animal | Working key and original identifier context |
| Birth relationship | Recorded birth dam, source litter and supporting record |
| Assignment event | Animal, previous group, new group and actual date precision |
| Observation | Subject, observation time, author and original wording |
| Correction | Affected entry, revised link, reason and entry date |
These are suggested data fields, not instructions for making a fostering decision or carrying one out.
Reconcile a transfer without creating another birth
In this fictional ledger, litter A contains twelve recorded piglets and litter B contains eight. A later assignment record moves three identified members of A to foster group B. After that event, the current group counts are nine and eleven, totaling twenty. The birth-litter counts remain twelve and eight, also totaling twenty.
If a summary adds the three foster assignments to the birth total, it reports twenty-three animals from records that identify only twenty. If it rewrites the three animals' birth relationships as B, it loses the original cohort. Preserve the two views and label each total with the relationship it counts.
A group-only transfer note may not identify the individual three. Keep that limitation rather than inventing their keys from the next available roster. A later correction can resolve a link when supporting records exist; it should retain what was previously uncertain.
Put observations on the roster valid at that time
Suppose a note about group A is recorded before the assignment event. Joining that note to today's roster would attach it only to the nine remaining members. The earlier note described a different recorded membership. Retain the earlier roster or the assignment history needed to reconstruct it.
The converse matters too: a group-level note does not become an individual finding for every member merely because a database join can copy it into twenty rows. Store its original subject and scope. If a separate individual record exists, link it without expanding what the group note established.
Keep the source behind each relationship
The W3C PROV overview describes provenance through data, activities and the people involved. Here, that general idea means retaining the note, its transcription and the person who resolved an assignment. The table and fictional arithmetic are original applications of that idea.
Before releasing a summary, ask another reader to recover both the birth-cohort view and the group-at-date view from the same file. Use the sow-record comparison guide for changes in recording rules and the correction timeline guide for later revisions. The finished account should make its grouping rule visible without supplying a biological explanation for the recorded events.
Keep a goat kid’s separation distinct from its birth identity
Retain the kid and birth-doe references, actual separation time or interval, receiving group and responsible caregiver. A separation does not necessarily mean the kid joined a foster dam. Record the arrangement actually supported rather than choosing the nearest form category.
Keep observed nursing, documented feeding and later clinical findings under their own times. A planned routine is not proof of completed intake, and proximity to another doe is not a recorded nursing event. Use the goat veterinarian’s appropriate plan and preserve the handoff when caregivers change. The goat hub supplies the species reading path.
Cite this reference
LivestockDefense. “Keep birth relationships and later rearing groups in separate records.” Updated 2026-10-31. https://livestockdefense.com/guides/cross-fostering-records-that-obscure-disease-timelines/
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 ↗Sources & boundaries
Read the evidence in context.
These documents support the statements identified in this reference. Check their scope and dates when deciding whether they answer your question.
- World Wide Web Consortium: An Overview of the PROV Family of Documents
Source update: 2013-04-30. Most recent check: 2026-10-30.
Non-normative overview definition of provenance; original record-linking application only. No official animal-identification requirement or movement authorization established.