Difference between revisions of "Long-tail of science pilot User story"
Jump to navigation
Jump to search
Step 1: User Login/register into Portal
Line 44: | Line 44: | ||
3. For non-Staff supervisor name, e-mail shoul be added | 3. For non-Staff supervisor name, e-mail shoul be added | ||
=== Step 2.1: Affilaition is verified === | === Step 2.1: Affilaition is verified === | ||
1. Operationa Staff is veryfing affilaition added: | 1. Operationa Staff is veryfing affilaition added: | ||
*In case problems/need additional information - communication via user e-mail | *In case problems/need additional information - communication via user e-mail | ||
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 === | |||
1. Users have a link to SGs | |||
2. Users see allocation with default (seed reasources): | |||
*Max | |||
*Single form: register in eGRANT | |||
*Special, central pool for EGI-seed resource | |||
*In request: describe what he is doing | |||
*Allow for more than one request |
Revision as of 08:38, 27 January 2015
User Story for 1st phase LToS
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 local account and authentication thought EduGain, X509, ...
3. Registration requirement:
- Required fields: Full name, country, validated email address
- Optional fields: ResearchGate profile, LinkedIn profile, ...
- Acceptance of general Usage Policy
- At this stage account is created instantly (without any verification)
4. Result: Simple account in the portal is created
- Option avaialbe for verified user are visible but nonactive
4. Additions:
- User should confirm the APU of LTOS VO
- User should describe in request what he/she will be doing
Step 2: User adds his/her affiliation
1. Information needed:
- Country/NGI
- 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
- More than one affilaition might be possible
3. For non-Staff supervisor name, e-mail shoul be added
Step 2.1: Affilaition is verified
1. Operationa Staff is veryfing affilaition added:
- In case problems/need additional information - communication via user e-mail
2. E-mail notification to user about decision taken
3. Included the date for how long the affiliation is valid
Step 3: User requests initial resources/services
1. Users have a link to SGs
2. Users see allocation with default (seed reasources):
- Max
- Single form: register in eGRANT
- Special, central pool for EGI-seed resource
- In request: describe what he is doing
- Allow for more than one request