Overview¶
This section explains the overall data model before the handbook dives into individual source families, evidence files, or report outputs.
bijux-pollenomics is not a single-dataset repository. It combines pollen
context, archaeology context, boundary framing, fieldwork records, human
ancient DNA, and animal ancient DNA recovery work. Those families do not have
the same strengths, the same gaps, or the same publication maturity. This
overview is here to make that mixed system understandable before you move into
the details.
What This Overview Helps You Understand¶
- how the tracked data system is organized
- how the repository moves from source capture to public publication
- how pollenomics-first publishing works across several evidence families
- why animal ancient DNA needs more recovery and review steps than pollen context
- where the main repository-owned data directories live
- how this handbook separates source pages, evidence pages, and output pages
Start Here¶
- Data system overview
- Data architecture handbook
- Pollenomics publication model
- Provenance and publication linkage
- Source selection and refresh
- Coverage and naming
- Cross-domain evidence matrix
- Animal ancient DNA evidence
- Data directory layout
A Good Reading Order¶
- Start with the data system overview to see the full evidence landscape.
- Read the data architecture handbook when the question is where truth lives and how stages differ.
- Read the pollenomics publication model when the question is how these domains are supposed to appear together publicly.
- Open the cross-domain evidence matrix when the real question is balance, not one file family.
- Read animal ancient DNA evidence when the question is about sample-backed animal records and their extra recovery burden.
- Open data directory layout when you need the file-tree view behind those explanations.
Why This Overview Matters¶
Without this framing, the repository can look more chaotic than it really is. That usually happens when a generated report, a source audit, and a normalized evidence file sit side by side without a clear explanation of why each exists or which one governs the claim.
This overview keeps three boundaries explicit:
- source pages explain what enters the repository
- evidence pages explain how one claim becomes reviewable
- output pages explain what the public-facing bundles show
Those boundaries are simple, but they make the rest of the handbook much easier to read.
Restored Foundation Topics¶
- provenance model and publication linkage now live in provenance and publication linkage
- source selection rules, update lifecycle, and rewrite pressure now live in source selection and refresh
- naming conventions, breadth expectations, and layout pressure now live in coverage and naming