add example roc metadata
5 unresolved threads
Add a draft for example roc metadata for the fixed script example
Is this runs
or a specific run, aka something like runs/ColumnAddition
?
Yes, in this basic example it was just "runs" so far. But naming it makes more sense
Also F#
?
F# is already referenced in the workflow. We could reference it in both, or just the part where it is specified that it is F#
I think we could reference the workflow used in that run here (hasPart), what do you think?
Not sure whether
hasPart
would be okay here, given it being used to depict filesystem structure in RO-Crate. (Although I agree that it would make sense)An alternative would be
about
. This way the relationshipassay -> process
would be equivalent torun -> workflow
.@wetzels would you also add it to the about section or do you think hasPart could be ok?
I need to have a closer look into this. But first: I would disagree that assay->process is equivalent to run->workflow. Can you elaborate on this @weil?
Now some general question: what are you describing here? To me, it looks like an ro-crate for the workflow/run part of an arc only. Everything else is missing, right? Did you use any of the existing work on workflow-run profiles for ro-crate (https://www.researchobject.org/workflow-run-crate/)?
Whats currently described here is the general workflow in the arc, and the specific inputs used to create the result in the runs folder of the arc. The profile describing the workflow can be found here (CWL), and the execution part is based on that profile.