Current PMA Beta guidance
Resolving PMA Import Review Findings
Understand every staged-row classification, inspect duplicate evidence, choose an explicit action, export rejected rows, and prevent uncertain records from becoming authoritative data.
Purpose
Import Review is the decision layer between parsed source data and PMA’s authoritative records. A warning is not validation, and a potential match is not permission to merge.
Before you begin and permissions
- Owners and administrators can record import-review decisions and perform final execution.
- Managers and other non-administrator roles cannot change staged import decisions.
- Read-only roles can review results only where their normal organization permissions allow.
Step-by-step workflow
Ready to import
Required values are present and no warning or duplicate evidence is active. Review the normalized record before leaving Create new selected.
Ready with warning
The row can proceed, but a non-blocking transformation or missing recommendation needs awareness. Read the evidence before confirming.
Needs user review
PMA cannot prove a safe action. Resolve the issue, skip the row, or keep it blocked.
Missing required data
Add the missing required identity or species information in the source or mapping. Do not invent a placeholder solely to pass validation.
Possible duplicate
Compare the proposed row with the potential existing record and supporting evidence. Choose Create new, Update existing, Skip, or Resolve manually; PMA never silently merges.
Unsupported value
Keep the source evidence, correct or map the value, or exclude the row. Unsupported genetics notation must not become verified genetics.
Relationship unresolved
Review sire, dam, Housing, or other relationships manually. PMA does not invent lineage or assume Housing from proximity.
Excluded
The row is deliberately outside this execution plan. Exclusion remains part of the review evidence.
Clear the final blockers
Execution remains blocked while manual-review decisions, invalid required data, unresolved relationships, or undecided duplicates remain.
Download and recover
Download rejected rows, safely cancel before confirmation, and reopen interrupted sessions. Completed sessions and warnings remain available in history.
Expected result
Every staged row has one visible classification and explicit decision, unresolved uncertainty blocks execution, and successful execution preserves an auditable execution record without deleting or silently overwriting existing records.
Safety boundaries
- No staged import writes authoritative records before explicit final confirmation.
- PMA never silently merges animals, invents lineage, confirms uncertain genetics, or guesses Housing assignments.
- Verified settings and existing records are not silently overwritten.
- Sample records must remain clearly labelled and separately removable from real records.
- A PMA readiness recommendation is not professional husbandry, veterinary, biosecurity, legal, or facility certification.
Troubleshooting
Update existing is unavailable or unsafe
Confirm the duplicate target and evidence. If the match is uncertain or verified fields could be overwritten, keep Resolve manually or Skip.
A recovered older batch is blocked
PMA conservatively recovers clean staged rows. Duplicate and error rows remain Resolve manually until reviewed.
Rejected-row download is empty
Change the filter or confirm that the current plan contains blocking, unsupported, excluded, or unresolved rows.