Skip to content

docs: add datasets untag migration note #269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Jayant-kernel wants to merge 2 commits into from
Closed

docs: add datasets untag migration note #269

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
04a2c43
docs(migration): document datasets untag behavior
Jayant-kernel Mar 11, 2026
37db660
docs(migration): clarify untag ownership and non-owner error response
Jayant-kernel Mar 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,6 +107,22 @@ For example, after tagging dataset 21 with the tag `"foo"`:
}
```

### `POST /datasets/untag`
The endpoint now enforces tag ownership when untagging:

- The original tag uploader can untag their own tag.
- Administrators can untag any tag.
- Other authenticated users receive an error.

On success, the response matches legacy behavior and returns only the dataset id:
```json
{
"data_untag": {
"id": "21"
}
}
```

## Studies

### `GET /{id_or_alias}`
Expand Down