Refreshing an existing goat's record from ADGA
Already have a goat in MyGoatHerd with missing or outdated details? Here's how to bring supported registration and pedigree fields from ADGA into her existing record and choose what to replace.
Before you start
- When to use this: use ADGA HTML Update instead of Add Goat when the goat already exists in your herd — for example, she was entered by hand before you had her ADGA paperwork, and her pedigree still shows "Not recorded."
- Before you start: sign in to your ADGA account at app.adga.org and your MyGoatHerd farm account in two browser tabs. Use a desktop browser to save the fully rendered ADGA pedigree page; you can read this guide on a phone.
- Who can follow these steps: farm owners and admins are the only roles that can add or update goats. Farm hands can read both tutorials, but should ask an owner or admin to make these changes. The farm must also have write access; adding a new goat requires available counted-goat capacity.
- For an existing goat, the update review keeps the goat's current breed available for comparison even if that breed was later disabled in Farm Settings. A different ADGA breed is imported only when it is enabled for the farm; unsupported or missing values stay out of the selected updates.
- A successful parent update can offer an optional progeny pedigree sync. It appears only after an inheritable pedigree change when linked progeny have a different branch to review; it never silently overwrites those records.
1. Spot the gap
Rousey is already in the herd, but her breeding lines all read Not recorded — she was added before her ADGA pedigree was on hand.
2. Open her Pedigree tab on ADGA
In your ADGA tab, search for the goat and open the Pedigree tab so the full generational tree renders on the page.
3. Save the page as a complete webpage
Press Ctrl+S on Windows or Command+S (⌘S) on Mac, or choose File → Save As. Name the file after the goat (Rousey), set the format to Webpage, Complete, and save it to the same folder you use for these files.
Choose the saved .html or .htm file, not its companion resource folder, a PDF, or a web archive. MyGoatHerd reads the file locally without running scripts or loading linked resources.
4. Open ADGA HTML Update on her existing record
Back in MyGoatHerd, go to Rousey's record and click More → ADGA HTML Update. This is different from Add Goat — it updates the goat you already have instead of creating a new one. Use the More menu on the goat's record, not the mobile navigation's More tab.
5. Upload the saved file
Click the upload area and choose the Rousey.html file you just saved. Check that the imported registered name and registration number belong to the existing goat before continuing.
6. Review what changes — and resolve conflicts
MyGoatHerd lines up each supported imported field, current value against ADGA's value:
Newly filled fields (registered name, reg ID, sex, tattoos) are checked automatically where the existing field was empty. Review these selections too.
Unchanged fields already match and are left alone.
Conflicting updates — here, Date of Birth, where the existing record said 2021‑11‑02 but ADGA says 2024‑03‑12 — are left unchecked. You decide whether to take the ADGA value.
7. Save the update
Once you've decided on every conflicting field, confirm the required Barn Name and review all selected values. Click Apply selected updates to save. Unlike creating a new goat, this screen does not have a separate overall confirmation checkbox.
Wait for Update Complete, then choose Return to Record after any optional progeny prompt is handled. Selecting a file or checking individual fields alone does not save the update. If the farm is read-only, the server can reject this save; contact the platform administrator to restore write access.
8. Her record is now complete
In this example, Rousey's page now shows the imported pedigree with both breeding lines populated, and accepting her corrected date of birth has recalculated her age automatically.
Your result depends on what was present in the saved page and which updates you selected. Verify the finished record; unselected conflicts should retain their existing values.