UC AWOB UM 01 SPEC Register User

MPDL,GAVO

= R0.8 =

Schedule & Summary

 * R0.8
 * Update from Demonstrator http://colab.mpdl.mpg.de/mediawiki/UC_AWOB_UM_01_SPEC_Register_User#AWOB_UM_01_Register_User
 * Able to enter user’s main affiliation at registration, and it appears on user profile as well as member list of project/WG/consortium

'''[TODO] Decide whether to implement supporting affiliation using enumeration or LR organization. '''

Actor
Anonymous user

Step
An actor is able to enter user’s main affiliation.


 * 1) User can select his/her institute from astronomy institute list.
 * 2) List of Astronomy institutes: ESO List in http://colab.mpdl.mpg.de/mediawiki/AWOB_Task_026
 * 3) If actor’s institute is not available in the list,
 * 4) Actor can choose ‘other’ on the list
 * 5) Actor can also contact AWOB to request to add a missing institute to the list if actor wishes.
 * 6) If actor doesn’t have an affiliation, actor doesn’t choose any institute

Post conditions

 * 1) The affiliation appears on user’s My Account.
 * 2) From ‘My Account’ the actor is able to change it.
 * 3) If the affiliation is changed, update accordingly everywhere where the actor is listed

Schedule & Summary

 * R0.8
 * New Use Case

Actor
Registered user

Step
1. An actor changes user profile from ‘My Account’.

Post conditions

 * 1) Update accordingly everywhere where the actor is listed.
 * 2) Eg., affiliation.

= DEMONSTRATOR =

Overview
An individual wants to register to AWOB. It means that an individual wants to create an account in an awob system. It doesn't mean that it requests to become a member of a project.

Links

 * Conceptual Model AWOB_Concepts_Project
 * GUI [|Register User]

Status/Schedule

 * Status: Specification
 * Schedule:Demonstrator

Triggers

 * A person wants to create a user account within an AWOB instance.

Actors
Anonymous User

Pre-Conditions

 * None

Flow of Events

 * 1. The Anonymous User chooses to register as a user of AWOB
 * 2. The system displays a registration form, requesting some basic information (First name, Last name, email address) and CAPTCHA.
 * 3. The Anonymous User enters necessary information and confirms his/her input
 * 4 The system checks if all fields are provided.
 * 4.1. if all fields are provided, continue with step 5.
 * 4.2. otherwise the System displays error messages on the registration page. Continue with step 2
 * 5. The system checks if any of the e-mail account are already registered in AWOB
 * 5.1. A Registered user with the same e-mail(or username) does not exist in the system (continue with step 6)
 * 5.2. Otherwise the system displays error message on the registration page. Continue with step 2
 * 6. The system creates a temporary user account (with an expiry timestamp) and sends a confirmation request per e-mail (with a predefined subject, text and link for the confirmation request) to the provided e-mail address.
 * 6.1. The system displays a success message informing the Anonymous User to check his/her email. The use case ends successfully.

Alternatives

 * 5.2.1. Otherwise the system displays error message on the registration page. The Anonymous User cancels the registration.The use case ends unsuccessfully.
 * 6. The system creates a user account and sends a confirmation request, including the password per e-mail (see discussion, at present this is supported, no confirmation e-mail is supported)

Post-Conditions / Results

 * A temporary user account (with an expiry timestamp) is created. A confirmation request per e-mail (with a predefined subject, text and link for the confirmation request) to the provided e-mail address

Discussion
We should agree on this point. I myself prefer to type in my own password in the form. However, if it's security reason I'm open to Rupert's suggestion.--Jkim 19:25, 27 June 2011 (CEST)
 * 1. Note: Liferay supports partly the use case at present, but does not by default allows the user to state his/her organization and the e-mail confirmation link during user registration. As far as one can see based on their development tracks, they shall delivering the functionality of the e-mail confirmation link during registration with the next release.
 * 2. Question about password. While working on mock up Rupert thought that for security reason a user password should be sent to an individual by email instead of that one enters one's own password on the registration form.
 * The system can be set-up in such a manner that a password re-set is required. As there are couple of policies that can be defined for password management, i would follow up the suggestion to send per email. Once the user loggs-in, she may be able to update own password (or would be explicitely enforced by the system to do so).--Natasa 11:23, 7 July 2011 (CEST)

AWOB UM 02 Confirm user registration
An individual wants to confirm his/her registration request for an account in AWOB.

Status/Schedule

 * Status: Specification
 * Schedule:Demonstrator

Triggers

 * A person received an e-mail from an AWOB instance, containing a confirmation link for finalization of the registration of an AWOB account.

Actor

 * Individual

Precondition

 * The Individual has an email account
 * The Individual has received an e-mail with an activation link to become a Registered User in AWOB

Flow

 * 1. An Individual chooses to follow up the activation link she received per e-mail
 * 2. The system validates the activation link
 * 2.1. if the activation link is valid, the system creates a Registered User and displays a success message containing further instructions. The use case ends successfully.
 * 2.2. if the activation link is not valid, the system displays an error message and asks the Individual to register again. The use case ends unsuccessfully.

Post-Conditions/Results

 * A new Registered User is created in AWOB.