-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same Input/Output over the ARC #67
Comments
Both points (1+2) should be allowed in my opinion. This and #66 points IMO a lot to proper use of PIDs, which in an ARC is basically (or virtually) given via URL to the (referenced) file. And I would suggest to enforce as little as possible. Especially, as long as there is no automated control / warning. But even then, if I were to reuse samples with same name from another ARC, I'd have to rename, which I would not want to. In other words, it would probably be best to not reference a file (e.g. in dataset) just by the name, but by using the (absolute or relative) path to the file ( |
Being able to exactly reference a file also emphasizes one strength of the ARC over using pure ISA. |
Sufficiently covered with
? |
Will close for now. Feel free to reopen if ambiguity issues arise. |
Let's assume a Input/Output called
Sample_1
.Sample_1
multiple times over different assays?Assay_1
, output first table isSample_1
.Assay_2
, output first table isSample_1
.Is this valid? If not, should it be valid? As this could represent a form of "pooling" the input of the tables from
Assay_1
andAssay_2
into the same sample.Sample_1
multiple times over different studies?Same example.
The text was updated successfully, but these errors were encountered: