6.7.2.2 EventEvidence
6.7.2.2.1 Purpose¶
Links a canonical event to the resolved event it supports, with its role and the groups of attributes whose values it provides. Its revisions rebuild what we believed at any write number.
6.7.2.2.2 Questions it answers¶
- Which evidence supports a resolved event?
- Which source provided the date, the sire or the products?
- Was an event a duplicate or a conflicting statement?
6.7.2.2.3 Fields¶
| Field | Type | Cardinality | Description |
|---|---|---|---|
id |
string (uuid) |
1..1 |
Key. |
resolved_event |
ResolvedEvent | 1..1 |
|
canonical_event |
CanonicalEvent | 1..1 |
|
role |
enum | 1..1 |
Values: primary, supporting, duplicate, conflicting.duplicate: the same record emitted twice by one feed (export artefact). |
wins |
set of enum | 1..1 |
Values: timing, classification, genetics, clinical, quantities.Attribute groups whose values come from this evidence, chosen by SourceReliability. e.g. sire from the breed association, exit type from the most specific compatible source, products from the prescription. |
gap_days |
integer |
1..1 |
Date gap to the primary evidence. |
revision |
RecordRevision | 1..1 |
A link is valid from the write number of its revision until the next one (RecordRevision): this rebuilds what we believed at any time. |
rule_set |
ReconciliationRuleSet | 1..1 |
|
created_at |
datetime |
1..1 |
6.7.2.2.4 Relationships¶
References
EventEvidence.resolved_event→ ResolvedEvent (1..1)EventEvidence.canonical_event→ CanonicalEvent (1..1)EventEvidence.rule_set→ ReconciliationRuleSet (1..1)
Uses types
6.7.2.2.5 Rules & constraints¶
- Links a CanonicalEvent to the ResolvedEvent it supports. Like the cross-reference (XREF) table of MDM systems.
- At a system-time cutoff an included event revision supports at most one active ResolvedEvent revision.
- Link time is system time (write number), not occurrence time; pending evidence may have no published resolution.