Difference between revisions of "Long-tail of science pilot User story"

From EGIWiki
Jump to: navigation, search
(-)
Line 1: Line 1:
= User Story for 1st phase LToS  =
+
== User Story for 1st phase LToS  ==
  
=== Step 1: User Login/Register into Portal<br> ===
+
=== User Step 1: User Login/Register into Portal  ===
  
 
1. The entry page of Portal:  
 
1. The entry page of Portal:  
  
*Basic info about EGI offer  
+
* Basic info about EGI offer  
*Info about similar national options for access  
+
* Info about similar national options for access  
*Encouragement to register  
+
* Encouragement to register  
*Login and Register option easy visible
+
* Login and Register option easy visible
  
2. Login option include local account and authentication through EduGain, X509, ...
+
2. Login option include:
 +
* EGI SSO
 +
* EduGain,  
 +
* X509 certificate
 +
* open accounts (google, facebook)
  
 
3. Registration requirements:<br>  
 
3. Registration requirements:<br>  
  
*Required fields: Full name, country, validated email address  
+
* Required fields: Full name, country, validated email address  
*Optional fields: ResearchGate profile, LinkedIn profile, ...  
+
* Optional fields: ResearchGate profile, LinkedIn profile, ...  
*Acceptance of general Usage Policy  
+
* Acceptance of General Usage Policy (is this the same as LTOS VO AUP?)
*At this stage account is created instantly (without any verification)
+
* At this stage account is created instantly (without any verification)
  
4. Result: Simple account in the portal is created  
+
4. Result: Account in the portal is created  
  
*Option available for verified user are visible but nonactive
+
Note: Options available for verified user are visible but might be nonactive, however completing the scenario including sending request for resources is  possible without waiting for verification.
  
4. Additions:  
+
=== User Step 2: User adds his/her affiliation  ===
  
*User should confirm the APU of LTOS VO
+
Valid and verified affiliation is needed for having acces to resources.  
*User should describe in request what he/she will be doing
 
 
 
=== Step 2: User adds his/her affiliation ===
 
 
 
1. Information needed:
 
  
*Country/NGI
+
1. Adding affiliation, forms:
*Related site (optional)
 
*Institution (including department)
 
*Address
 
*Web-page of the institution (with list of Staff)
 
  
2. Verified affilaition of the user is required to obtain access to resources
+
* Country/NGI
 +
* (option) Related site (????)
 +
* (option) for non-staff, supervisor name and e-mail
 +
* Institution (including department)
 +
* Address (????)
 +
* Web-page of the institution (with list of Staff)
  
*More than one affilaition might be possible
+
after sending the form affiliation is visible, but not active
  
3. For non-Staff supervisor name, e-mail shoul be added
+
* More than one affiliation might be possible.
 +
* Staff is notified about the request.
  
=== Step 2.1: Affilaition is verified  ===
+
=== Operator Step 2.1: Affiliation is verified  ===
  
1. Operationa Staff is veryfing affilaition added:  
+
1. Operation Staff is confirming affiliation added:  
  
 
*In case of problems/additional information - communication via user e-mail
 
*In case of problems/additional information - communication via user e-mail
 
+
s
 
2. E-mail notification to user about decision taken  
 
2. E-mail notification to user about decision taken  
  
 
3. Included the date for how long the affiliation is valid
 
3. Included the date for how long the affiliation is valid
  
=== Step 3: User requests initial resources/services  ===
+
=== Operator Step 3: User requests initial resources/services  ===
  
 
1. User has a link to SGs  
 
1. User has a link to SGs  
Line 65: Line 66:
 
*In request: describe what he/she is doing  
 
*In request: describe what he/she is doing  
 
*Allow for more than one request
 
*Allow for more than one request
 +
 +
 +
*User should describe in request what he/she will be doing
 +
 +
2. Verified affilaition of the user is required to obtain access to resources
 +
 +
== Extensions for 2nd prototype ==
  
 
=== Step 4: User is using services  ===
 
=== Step 4: User is using services  ===

Revision as of 18:12, 28 January 2015

User Story for 1st phase LToS

User Step 1: User Login/Register into Portal

1. The entry page of Portal:

  • Basic info about EGI offer
  • Info about similar national options for access
  • Encouragement to register
  • Login and Register option easy visible

2. Login option include:

  • EGI SSO
  • EduGain,
  • X509 certificate
  • open accounts (google, facebook)

3. Registration requirements:

  • Required fields: Full name, country, validated email address
  • Optional fields: ResearchGate profile, LinkedIn profile, ...
  • Acceptance of General Usage Policy (is this the same as LTOS VO AUP?)
  • At this stage account is created instantly (without any verification)

4. Result: Account in the portal is created

Note: Options available for verified user are visible but might be nonactive, however completing the scenario including sending request for resources is possible without waiting for verification.

User Step 2: User adds his/her affiliation

Valid and verified affiliation is needed for having acces to resources.

1. Adding affiliation, forms:

  • Country/NGI
  • (option) Related site (????)
  • (option) for non-staff, supervisor name and e-mail
  • Institution (including department)
  • Address (????)
  • Web-page of the institution (with list of Staff)

after sending the form affiliation is visible, but not active

  • More than one affiliation might be possible.
  • Staff is notified about the request.

Operator Step 2.1: Affiliation is verified

1. Operation Staff is confirming affiliation added:

  • In case of problems/additional information - communication via user e-mail

s 2. E-mail notification to user about decision taken

3. Included the date for how long the affiliation is valid

Operator Step 3: User requests initial resources/services

1. User has a link to SGs

2. User sees allocation with default (seed reasources):

  • Max
  • Single form: register in eGRANT
  • Special, central pool for EGI-seed resource
  • In request: describe what he/she is doing
  • Allow for more than one request


  • User should describe in request what he/she will be doing

2. Verified affilaition of the user is required to obtain access to resources

Extensions for 2nd prototype

Step 4: User is using services

1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal

2. Access is blocked when initial allocation is over

  • Notification and encouragement to full resources request

Step 5: User uses feedback form

1. Interface encourage to write to EGI and express his/her needs

Step 6: User report results supported by EGI

1. User uses form to report result supported by EGI (it is his/her obligation):

  • Scientific paper
  • Project that is using EGI
  • ...

Additions:

  • The User Registration Portal needs to generate DNs for new users, and be ready to communicate the list of user DNs to VOMS