openml / openml/openml.org

Long-term roadmap

Open
#130 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
33
Forks
30
Avg merge
2d 21h
Merged PRs (30d)
6

Description

Feedback gathered from user reviews of the current OpenML website. I'm posting it here to keep track, these can be prioritized and split off into new issues at the appropriate time.

  • It's unclear for many users how to use OpenML. Make a better 'getting started' page and/or video tutorials.
  • OpenML feels unstructured. It lacks high level overview of dataset etc.
  • Difficult to filter on image/vision datasets.
  • Datasets are all public. No way yet to share datasets with a limited group of people
  • Local installation is hard.
  • Limited instructions on how to deploy in organizations. How to upgrade?
  • AutoML 'bots' do not run automatically on new datasets. Many tasks have no results.
  • Donations should be possible (in a non-intrusive way)
  • Lack of integration with other dataset repositories (e.g. Zenodo, Kaggle, data.world, UCI, open government, OpenNeuro, BrainLife.io,...)
  • Trustworthiness of results: how do we know if results are not overfitted/biased?
  • Data/algorithm management: how to correct issues?
  • Handling of large datasets. Need efficient downloading and loading of large datasets.
  • Handling of evolving datasets. E.g. where new data is added every day.
  • Automated tools for checking data quality, fixing issues
  • Collaboration: Need chat/communication/forum to support user discussions/help. Only some users find their way to GitHub issues, and those discussions are hard to find (e.g. https://github.com/openml/discussionboard/issues/35)
  • Collaboration: Streamline interactive model building. Allow people to see and understand each other's models, download and improve them, discuss online,... Maybe have one user/group-assigned 'leading model' per task (not necessarily the one with highest accuracy).
  • Unclear documentation on the security of uploaded data. How to collaborate on sensitive datasets (e.g. medical)?

Contributor guide

No contributing guide indexed for this repository

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

This issue is a long-term roadmap rather than a defined change, and it names no files, tests, or entry points. Split one roadmap item into a focused issue first, then identify the relevant website area and define its acceptance criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.