You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
After completing #122 and #125 it will be easier to keep ISA objects around and modify investigations. However, these issues do not help with manipulating study and assay TAB files.
Describe the solution you'd like
We need similar wrappers that allow for easier querying and manipulation. We will need to be able to:
lookup columns in studies/assays
lookup by column name can/will lead to duplicates, so we need some sort of cursor
most simple: numeric index (then changes must be applied rightmost-to-leftmost)
almost as simple: unique column index assigned when reading from tabs (more stable but cannot be used after serialization/deserialization)
lookup results must contain a pointer/cursor to the annotated Material or Process column
lookup column values in studies/assays
in contrast to the point above, this allows to identify Material/Process or annotating (Characteristics, Parameter, Factor, Comment, ...) nodes
the result pointers must contain a pointer/cursor to the annotated node and the column they belong to
the "pointers" can or even should be unique node identifiers
create new columns in studies/assays
adding characteristics, comments and parameters can be done on the study/assay data structure only
factors must be registered in the StudyInfo
base Material and Process objects must be specified
by default, appended for given Material and Process, but index can be given
remove columns in studies/assays
Note that OntologyTermRef fields correspond to three columns in the TAB and nothing can come in between in the DAG model (which is good).
The above sketches/hints at the interface that we need. Below are some remarks towards an implementation:
prepare operations by collecting args, and structures to replace them
take good care to proper handling of splitting/merging structures
...
Note that writing this issue is still work in progress.
Is your feature request related to a problem? Please describe.
After completing #122 and #125 it will be easier to keep ISA objects around and modify investigations. However, these issues do not help with manipulating study and assay TAB files.
Describe the solution you'd like
We need similar wrappers that allow for easier querying and manipulation. We will need to be able to:
StudyInfo
Note that
OntologyTermRef
fields correspond to three columns in the TAB and nothing can come in between in the DAG model (which is good).The above sketches/hints at the interface that we need. Below are some remarks towards an implementation:
Note that writing this issue is still work in progress.
Describe alternatives you've considered
N/A
Additional context
The text was updated successfully, but these errors were encountered: