AstroGrid

AstroGrid increases scientific research possibilities by :

• enabling access to distributed astronomical data and information resources.

• providing a standardized framework for astronomical data processing.

• including publishing, co-operative analysis and visualization of data.

Myspace

DataAccess CEA

Community

Workflow

Portal

Registry

Access to the Data

Tool to sequence applications

working on a data set

•Auxiliary applications for portability of heterogeneous data.

Integrated applications for data manipulation

The virtual data repository

•Data discovery and resource directory,

AstroGrid framework:

AstroGrid Registry

• The registry is a set of web service interface methods conforming to the IVOA standard for Query and Harvesting interfaces,

• Astrogrid registry versions supports 0.9 and 0.10. • registry uses eXist database for the xml and

indexes the xml for querying using Xquery • Now replaced with eXist with exception handling

using the apache-commons-http

Features• The registry supports search in ADQL.• The version of Resources for querying is identified by

the VR namespace (or defaults if not present).• The registry server provides a variety of properties that

normally do not require changing the registry. But the flexibility allows to support other versions of IVOA schemas.

• Updates access the VR namespace and store it in the appropriate collection (table).

• Registry web service infrastructure uses Axis message-style back-end.

Features contd.

• Axis simply gives the XML DOM doc to the service to figure out what to do. Binding or generation of java objects anywhere is avoided.

• The wsdl written with the registry even though is a Axis message style back-end the wsdl is actually a Document-literal written in a wrapped style.

• Validates the XML incoming, but depending on how the properties are set, it will try to store the XML.

• Using a XML database allows storing any extensions to the Registry Resource schemas (CEA XML).

Current Astrogird registries

• Astrogrid

– Cambridge - publishing registry

– Cambridge - full registry 0.9 only at the moment

– Hydra - full registry 0.9 and 0.10 data.

• Others

– STSCI – full registry recently 0.10

– Caltech – full registry 0.10

– NCSA – Publishing registry 0.10

– Heasac – Publishing registry 0.10

– Vizier – Publishing registry 0.9 and 0.10

– JVO and CanadaVO may be coming soon.

Problematic Areas

• Invalid data and namespaces became a big problem for the portal.

• eXist database as its own server seems to better. A few inconsistant problems show up with the webapp version under tomcat with large amounts of data.

Next Step

1) Security

2) Curration

3) Re-factoring

4) Explore other interfaces into eXist; ex: Soap service vs REST style

5) Query processing: return sub-elements to Resource query

6.) Xforms – Maybe another look at this at a later date.