codalab / codalab/codabench

Codabench Datasets

Open
#1,898 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement Post-it
Dominant language
Python
Stars
176
Forks
74
Avg merge
5d 3h
Merged PRs (30d)
21

Description

Datasets updates

RELEASE 1 (Done, Solved by #1955):
  • new page for public datasets
  • filters like competitions page for searching
  • new properties in datasets page (name, description, uploader, uploaded when, size, downloads, verified
RELEASE 2 (Done, Solved by #2050)
  • add croissant metadata for public datasets
  • fix license not added to db on dataset creation
RELEASE 3 (To be discussed)
  • Field for citation (also in json-ld)
  • Field for version (also in json-ld)
  • Documentation (Markdown) about data format and reading, source of data, references, etc.
  • Type (tabular, images etc)
  • Size (number of examples)
  • Tags (multiple)
  • Mechanism to update verified flag (verified by admins for quality and safety)
  • How to handle revisions or versioning of datasets?
    It should not be possible to update verified datasets, or at least updating should break the verified flag.
Suggestions (from Adrien)
  • Having an unique DOI for each dataset
  • Progress bar during upload

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

Start by reviewing the unchecked Release 3 items and suggestions, then inspect the existing public dataset page, metadata/json-ld, dataset creation, and upload flows. Before implementation, narrow the issue to an agreed subset with acceptance criteria; done should mean the selected dataset fields or behavior are implemented and their handling is documented and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.