Ceo: Difference between revisions

From CSCWiki
Jump to navigation Jump to search
(New page: CEO is the CSC member creation and administration interface. CEO was originally written in perl by persons of mysterious-ness. CEO was re-written in python by Michael Spang in early 2007.)
 
(Add feature requests)
Line 1: Line 1:
CEO is the CSC member creation and administration interface. CEO was originally written in perl by persons of mysterious-ness. CEO was re-written in python by Michael Spang in early 2007.
CEO is the CSC member creation and administration interface. CEO was originally written in perl by persons of mysterious-ness. CEO was re-written in python by Michael Spang in early 2007.

= Feature Requests and Ideas =

* 'New member' should prompt for userid and then use uwldap to pre-fill name and program
* Merge 'New member' and 'Create an account'
* Remove 'Library functions', as they are now in koha
* Remove student ids from CEO and LDAP
** We do not provide student ids to MathSoc when we present memberlists
** It is against policy to store both student ids and names
* Remove 'Search for a member by student id'
* Add ability to set the executive
** The positions should be stored in LDAP
** CEO should prompt for each position (pre-filling with the current position holder)
** CEO should then update ldap and regenerate aliases
*** We would have an /etc/aliases.exec or something
** The exec xml would be auto-generated from LDAP

Revision as of 21:40, 14 September 2007

CEO is the CSC member creation and administration interface. CEO was originally written in perl by persons of mysterious-ness. CEO was re-written in python by Michael Spang in early 2007.

Feature Requests and Ideas

  • 'New member' should prompt for userid and then use uwldap to pre-fill name and program
  • Merge 'New member' and 'Create an account'
  • Remove 'Library functions', as they are now in koha
  • Remove student ids from CEO and LDAP
    • We do not provide student ids to MathSoc when we present memberlists
    • It is against policy to store both student ids and names
  • Remove 'Search for a member by student id'
  • Add ability to set the executive
    • The positions should be stored in LDAP
    • CEO should prompt for each position (pre-filling with the current position holder)
    • CEO should then update ldap and regenerate aliases
      • We would have an /etc/aliases.exec or something
    • The exec xml would be auto-generated from LDAP