Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Define metadata.yaml schema

See original GitHub issue

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
    [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

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

lacavacommented, May 14, 2020

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

trangdatacommented, May 3, 2020

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Doc-as-Code: Metadata Format Specification | DocFX website
You can use any file format that can represent structural data to store metadata. However, we recommend using YAML or JSON. In this...
Read more >
Define Metadata Schema
Metadata schema is a set of user-defined attributes that extend the system-defined normalized data. The normalized data is generated from the source document...
Read more >
Metadata Format Reference | Hasura GraphQL Docs
Example: A public_author.yaml table metadata file specifying some of the above. table: name: author schema: public array_relationships: - name: articles
Read more >
Configuration schema/metadata
Properties; Types supported in metadata files ... The config_object type is defined in core.data_types.schema.yml as follows:
Read more >
Defining metadata (meta.yaml)
A schema-free area for storing non-conda-specific metadata in standard YAML form. EXAMPLE: To store recipe maintainer information: extra: maintainers: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found