Define metadata.yaml schema

Here’s what I’m thinking for the metadata.yaml schema. We can set up CI to validate this schema (potentially with jsonschema?)

Then a README of summary statistics/csv files can be automatically generated (which will allow for easy querying such as this).

hashid: # required, hash id of the dataset
dataset: # required, dataset name
description: # required, dataset description
source: # required, link to the source from where dataset was retrieved
publication: # optional, study that generated the dataset
task: # required, classification or regression
columns: 
    [column_name]: # can be 'target'
        type:  # required, either continuous, nominal or ordinal
        description: # required, what the column measures/indicates, unit
        code: # optional, coding information, e.g., 'Control' = 0, 'Case' = 1
        transform: # optional, any transformation performed on the column, e.g., log scaled

[lacava]

@trang1618 maybe you can open new issues about renaming datasets and renaming feature names

[trangdata]

I added first example metadata.yaml file but two things I would like to change:

• feature names should use _ instead of .
• similar for dataset name: it would be nice to have red_wine_quality instead of red-wine-quality.

If we were going to make this an example, I think we should make the changes on the dataset first before moving on.