Publish Your Data
Active Workflow
Canonical Terms Required
Internal + External Paths
Semantic Salmon System — entry path (front and center)
Before publishing, confirm this chain is complete
- DFO Salmon Ontology mappings are finalized
- Salmon data package metadata is complete
- metasalmon validation is clean
- Salmon Data GPT (optional) is used only to draft, not to bypass validation
- SPSR intake is complete for FSAR-oriented workflows
Quick links:
Cookbook Guide
Step 1: Finalize Metadata
Ensure your dataset has:
- complete data dictionary entries
- clear definitions and units
- canonical full IRIs for mapped terms
- contact + provenance + license details
Step 2: Verify Semantic Links
Use GC DFO Salmon Ontology documentation to verify that term IRIs are current and resolvable.
Example row:
variable_name,label,data_type,definition,standard_term_iri
CU,Conservation Unit,string,The conservation unit identifier,https://w3id.org/gcdfo/salmon#ConservationUnitDo not use partial URIs.
Step 3: Build Release-Ready Package
Prepare the package structure expected by your destination workflow:
dataset.csvtables.csvcolumn_dictionary.csvcodes.csv(if needed)- data files in
data/
Reference: Salmon data package specification
Step 4: Validate Before Submission
Run validation checks before upload/publication:
- required fields complete
- data types and date formats valid
- code lists consistent
- all IRI links present and syntactically valid
Step 5: Submit to SPSR for FSAR Workflows (when applicable)
For many FSAR-oriented datasets, SPSR is the operational intake path.
- SPSR docs: https://spsr.dfo-mpo.gc.ca/documentation/
- SPSR upload wizard: https://spsr.dfo-mpo.gc.ca/wizard/1/
- SPSR templates endpoint: https://spsr.dfo-mpo.gc.ca/download_sdp_templates
Upload only after internal quality checks are complete.
Step 6: Publish Externally (if approved)
For external/public release, follow policy and approval requirements:
Keep internal intake (e.g., SPSR) and external publication pathways clearly documented.