On Mon, Jun 28, 2010 at 15:26, David Withers <[email protected]> wrote: > The myExperiment ID is not stored as part of the workflow so I don't > think there is any way to get at it from a beanshell.
It is possible to use the SparQL endpoint at http://rdf.myexperiment.org/ to look up the workflow ID as defined in the .t2flow: PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> PREFIX dcterms: <http://purl.org/dc/terms/> PREFIX mebase: <http://rdf.myexperiment.org/ontologies/base/> PREFIX mecomp: <http://rdf.myexperiment.org/ontologies/components/> SELECT ?dataflow,?version,?workflow WHERE { ?dataflow dcterms:identifier '206f6ca5-083c-4314-8ff8-8a8c542e1160'^^xsd:string . ?version mecomp:executes-dataflow ?dataflow . ?workflow mebase:has-version ?version } .. but there is currently no way for a Beanshell script to find out information about its owning workflow - meaning that you would have to specify that id manually - either looking in the .t2flow file or as a Taverna plugin you could access Dataflow.getInternalIdentifier() ( or from Taverna 2.2: recordIdentifier() ) -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
