60 likes | 206 Views
Overview. Summary of the activities for the past two weeks Forthcoming deliverables Development plan for the following period. External Tools Specification Meeting . To discuss specification of external tools services and using BioCatalogue to store and enable search over them:
E N D
Overview • Summary of the activities for the past two weeks • Forthcoming deliverables • Development plan for the following period
External Tools Specification Meeting • To discuss specification of external tools services and using BioCatalogue to store and enable search over them: • Present: ONB, BL, Taverna team and Jits (representing BioCatalogue) • Minutes available at: http://tinyurl.com/3gsul4g • Existing tool specs (by British Library) can be found at: https://github.com/openplanets/scape/tree/master/xa-pit/src/main/resources/toolspecs • At the moment,BioCatalogue only supports storing Web service descriptions • Short term solution (proposed by Jits; user partners agreed: store the tools descriptions in myExperimentas tagged "files: • Pros: This gives us something quick to start with • Cons: "files" on myExperiment can only be searched by tags, title and description and there are no rich annotations capabilities such as for Web services in BioCatalogue • Long term solution: extend BioCatalogue to support adding, annotating and search of SCAPE preservation command line tools (which is also one of our deliverables – Milestone MS40)
Extending BioCatalogue With Support for Command Line Tools Meeting • To discuss with Jits what we would need to do to extend the BioCatalogue API • The requirements document available at: http://www.mygrid.org.uk/dev/wiki/display/scape/Requirements+document+for+the+preservation+components+catalogue • This document will be our PT.WP.4 Month 6 Checkpoint: “Requirements document for the preservation components catalogue” due at Month 6 • Jits to create a BioCatalogue VM that Alex will skin using the SCAPE stylesheets: • Deploy it in the SCAPE infrastructure so people can start adding Web services and play with it • Update it when support for external tool services becomes available
Regular PT Chat • Again, no one from TUB (Berlin) showed up • Ross King was not too thrilled about the idea of using myExperiment “files” for storing tool specifications as the project proposal says “use BioCatalogue” • Need to reassure him we will extend BioCatalogue with support for external tools: • Requirements doc for BioCatalogue repository due at Month 6 • Actual BioCataloguerepository due at Month 24! (needs to be available sooner so people can try it?)
Forthcoming Deliverables • Started up a wiki page with our (Platform-related) deliverables for Year 1 at: http://tinyurl.com/3wnd22b • Requirements documents for Taverna (Month 6): • Available at: http://tinyurl.com/3mtc5on • For Web services developers (DONE) • For external tools developers (IN PROGRESS) • Requirements document for the preservation components catalogue (Month 6): • Available at: http://tinyurl.com/43mv7h2 • Need user partners to agree on the tool specification format • IN PROGRESS
Proposed Development Plan • List of things that we will likely have to develop/provide in the forthcoming period: • BioCatalogue VM (Jits and Alex) • BioCatalogue extension to support storing command line tool services (Alex): • Need user partners to agree on the tool specification format so we can generalize it and startmodelling the BioCatalogue API extension • Continue the Taverna Platform work: • Translate all current Taverna services into SCUFL2 and the new Platform (at the moment only a selection of services is translated – Web services and Beanshells I believe ? • Currently done by David but Alex to join too with translation? • Install our own little Hadoop playground; 1 server should be enough to play with (David and Alex): • Will give us better understanding/idea of how to parallelize Taverna workflows