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
Currently, order information is lost due to the graph transformation. It should be possible to reconstruct an ISA-tab in the same order as imported. Therefore each node needs to keep the info of row origin and the union find algorithm needs to take this information into account. Other applications such as SODAR will benefit from this as well.
I don't think that we need to touch the Investigation as we are using using tuples for enumerating studies and assays and these already have explicit ordering. It's probably the easiest approach to enumerate(...) when importing into SODAR and adding order from there and then just construct the tuple when exporting from SODAR. Also, Python dicts are ordered from 3.6 on (this does not hold for JSONB fields in Postgres).
I think our focus should be on retaining order on the studies and assays on conversion between graph and table. I would not attempt to retain the order of all possible inputs. Retaining order on the sensible inputs is enough plus after the first round trip, round-tripping should not change the file any more.
Requestested by @holtgrewe and @mikkonie.
Currently, order information is lost due to the graph transformation. It should be possible to reconstruct an ISA-tab in the same order as imported. Therefore each node needs to keep the info of row origin and the union find algorithm needs to take this information into account. Other applications such as SODAR will benefit from this as well.
This feature partly overlaps with #46.
The text was updated successfully, but these errors were encountered: