Dear Wiki user, You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.
The "DebianMed-Taverna-20110130" page has been changed by AlanWilliams: http://wiki.debian.org/DebianMed-Taverna-20110130?action=diff&rev1=7&rev2=8 A linux-only use case will have aforementioned tab for selecting, which will be used to choose one of the taverna-wide invocation environments. This makes sense on windows and linux machines, because even when running on windows, the user will not be able to create an invocation environment to use local execution. + == Reading and publishing tool descriptions == + + Keep descriptions in workflow. Descriptions have a UUID and, if non-template descriptions, they have a reference to the source from the repository. When loading/running the workflow, check UUID against repository (if any) and prompt user to update or use old. On a server, it should either always take the latest from the repository or from the workflow. Best to take those in the workflow. + + For publishing back. Needs to be curated. Descriptions need version. Need long term plan for this e.g. go for Heroku. Also need UI for creating use cases, or restrict to upload from Taverna. Taverna would need to know about possible repositories. + + Talk to BioCatalogue people. At minimum would like to know about UseCase repositories and to synchronize with them. + _______________________________________________ debian-med-commit mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-med-commit
