Publish Your Data

Active Workflow Validation Required Internal + External Paths

Use this page when your dataset is nearly ready and you need to choose the correct release path.

Before publishing anything

Confirm this chain is complete:

1. ontology mappings are finalized
2. the salmon data package is complete in metadata/ + data/
3. validation is clean
4. provenance, contacts, and version notes are present
5. required approvals are in place

Choose the destination path

Internal / SPSR path

Use this when the dataset is moving into FSAR-oriented operational workflows.

• keep the salmon data package as the source of truth
• choose the SPSR route scope that matches the data grain:
  • CU/composite
  • SMU
  • Population
• generate wizard or bulk upload files from the same package
• do not maintain a separate spreadsheet-only bulk path

Canonical guidance:

• Salmon data package + guided review + SPSR intake path
• FSAR Data Standardization Workflow

External / public release path

Use this when the dataset is approved for external publication.

• follow classification and approval requirements
• include citation, version, provenance, and licence information
• document how the public release relates to any internal operational package

Canonical guidance:

• Publishing Data Externally

Release checklist

• package metadata is complete and validated
• release scope is clear (internal SPSR, external publication, or both)
• route scope is documented for SPSR submissions
• upload or release artifacts trace back to the same package version
• approvals and contact information are current
• release notes are archived

Cookbook spotlight

If your near-term publishing task is a CU/composite escapement submission, use the focused recipe:

• CU/composite escapement estimates for package-first SPSR intake

Next Steps

• FSAR Data Standardization Workflow
• Salmon data package + guided review + SPSR intake path
• Publishing Data Externally