openml / openml/OpenML

Cannot change visibility of my dataset

Open
#1,111 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
755
Forks
128
PR merge metrics
No merged PRs in 30d

Description

Description

I want to set the visibility of some of my datasets (e.g. 42584) to "public", but I get an "Error 131" when I try this through the "edit" menu.

Steps/Code to Reproduce
  1. Go to a private dataset owned by the logged in user
  2. Click 'Edit'
  3. Change "Who can view this data" to "Everyone" (or to be more precise, leave it at that value, because the page loads with this field set to "Everyone" already)
  4. Try out different combinations of changing other fields (increasing version, uploading data again, providing url to ARFF file in 'URL' field, filling in / leaving blank the 'State what changed' field)
  5. Click SUBMIT
Expected Results

Visibility is updated: file is publically accessible.

Actual Results

Error 131: Problem validating uploaded description file.

Other notes

Possibly related to https://github.com/openml/OpenML/issues/1048 (and like said there, I am submitting this issue to the OpenML instead of the OpenML.org repo), but that one is trying to add ignored features and therefore changing feature metadata, while I am trying to make the dataset public. One could argue that changing feature metadata means it is in fact a new version of the dataset and should have a new version number, ID, re-uploaded data etc. However, I think there is really no point to the visibility = "private" feature if one does not have the option of changing the visibility to public later without changing the ID, since as far as I can see one can not do anything with a private dataset in that case?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the problem from the edit menu for private dataset 42584, using the listed visibility and submission steps, and inspect the Error 131 response. Trace the dataset update entry point that validates the uploaded description file. Done means changing a private dataset to public succeeds and the file is publicly accessible without changing its dataset ID.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.