DS3 Stage01 Plans

Plans and actions for Stage01, due for delivery 30th June 2005

Activities

CVS Repository

Create a CVS repository for VOTech sources, intially using AstroGrid resources. Provide secure Shell (SSH) access to the repository for authorised users. Include repository in scheduled backups. Migrate to VOTech systems when available.

Maven build environment

Create a build environment based upon the AstroGrid environment. Provide usage help and produce outline process if required. Discuss with partners.

Publishing site

Create web site for publishing VOTech software. Initially use AstroGrid hosts, but migrate to VOTech systems when available.

1::Many FileManager::FileStore support

Provide true distributed file storage based upon AstroGrid MySpace V2 component.

CEA proxy for SIAP, SSAP, ConSearch, OpenSkyQuery

Investigate and implement wider access to on-line resources from the AstroGrid CEA Proxy service.

Native JES support for SIAP, SSAP, ConSearch, OpenSkyQuery

Investigate and plan migration of above support directly into AstroGrid JES component

Prototype client-side GUI workflow builder application

In conjunction with the Workflow Use Case activity below, investigate and develop a prototype client-side GUI workflow builder. Include evaluation of exisiting tools (Taverna, Triana etc) as well as integration with AstroGrid Dashboard and JES components

Security report

Based upon current requirements and IVOA agreements (or at least, converging discussions), publish a report providing security implementation guidelines for VOTech developmenst in the short and medium terms.

Client-side User Interface report

Based upon experience of using the AstroGrid-2 Dashboard with various client-side applications, publish a report recommending further research and implementation guidelines.

DSA to provide SIAP, SSAP, ConSearch, OpenSkyQuery interfaces report

Investigate and publish a report recommending the viability and best approach to providing the above interfaces from the AstroGrid DSA component

Develop Use Cases for generic workflow requirements

By examining existing and expected usage models, develop and publish Use Cases defining the role of workflow in the VO environment

Develop profiles (and examine existing) for web services, report

Publish web service profiles for discussion at the IVOA Interop meeting in Kyoto

Vizier-ADQL

ADQL is easy to implement over relational databases but "VizieR" is not a "relational database" Investigate how to implement ADQL in this context (wrapping, etc.)

---

Plan

Environment
Deliverable	Who	Delivery Date	Status
CVS Repository	Catherine Qin	30 June	Awaiting VOTech hardware
Maven build environment	Catherine Qin	30 June	Awaiting h/w and reqs feedback
Publishing site	Catherine Qin	30 June	In progress
Infrastructure
Deliverable	Who	Delivery Date	Status
1::Many FileManager::FileStore support	Noel Winstanley	29-April	Done
CEA proxy for SIAP, SSAP, ConSearch, OpenSkyQuery	Paul Harrison	27 May	Update reqd
Native JES support for SIAP, SSAP, ConSearch, OpenSkyQuery	Paul Harrison	30 June	Update reqd
Prototype client-side GUI workflow builder application	Andre Schaaff (and trainee : Cyril Pestel)	30 June	Done - Available at CDS devcorner
Studies
Deliverable	Who	Delivery Date	Status
Security report	Guy Rixon	30 June	Update reqd
Client-side User Interface report	Noel Winstanley	30 June	Done (pdf attached)
DSA to provide SIAP, SSAP, ConSearch, OpenSkyQuery interfaces; report	Dave Morris	30 June	Update reqd
Develop Use Cases for generic workflow requirements	Andre Schaaff (and CDS working group)	27 May	Done
Develop profiles (and examine existing) for web services, report	Andre Schaaff	12 May	Done - IVOA Document
Investigate requirements for adding support for ADQL queries to Vizier, report	Andre Schaaff	30 September	Done - Madrid Interop

Actions

Who	What	When	Status
All	Discuss, amend and finalise deliverables	9 March	Done
All	Approve Activities and Plan above	14 March	Done
KN	Develop project plan, assign tasks	30 March	Done
All	Status update required	10 June	On-going

Note: The assignments are against the directly responsible individual; other DS3 resources may be required for implementation purposes

-- KeithNoddle - 03 Mar 2005