[Plato: Develop Experiments] myExperiment search returns nested workflows

[mksplg]

When searching on myExperiment, the endpoint returns workflows with nested workflows that fit the query even if the top workflow does not fit.

[mksplg]

Best solution now is to filter for nested workflows.

Prefixes:
    prefix comp: <http://purl.org/DP/components#>
    prefix prov: <http://www.w3.org/ns/prov#>

Query:
    ?w comp:fits comp:Characterisation .

    FILTER NOT EXISTS {
        ?processor prov:specializationOf ?w .
        ?parent wfdesc:hasSubProcess ?processor
    } .

[kraxner]

Good enough for now, but do myExperiment developers already know about this bug?

[seanbechhofer]

On 27 Aug 2014, at 09:34, kraxner [email protected] wrote:

Good enough for now, but do myExperiment developers already know about this bug?

I’ll pass it on.

Sean

Sean Bechhofer
Senior Lecturer
School of Computer Science
University of Manchester
[email protected]
http://staff.cs.manchester.ac.uk/~seanb
http://orcid.org/0000-0002-5872-3573

[mksplg]

I've contacted the myExperiment team using their feedback mail, they should be aware of it. The answer at that time was:

Unfortunately the RDF we are storing for each workflow/component, doesn't declare that a workflow >is a "top level" workflow, but what you can do is check that the workflow is specifically NOT a nested >workflow like so:

Prefixes:

   prefix comp: <http://purl.org/DP/components#>
   prefix prov: <http://www.w3.org/ns/prov#>

Query:

   ?w comp:fits comp:Characterisation .

   FILTER NOT EXISTS {
       ?processor prov:specializationOf ?w .
       ?parent wfdesc:hasSubProcess ?processor
   } .

Hope this helps.