ISA-tools / ISA-tools/isa-api

ISA converter - use of default configuration - update needed to cope with new assay definitions

Open
#517 0 comments 0 reactions 1 assignee View on GitHub

@proccaserra is already working on this.

Since Jan 8, 2024.

blocker bug documentation
Dominant language
Python
Stars
48
Forks
42
PR merge metrics
No merged PRs in 30d

Description

Symptoms:

Conversion from ISA-JSON to ISA-TAB drops unrecognized assays if measurement type and technology types not found in
/resources/config/json/default by the converter

  • strict requirement on measurement type.term and technology type.term value: exact match needed.
  • strict requirement on protocol_type.term value: exact match needed.
  • strict requirement on the sequence of processes and input/output (no support for optional steps, e.g. optional Labeling events during sample processing

TODO:

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.