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 @ egi.eu.
Difference between revisions of "GOCDB/notifications"
< GOCDB
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
=== UTF-8 Character Support === | === UTF-8 Character Support === | ||
Allow UTF-8 characters for selected fields with rendering in the output of the relevant PI methods. This will allow chars such as àšëÂÒÚÿaúø (this is only a small selection). | Allow UTF-8 characters for selected fields with rendering in the output of the relevant PI methods. This will allow chars such as àšëÂÒÚÿaúø (this is only a small selection). Initially allow for selected fields (can extend support to other fields later if required): | ||
* Human readable Description fields on: Project, NGI, Site, Service, Service Group, Downtime, ServiceType. | * Human readable Description fields on: Project, NGI, Site, Service, Service Group, Downtime, ServiceType. | ||
* Extension Property values (Sites, Services, ServiceEndpoints, ServiceGroups). | * Extension Property values (Sites, Services, ServiceEndpoints, ServiceGroups). | ||
Revision as of 15:26, 11 February 2015
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
| Tools menu: | • Main page | • Instructions for developers | • AAI Proxy | • Accounting Portal | • Accounting Repository | • AppDB | • ARGO | • GGUS | • GOCDB |
| • Message brokers | • Licenses | • OTAGs | • Operations Portal | • Perun | • EGI Collaboration tools | • LToS | • EGI Workload Manager |
Proposed Changes
Please contact gocdb-admins if the changes listed below will have repercussions:
UTF-8 Character Support
Allow UTF-8 characters for selected fields with rendering in the output of the relevant PI methods. This will allow chars such as àšëÂÒÚÿaúø (this is only a small selection). Initially allow for selected fields (can extend support to other fields later if required):
- Human readable Description fields on: Project, NGI, Site, Service, Service Group, Downtime, ServiceType.
- Extension Property values (Sites, Services, ServiceEndpoints, ServiceGroups).
get_user PI method updates
- New elements to be added: <SSOUSERNAME> and <PRIMARY_KEY> (PK of role's target entity)
- Update values of <ENTITY_TYPE> element so that:
- 'group' value is separated into 'ngi' and 'project'
- All values then become: project, ngi, site, servicegroup
Sample changes highlighted below:
