Skip to content

docs(spec): add data-publishing feature specification - #112

Merged
Anthony Cintron (prbatero) merged 1 commit into
mainfrom
prbatero/feat/data-publishing
Aug 10, 2026
Merged

docs(spec): add data-publishing feature specification#112
Anthony Cintron (prbatero) merged 1 commit into
mainfrom
prbatero/feat/data-publishing

Conversation

@prbatero

Copy link
Copy Markdown
Contributor

Feature spec for Data Publishing & Published Datasets: a Published Datasets section (analogous to the Model Catalog) plus a "Publish dataset" action on model results, routed through a PublishingProvider abstraction with a Local (HASTE storage) provider and a Planetary Computer (MPC Pro GeoCatalog / STAC) provider.

Documents: README (summary + key design decisions), user-stories, ux-spec, design, data-model, plan, impact-analysis, test-plan, rollout. Rollout carries an operator-facing App Settings reference (azd env var -> App Setting mapping, enablement steps, and the operator-owned GeoCatalog grants).

Description

Fixes #

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that changes existing behavior)
  • Documentation update
  • Infrastructure / CI change

Checklist

  • I have read CONTRIBUTING.md
  • My changes follow the project's coding standards (PEP 8 for Python, ESLint rules for JS/TS)
  • I have added or updated tests that cover my changes
  • Python tests pass locally (cd hastelib && hatch run test:pytest) and the UI lints clean (cd ui && npm run lint)
  • I have updated the relevant documentation (README, docs/, inline comments)
  • I have added an entry to CHANGELOG.md if this is a user-facing change

Testing

Additional context

Feature spec for Data Publishing & Published Datasets: a Published Datasets
section (analogous to the Model Catalog) plus a "Publish dataset" action on
model results, routed through a PublishingProvider abstraction with a Local
(HASTE storage) provider and a Planetary Computer (MPC Pro GeoCatalog / STAC)
provider.

Documents: README (summary + key design decisions), user-stories, ux-spec,
design, data-model, plan, impact-analysis, test-plan, rollout. Rollout carries
an operator-facing App Settings reference (azd env var -> App Setting mapping,
enablement steps, and the operator-owned GeoCatalog grants).
@prbatero
Anthony Cintron (prbatero) requested a review from a team as a code owner August 10, 2026 19:05

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@prbatero
Anthony Cintron (prbatero) merged commit c210866 into main Aug 10, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants