Difference between revisions of "GOCDB/Release4/Regionalisation/PI Updates"
(Created page with '= Introduction = By introducing an EGI scope into GOCDB there is logically a non-EGI scope available for data. This will be used to store topology information for GOCDB objects t…') |
|||
Line 1: | Line 1: | ||
Back to [[GOCDB/Documentation_Index]] <br/> | |||
Back to [[GOCDB/Release4/Regionalisation]] <br/> | |||
= Introduction = | = Introduction = | ||
By introducing an EGI scope into GOCDB there is logically a non-EGI scope available for data. This will be used to store topology information for GOCDB objects that aren't a part of EGI. However this non-EGI data will be used by other tools and should be exposed. | By introducing an EGI scope into GOCDB there is logically a non-EGI scope available for data. This will be used to store topology information for GOCDB objects that aren't a part of EGI. However this non-EGI data will be used by other tools and should be exposed. |
Revision as of 13:03, 23 June 2011
Back to GOCDB/Documentation_Index
Back to GOCDB/Release4/Regionalisation
Introduction
By introducing an EGI scope into GOCDB there is logically a non-EGI scope available for data. This will be used to store topology information for GOCDB objects that aren't a part of EGI. However this non-EGI data will be used by other tools and should be exposed.
Currently the GOCDB PI exposes only EGI data and by default the GOCDB PI will continue to show only EGI data. In order to access data that isn't in the EGI scope an optional scope parameter will be added. For example:
e.g. https://goc.egi.eu/gocdbpi/public/?method=get_site_list&tag=local
The central instance of GOCDB will provide one scope parameter: local. By default the regional GOCDBs will also expose non-EGI data using the scope=local parameter.