2015-06-29 10:51 GMT+01:00 Ian Dunlop <[email protected]>:

> Hello,
>
> I would think that the player will generate its own ids for workflows or
> runs, these will not be related to the myexperiment ids. I don't think the
> player will communicate with myexperiment at all but use the local
> workflows that you upload so there should be no clash of ids.
> Are you having  problems with the player API?
>
No, am comfortable with it. So, what we are saying is that we would have to
upload the workflows from myexperiment to the player then retrieve a run
skeleton so that a user can fill in the required run inputs to create the
run. That is how the API operates.
I was just thinking that this might be redundant, but its ok.

cheers


> Cheers,
>
> Ian
>
> -----Original Message-----
> From: Larry Akah [mailto:[email protected]]
> Sent: 28 June 2015 00:37
> To: [email protected]
> Subject: Taverna Mobile Project
>
> Hello,
> In order to use the Player to create runs for the workflows, the workflows
> must be uploaded to a place where the player can access it. This is so that
> the player can identify which workflow run is requested from the id of the
> workflow as specified in the player API. Since workflows are coming from
> myexperiment, they have their own id's such that if the database that the
> player was communicating with is relational, then one might get conflicts
> when trying to upload workflows through the player. Because i think it
> would be wise to use the workflow id's of myexperiment as the ids used to
> upload them through the player to the specific database (if relational).
> What options do we have or how can we go about that? What information am i
> lacking?
>
> cheers
>
> --
> *Akah Larry N.H*
>
> *Lead Software Engineer @ GiftedMom*
> *Founder IceTeck Inc*
> *www.iceteck.com*
>
> Developing technologies for emergence and sustainable development.
>



-- 
*Akah Larry N.H*

*Lead Software Engineer @ GiftedMom*
*Founder IceTeck Inc*
*www.iceteck.com*

Developing technologies for emergence and sustainable development.

Reply via email to