Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

GOCDB/Data Scoping

From EGIWiki
Revision as of 10:58, 23 June 2011 by Jcasson (talk | contribs) (→‎PI)
Jump to navigation Jump to search


To mark data within GOCDB as EGI data a new tagging system will be implemented. Such a tagging system will allow other types of tags to be defined in future. These other tags can be used by NGIs wishing to customise their GOCDB instance.

Underlying Implementation

A new PROM class called Tag will be introduced that can be linked to sites, service endpoints, downtimes, users and user roles. We will create an instance of this tag class called EGI. If a site, SE, downtime, user or user role has a PROM link to the EGI tag then the object will be exposed to the EGI infrastructure through the PI. If such an object isn’t tagged it won’t be exposed to the production infrastructure.

Scoping Rules

An EGI child must have an EGI parent (e.g. an EGI SE must have a parent EGI site, an EGI role must have a parent EGI user etc).

User Interface


  • Add a tick box to each affected data type (sites, service endpoints, downtimes, users and user roles) on the add and edit forms.
  • The question mark button will lead to a page explaining that marking data as EGI will send that data to the central GOCDB portal
  • The user interface should enforce the scoping rules set out above (EGI child must have EGI parent)
  • The UI should also automatically de/select the EGI tick box for new objects depending on whether their parents are EGI objects.
    • For example, when adding a new service endpoint to an EGI site the EGI box in the Add New Service Endpoint form should be ticked by default.
    • Similarly if a downtime is to be added to a set of non-EGI service endpoints the EGI box shouldn’t be ticked by default.
  • Change Browse Sites in the left hand menu to Browse EGI sites
  • Add a new link to Browse Local Sites. This will also need a help button by it explaining the difference.
  • Viewing a list of sites, SEs, downtimes and search results can be filtered by EGI / non-EGI.
  • When viewing an object (site, SE, downtime, user, role) it should be clear that the object is local-only.
  • Site/SE etc. page titles will change to Local Site / Local SE etc
  • Consider changing the colour of the headings on the page.
    • This could be accompanied with a "Why is this page blue?" link.
  • For each table add a EGI or Local column with a colourful icon
  • Search results will include a separate section for local objects.