Standards & Workflow Changelog
This changelog tracks user-facing changes to standards guidance, ontology workflow docs, and FSAR/SPSR integration paths.
Canonical
Active
Guidance
Entry template
Use this structure for each changelog item:
- Date: YYYY-MM-DD
- Area: ontology / salmon data package / FSAR workflow / SPSR intake / publishing
- Change: what changed
- Reason: why it changed
- Impact: who should care and what to do next
- Links: PR/issue/pages
2026-02
2026-02-25 — terminology normalization + FSAR workflow refresh
- Area: salmon data package + FSAR workflow + SPSR intake
- Change: replaced user-facing SDEP wording with “salmon data package”/“SDP”; added canonical markdown spec links to
smn-data-pkg; updated FSAR workflow guidance to reflect current SPSR CUYear-first intake direction and template-first upload prep. - Reason: keep terminology aligned with current naming and reduce confusion between overview pages and canonical spec sources.
- Impact: contributors should use “salmon data package” wording in docs and rely on SPSR template endpoint + canonical GitHub specification for field-level implementation details.
- Links:
2026-02-20 — ontology docs consolidation + FSAR/SPSR alignment
- Area: ontology + standards hub + workflows
- Change: integrated ontology conventions guidebook into DSU docs; retired duplicate term explorer path; rewired standards pages around canonical ontology docs + salmon data package + SPSR intake.
- Reason: reduce duplication and keep one formal source of truth.
- Impact: contributors should use WIDOCO + conventions guidebook for term semantics and use updated FSAR/SPSR workflow pages for intake.
- Links:
2026-02-20 — semantic system entry path made explicit
- Area: standardize/publish workflow pages
- Change: made DFO Ontology → salmon data package → metasalmon → Salmon Data GPT → SPSR path prominent at top of key workflow pages.
- Reason: make the intended system flow obvious during standardization and publishing.
- Impact: data producers should follow the explicit entry path before upload or external release.
- Links:
2026-02-20 — branded semantic start page added
- Area: standards IA + homepage/navigation
- Change: added a branded front-door page for the full path, with one primary CTA: Start my FSAR intake path.
- Reason: provide a single obvious entry point before users branch into detailed pages.
- Impact: new users can start from one page and follow the canonical sequence without guessing navigation order.
- Links:
Quality checks (CI)
Automated checks are configured to catch:
- legacy namespace/content patterns in active docs
- broken internal local links in active
.qmdpages
CI workflow file: .github/workflows/docs-quality.yml