OpenWetWare:Feature list/User management system: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=Brief description=
==Brief description==
The [[OpenWetWare:Software/User_management|UMS]] that we use to process new users doesn't interface well with the mediawiki DB backend.
The [[OpenWetWare:Software/User_management|UMS]] that we use to process new users doesn't interface well with the mediawiki DB backend.


=Detailed description=
==Detailed description==
*[[OpenWetWare:Software/User_management#New_Feature_Requests|New feature requests]]
*[[OpenWetWare:Software/User_management#New_Feature_Requests|New feature requests]]
*The user count given by <code><nowiki>{{NUMBEROFUSERS}}</nowiki></code> is not up to date.
*The user count given by <code><nowiki>{{NUMBEROFUSERS}}</nowiki></code> is not up to date.
*Track who approved which account (optional)
*Track who approved which account (optional)
*Allow discussion/wiki page for each request (optional)
*Centralized archival of all request approvals and denials along with discussion
*Centralized archival of all request approvals and denials along with discussion
*Advanced user account management (delete user while reassigning edits (merge accounts), etc - see [[User:Ilya/OpenWetWare/UMS|Ilya's UMS page]] for other useful queries)
*Advanced user account management (delete user while reassigning edits (merge accounts), etc - see [[User:Ilya/OpenWetWare/UMS|Ilya's UMS page]] for other useful queries)
*Dynamic check of whether the username is already taken, also whether the email provided has been registered (which indicates a duplicate account)
*An easy way for admins to check if a first/last name has already been registered
*Users must confirm a valid email BEFORE admins see the request, otherwise we have many people who are approved but their approval emails bounce.
*Allow editing/reformatting of a person's name within the user management queue.  (In capitalization is wrong or something.)
*check boxes for signing up for 'oww-discuss' mailing list.
==Tasks==
#Change the user management system backend to use MediaWiki hooks rather than direct access of the database.
#Change workflow so that upon account request, the applicant receives an email in which they confirm their account request (to confirm a valid email address), and then they show up in the queue.
#Log


=Team=
==Team==

Latest revision as of 11:05, 6 September 2007

Brief description

The UMS that we use to process new users doesn't interface well with the mediawiki DB backend.

Detailed description

  • New feature requests
  • The user count given by {{NUMBEROFUSERS}} is not up to date.
  • Track who approved which account (optional)
  • Centralized archival of all request approvals and denials along with discussion
  • Advanced user account management (delete user while reassigning edits (merge accounts), etc - see Ilya's UMS page for other useful queries)
  • Dynamic check of whether the username is already taken, also whether the email provided has been registered (which indicates a duplicate account)
  • An easy way for admins to check if a first/last name has already been registered
  • Users must confirm a valid email BEFORE admins see the request, otherwise we have many people who are approved but their approval emails bounce.
  • Allow editing/reformatting of a person's name within the user management queue. (In capitalization is wrong or something.)
  • check boxes for signing up for 'oww-discuss' mailing list.

Tasks

  1. Change the user management system backend to use MediaWiki hooks rather than direct access of the database.
  2. Change workflow so that upon account request, the applicant receives an email in which they confirm their account request (to confirm a valid email address), and then they show up in the queue.
  3. Log

Team