Skip to content

dataset_description requirements #373

@djarecka

Description

@djarecka

I noticed that you changed the requirements that each input requires dataset_description.json file, and I'm wondering if it's really good idea to enforce it (perhaps we can have just warnings?).
And if that's the case, should we create dataset_description.json for the output as well? Right now the output of babs couldn't be used for an input

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions