Difference between revisions of "GOCDB Regionalisation Plans"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
= Regionalisation Plans = | = Regionalisation Plans = | ||
== Introduction == | == Introduction == | ||
Our current regionalisation status | Our future plans for regionalisation are described here. To see our cur current regionalisation status please visit [[GOCDB/Release4/Regionalisation | GOCDB4 Regionalisation Status]]. . | ||
== | == Separate EGI and Non-EGI Data == | ||
A GOCDB instance needs to differentiate between EGI and non-EGI data. | A GOCDB instance needs to differentiate between EGI and non-EGI data. A new group named EGI will be created along with tool to insert / remove data to and from a specified group. With this functionality in place NGIs will be able to store and retrieve both local and EGI level sites in the central GOCDB. (This plan is from "Design A" in https://rt.egi.eu/rt/Ticket/Display.html?id=943#txn-52051). | ||
== Regional/Central Synchronisation == | |||
A long term goal for GOCDB is to synchronise regional GOCDB data to the central instance. |
Revision as of 16:13, 4 March 2011
Regionalisation Plans
Introduction
Our future plans for regionalisation are described here. To see our cur current regionalisation status please visit GOCDB4 Regionalisation Status. .
Separate EGI and Non-EGI Data
A GOCDB instance needs to differentiate between EGI and non-EGI data. A new group named EGI will be created along with tool to insert / remove data to and from a specified group. With this functionality in place NGIs will be able to store and retrieve both local and EGI level sites in the central GOCDB. (This plan is from "Design A" in https://rt.egi.eu/rt/Ticket/Display.html?id=943#txn-52051).
Regional/Central Synchronisation
A long term goal for GOCDB is to synchronise regional GOCDB data to the central instance.