Skip to content

feat(registry): map the datasets file selector and versions refusals - #10

Merged
jm-rivera merged 2 commits into
devfrom
feat/datasets-selector-mappings
Oct 23, 2026
Merged

jm-rivera merged 2 commits into
devfrom
feat/datasets-selector-mappings

Conversation

@jm-rivera

@jm-rivera jm-rivera commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Maps the refusals that two dfo-apis datasets routes serve, so the dfo-apis registry binding test passes once its spec-kit pin moves here. No new codes.

  • datasets.files gains GET /api/datasets/{id}/{content_version}/file, which selects a stored version's file by format, bundle and layout and renders it when it is missing. It refuses request_invalid (400); excel_limit, excel_illegal_character, parquet_size_bound and rollup_not_summable (422); capability_unavailable (501, as on every other endpoint); and internal_error (500).
  • datasets.snapshot gains the open, paginated GET /api/datasets/{id}/versions, which refuses request_invalid (400).

tools/validate_registry.py validates 203 entries, tools/tests passes 53 tests and python/spec-kit passes 259.

`GET /api/datasets/{id}/{content_version}/file` serves under `datasets.files` and refuses `request_invalid` (400), `excel_limit`, `excel_illegal_character`, `parquet_size_bound`, `rollup_not_summable` and `capability_unavailable` (422), and `internal_error` (500). The open `GET /api/datasets/{id}/versions` serves under `datasets.snapshot` and refuses `request_invalid` (400). The registry README names both routes.
The platform resolves one status per code, and every other endpoint answers capability_unavailable with 501.
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.

1 participant