Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Trace cardinality across normalization and persistence
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
For missing-related-entity investigations, check cardinality at every boundary: provider payload, normalized contract, creation helper, persisted rows, and UI projection. A model that supports several entities does not imply every ingestion path preserves them; successful import or enrichment can still omit secondary entries when normalization selects only a primary. Distinguish simultaneous entities from replacement assignments. A refreshed snapshot establishes what was available at fetch time, not what existed at initial creation. A summary flag should not substitute for actual populated slots without a documented provider contract.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review