Move conception records to a study dataset and report the elapsed days

[labkey-martyp]

Rationale

Moves conception records out of the nbri_ehr schema into a study dataset keyed on the dam and the conception date, and adds an elapsed day count so how far along a pregnancy is can be seen wherever a conception appears.

As a dataset the records pick up the EHR framework's participant handling, QC state workflow and audit behaviour, all of which the hard table had been reproducing by hand — a whole trigger script existed only to announce the modified dam, because the table had no Id column to announce her from. It also leaves the nbri_ehr schema with no tables, though its custom queries stay.

Two consequences are worth knowing when reviewing: existing conception rows are not migrated, and the conception Id uniqueness the database used to enforce is now enforced by the trigger script. The upgrade script drops the old table but does not reload the folder, so an existing container needs a study reload before the dataset exists and the conception form and its queries resolve.

Related Pull Requests

None.

Changes

• Conception records moved to a study dataset filed against the dam, with the conception date as the record date; the old table is dropped without migrating its rows.
• Data entry, the animal snapshot, the dam report, and the birth and pregnancy outcome triggers all read the dataset instead of the schema table.
• The hand-maintained QC state metadata and the dam-announcing trigger are gone, replaced by what the dataset provides natively.
• Conception Id uniqueness is now enforced by the trigger script rather than a database constraint.
• Each conception carries a calculated count of days elapsed since the conception date, shown on the dam report and beside the conception Id in the animal snapshot's Pregnant field.
• The snapshot reads that count from the cached demographics record, so it can trail the report by up to a day.