Feature D0 TTU D-Grids Fermilab OSG LHCb Atlas Alice CMS Sixt DTEAM GEANT4 GEAR OPS UNOSAT
1. Member status values 'suspended' and 'expired' (not only due to an expired certificate). need it need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it
2. Member institutional expiration (a date copied from an external db or added by VO Admin). don't use it need it don't use it don't need it need it need it via CERN HR db need it via CERN HR db (1) no answer but need it via CERN HR db need it via CERN HR db no answer need it need it need it need it need it
3. Group/Group_Role-related items: 3.1 Group membership access (Open/Restricted, i.e. not everyone can subscribe without approval to all Groups). need it need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it
3.2 Group description (a text field that explains what this Group is about). need it need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it
3.3 Group_Role membership access (Open/Restricted, i.e not everyone can subscribe without approval to all VOMS Roles). need it need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it
3.4 Group_Role description (a text field that explains what this VOMS Role is about). need it need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it
3.5 Ability to attach Group_Role to Group (some VOMS Roles don't make sense from within some Groups). Optional need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it
4. Dynamic list of collected personal information (the VO Admin can decide which personal information to collect,from passport number to hair colour. LHC experiment VOs do not use this feature). need it (2) need it need it need it need it don't need it don't need it no answer don't need it no answer don't need it don't need it don't need it don't need it don't need it
5. Event subscription (one can decide which email notifications (s)he wishes to receive when an event occurs, e.g.candidate VO member to approve, request to join a Group or Group_Role etc). need it need it need it need it need it need it (3) need it no answer need it no answer need it need it need it need it need it
6. Interfacing third-party directory during registration and membership validation (e.g. LHC experiment VOs now extract all required personal information of the candidates from the CERN HR db). need it need it don't use it now but need it don't need it don't need it need it via CERN HR db need it via CERN HR db no answer but need it via CERN HR db need it via CERN HR db no answer don't need it don't need it don't need it don't need it don't need it
7. Configurable online help in web UI (one can tailor the web page of his/her VO Registration with info specific to the VO). need it need it need it need it need it would be nice to have would be nice to have no answer would be nice to have no answer need it would be nice to have would be nice to have would be nice to have would be nice to have
8. UI-related items:8.1 Web UI: Sortable output, selectable output information (in VOMRS you can tick the fields you wish displayed when searhing). need it need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it
8.2 Ability to execute actions for multiple users simultaneously (in VOMRS you can, for example, add/remove a long list of users from a Group). need it need it need it need it need it need it need it no answer need it no answer need it need it need it need it need it

(1) All LHC Experiment VOs take this data from the CERN HR db. Atlas and CMS (user Piperov) experience problems when a VO member changes Institute. The Institute Expiration Date reached in VOMRS expires the user in the VO and it is complicated to move the CERN HR administration fast enough to reflect the new affiliation into the VO without disturbing the user's grid work. Also, LHCb reports that some Institute Expiration date may be reached while the user still has a proxy. The only way out of this situation now is either short-lived proxies or user certificate revokation.

(2) This feature should be implemented as a switchable solution, i.e. to be enabled at VO configuration time. Some VOs need it, others don't want to risk any extended private personal data getting into the VO db. Request recorded in https://savannah.cern.ch/bugs/?38159#comment3

(3) See https://savannah.cern.ch/bugs/index.php?38162#comment2 for more VO input on this feature.

-- MariaDimou - 21 Oct 2008

Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2008-10-28 - MariaDimou
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback