You need to have configured and installed an omixed server, created a resource, and to be familiar with its API. It also helps if you have written Taverna workflows before.
Download and install Taverna 1.7.1 (not Taverna 2, another version of the plugin will be made available for that). Launch Taverna.
Once Taverna starts up, go to Plugin Manager -> Find New Plugins -> Add Plugin Site. Enter the URL "http://www.omixed.org/taverna/plugin/", and add the plugin, calling it omixed resources (the name is up to you).
Then, tick the checkbox marked Omixed 0.3 and hit Install. Well done. Make yourself another cup of coffee. Once installed close the plugin manager windows to get back to the main Taverna window.
Restart Taverna.
Under the Available Processors tree, a new top-level node should appear called "omixed - http://www.omixed.org:8080/", expand this to find two children nodes : "server" and "admin".
The services on omixed.org contain a few reference demo resources, but in this tutorial we will add a new custom omixed server and use this instead.
Right click at the top of the Available Processors tree and you should see at the bottom a new "add omixed scavenger".
You can use this to point to your own omixed server installation, e.g. in my case I added "http://localhost:9090".
The omixed server provides two endpoints giving full control of omixed resources. The first endpoint, known as the server endpoint, is designed for most users who want to browse, download, or add to or modify existing resources. The second point, known as the admin endpoint, is designed for administrators to create and delete resources, assign schema to them, and modify user privileges.
First, expand the omixed @ http://localhost:9090 node, expand the server node, and right click on the connect method, then select "Add to model".
You should now see a blue connect box appear in the middle of the workflow diagram, as well as a new Processor node appear in the Advanced Model Explorer.
Now right click on Workflow Inputs (in the Advanced Model Explorer), and create a resourceName, a userName and a password input.
Now create a sessionID output by right clicking on Workflow Outputs.
Now hook up the inputs to the connect Processor's input parameters.
Hook up the connect's return to the workflow's sessionID output
You now have your first complete omixed workflow
Run the workflow, supplying login parameters for an already created resource on your server, in this case we used a resourceName of testing123, a userName of tester and a password of 123.
The workflow should return a sessionID if the connection succeeded.
Now let's add another processor to the workflow, getItemTypes.
Add the sessionID output from connect as an input to getItemTypes
Add an itemTypes workflow output and hook it up to the output from getItemTypes.
Rerun the workflow now and view the item types for this particular resource..
To get the itemIDs, you first need to generate a "partialItemID" for each itemType. This is essentially of the form "omixedDomainName/resourceName/itemType". There is a helper LocalWorker included in the plugin to facilitate this process. In the Available Services, expand the Local Services ← Local Java Widgets ← omixed and add the "makeItemID" LocalWorker processor to your workflow.
Now you can take the return output from "getItemTypes" and pass that as the "itemTypeName" parameter of "makeItemID". Leave the last two "makeItemID" parameters blank.
Add a getItemIDs Processor to your workflow, and pass the output from "makeItemID" to its "partialItemID" parameter.
Run the workflow and look at the item IDs in the resource.
Add the "getItems" Processor to your workflow.
Set the link expansion depth parameter to 0.
Hook up the "getItemIDs" output to its "partialItemID" parameter.
Run the workflow and view the results.
