<< Back to GOCDB/Documentation_Index
The developments we are currently working on are listed below. They come from the agreed development list, as defined by the Operational Tools Advisory Group (OTAG) who filters and prioritizes user requests.
(related: [GOCDB development items is available in the EGI RT ticket tracker]) Feedback received on the new system is given at: GOCDB/Release4/Feedback
Unifying Central GOCDB
Multiple Endpoints Per Service
Redevelop the xml_output module to implement nested XML collections
- probably using the Query2XML package. This is necessary because the existing XML Output module will only generate flat XML documents (e.g. that often map to individual DB entities). Currently SQL joins/associations between Sites, SEs and URLs cannot be represented as hierarchical/nested XML documents (for example, consider nesting multiple EndpointLocation objects and URLs within a single ServiceEndpoint element, see: Media:GocdbGlue2UnicoreV2.pdf). It is likely that this is a requirement for regionalisation to implement the proposed XML 'synch' docs described at: https://wiki.egi.eu/wiki/GOCDB/Release4/Regionalisation/Data_Transfer_Format
Render GOCDB data in GLUE2 Format
Longer Term Development Roadmap
- [Not confirmed] Support for VOs (maybe query SEs by supported VO)
- [Not confirmed] Regionalisation
- GOCDB4 Regionalisation Status and Plans - More details on regionalisation and progress of Standalone deployments within NGIs.