Skip to content

TSV parser object needed (with json schema) #73

@luiskuhn

Description

@luiskuhn

I will make sure to create this documentation and the suggested TSV parser object, but I would suggest making that another card, since that directly relates to the defined metadata model for each imaging modality (which I am still working on), input validation and controlled vocabulary. There I think we need to go the same route as for the nanopore data, but I see that separate from building/testing the functionality to ingest metadata to the omero server as key-value pairs.

Ok, but then please create an issue in this repo that this is not forgotten. This needs to be done before it is roled-out in production.

Originally posted by @sven1103 in #71 (comment)

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