• infoModelIssues.png:
  

Person - creator of - data item link

Is the only link between a data item and the person that ran the workflow through person - study participation - study - experiment design - experiment instance - scuflworkflowtrace - actualoutputparameter - lsdocument

I think this means that if more than one person takes part in a study it is not possible to return results created by a certain user.

Status - not confirmed Workaround - use metadata store to link data with its creator (person)

-- ChrisWroe - 09 Aug 2004

Workflow and results

I want to get hold of the workflow that produced a result. ExperimentDesign^? can have many ExperimentInstances^?. These instances are linked to the scuflworkflowtrace and actualoutputparameter. So I can link a design with an output. ExperimentDesign^? can have many Operations which links to operation content from which I can get the workflow. I can't find a link between the operation and the result. I can't go through ExperimentDesign^? because I can't be certain which of possibly many operations are linked to a design.

Status - confirmed problem Work around - assume each experiment design can only have one operation (aka workflow)

-- ChrisWroe - 09 Aug 2004

Updating a workflow

Currently the MIR enactor plugin does not detect when a workflow design has changed. When viewing provenance this becomes a problem because the results produced from a new workflow design are overlayed on the initial version of the workflow.

Status - not confirmed Workaround - Possibly remove the LSID from the scufl definition, to force it to be reassigned a new one.

Linking operation trace to a workflow processor

I cannot find a way to link an OperationTrace^? entity with the Processor in the workflow that was responsible for it.

Status - not confirmed Workaround - place processor name in OperationTrace^? XML script field. I have modified the MIR enactor plugin to fill in this field when running a workflow.

Linking Acutal**Parameter to the ports of a processor

I cannot find a way to link a ActualParameter^? with the corresponding port of a processor that created it. ActualParameters^? have a name field which should possible be filled with the name of the processor port?

Status - not confirmed Workaround - The metadata store currently stores a dc:title for each LSIDDocument resource. This is currently generated from the processor port name that generated it. All the LSDocuments associated with ActualParameters^? are collected and their names retrieved. It would be much more efficient to store the port name in the ActualParameter^? entity.

• personal-page.png:
  

• experiment-instance1.png:
  

• experiment-instance-trace.png:
  

• data-item.png:
  

• mir0_1_20040928.txt: DOT file autogenerated from MIR introspection

• MIR schema visualization (MIRv0_1 20040928):