https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Agpul&feedformat=atomEGIWiki - User contributions [en]2024-03-29T06:55:40ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=GGUS:EOSC_Portal_FAQ&diff=102734GGUS:EOSC Portal FAQ2019-10-29T07:50:30Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= EOSC Portal<br />
|Interface= H<br />
|purpose= To ensure that the Web application - EOSC Portal - is operational.<br />
|responsible= Cyfronet Marketplace team<br />
|service quality= According to: https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels<br />
|solved by= Solved if the scope applies.<br />
|components= https://eosc-portal.eu/<br />
|assigned by= TPM or portal operations support<br />
|documentation= tbd<br />
|sortname=eosc portal<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:EOSC_Portal_FAQ&diff=102733GGUS:EOSC Portal FAQ2019-10-29T07:09:30Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= EOSC Portal<br />
|Interface= H<br />
|purpose= To ensure that the Web application - EOSC Portal - is operational.<br />
|responsible= Cyfronet Marketplace team<br />
|service quality= According to: https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels<br />
|solved by= Solved if the scope applies.<br />
|components= https://eosc-portal.eu/<br />
|assigned by= TPM or portal operations support<br />
|documentation= <br />
|sortname=eosc portal<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:FAQ_Responsible_Units&diff=102731GGUS:FAQ Responsible Units2019-10-28T12:08:33Z<p>Agpul: </p>
<hr />
<div>{{GGUS-header|FAQ Responsible Units}} <br />
<br />
*List of FAQs see [[:Category:FAQ Responsible Units (GGUS)]]<br />
<br />
== Migration ==<br />
<br />
*The FAQ about responsible units started as FAQ about support units long ago. In March 2011 a new FAQ was started inside the EGI wiki. <br />
*The FAQs shall help the TPM to assign tickets and other responsible units to reassign tickets. <br />
*The FAQ is searchable and public. <br />
*The FAQ will not contain e-mail adresses or internal informations.<br />
<br />
The fields are <br />
<br />
;|Unit=&nbsp;<br />
:Responsible Unit&nbsp;<br />
:This is the name take from the GGUS system, please do not change. <br />
;|E-Mail=<br />
:unused <br />
;|Interface=<br />
:unused <br />
;|purpose=<br />
:What is the purpose of the UNIT? <br />
;|components=<br />
:For which components do you provide support? <br />
;|service quality=<br />
:Which quality of service ([[FAQ GGUS-QoS-Levels|QoS]]) will you provide? <br />
;|assigned by=<br />
:Who will assign tickets to UNIT? This could be TPM or DMSU or ... <br />
;|solved by=<br />
:Are tickets typically solved in UNIT or reassigned elsewhere? <br />
;|responsible=<br />
:Who is responsible for UNIT? This could be a person or an organisation. <br />
;|documentation=&nbsp;<br />
:What documentation is available on UNIT? <br />
;|more=&nbsp;<br />
:What if I have questions which are not dealt with by this FAQ? <br />
:this is optional <br />
;|sortname=&nbsp;<br />
:Name of the UNIT, with first letter upper case and everything else lower case <br />
:this helps sorting the FAQ, please do not change.<br />
<br />
== How to change ==<br />
<br />
*Be a member of the EGI group [[EGIWiki:Ggus-authors|ggus-authors]] <br />
*Replace the content after "="-sign in the appropriate wiki page. <br />
*You can add missing fields, see above (or [[Template:GGUS-FAQ]])<br />
<br />
;Old list <br />
:until March 2011: [https://gus.fzk.de/pages/resp_unit_info.php FAQs about the support units connected to GGUS].<br />
<br />
{{GGUS search}} <br />
<br />
*See also [[GGUS:FAQ]]<br />
<br />
[[Category:FAQ_Responsible_Units_(GGUS)|!FAQ]]</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:FAQ_Responsible_Units&diff=102730GGUS:FAQ Responsible Units2019-10-28T12:08:12Z<p>Agpul: </p>
<hr />
<div>{{GGUS-header|FAQ Responsible Units}}<br />
* List of FAQs see [[:Category:FAQ Responsible Units (GGUS)]]<br />
== Migration ==<br />
* The FAQ about responsible units started as FAQ about support units long ago. In March 2011 a new FAQ was started inside the EGI wiki.<br />
* The FAQs shall help the TPM to assign tickets and other responsible units to reassign tickets. <br />
* The FAQ is searchable and public.<br />
* The FAQ will not contain e-mail adresses or internal informations.<br />
<br />
The fields are<br />
;|Unit= : Responsible Unit 2<br />
: This is the name take from the GGUS system, please do not change.<br />
;|E-Mail=: unused<br />
;|Interface=: unused<br />
;|purpose=: What is the purpose of the UNIT?<br />
;|components=: For which components do you provide support?<br />
;|service quality=: Which quality of service ([[FAQ_GGUS-QoS-Levels | QoS]]) will you provide?<br />
;|assigned by=: Who will assign tickets to UNIT? This could be TPM or DMSU or ...<br />
;|solved by=: Are tickets typically solved in UNIT or reassigned elsewhere?<br />
;|responsible=: Who is responsible for UNIT? This could be a person or an organisation.<br />
;|documentation= :What documentation is available on UNIT? <br />
;|more= : What if I have questions which are not dealt with by this FAQ?<br />
: this is optional<br />
;|sortname= :Name of the UNIT, with first letter upper case and everything else lower case<br />
: this helps sorting the FAQ, please do not change.<br />
<br />
== How to change ==<br />
* Be a member of the EGI group [[EGIWiki:ggus-authors|ggus-authors]] <br />
* Replace the content after "="-sign in the appropriate wiki page.<br />
* You can add missing fields, see above (or [[Template:GGUS-FAQ]])<br />
; Old list<br />
: until March 2011: [https://gus.fzk.de/pages/resp_unit_info.php FAQs about the support units connected to GGUS].<br />
<br />
{{GGUS search}}<br />
* See also [[GGUS:FAQ]]<br />
<br />
[[Category:FAQ Responsible Units (GGUS)|!FAQ]]</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:Marketplace_FAQ&diff=100468GGUS:Marketplace FAQ2018-11-07T06:34:48Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= EGI Marketplace<br />
|Interface= H<br />
|purpose= To ensure that the Web applications – EGI Marketplace and EOSC Marketplace – are operational<br />
|responsible= Cyfronet Marketplace team<br />
|service quality= According to: https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels<br />
|solved by= Solved if the scope applies.<br />
|components= https://marketplace.egi.eu/<br />
https://marketplace.eosc-portal.eu<br />
<br />
|assigned by= TPM or marketplace operations support <br />
|documentation= Technical:<br />
https://github.com/cyfronet-fid/marketplace<br />
<br />
|sortname=egi marketplace<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:Marketplace_FAQ&diff=100467GGUS:Marketplace FAQ2018-11-07T06:33:43Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= EGI Marketplace<br />
|Interface= H<br />
|purpose= To ensure that the Web applications – EGI Marketplace and EOSC Marketplace – are operational<br />
|responsible= Cyfronet Marketplace team<br />
|service quality= Accoring to: https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels<br />
|solved by= Solved if the scope applies.<br />
|components= https://marketplace.egi.eu/<br />
https://marketplace.eosc-portal.eu<br />
<br />
|assigned by= TPM or marketplace operations support <br />
|documentation= Technical:<br />
https://github.com/cyfronet-fid/marketplace<br />
<br />
|sortname=egi marketplace<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:LTOS_FAQ&diff=89756GGUS:LTOS FAQ2016-09-20T10:29:44Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= LTOS<br />
|purpose= The purpose of the LTOS SU is handle ticket assigned to it.<br />
<br />
|components= The LTOS SU provides support for the User Registration Portal. <br />
<br />
|service quality= According to https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels we will provide medium QoS.<br />
<br />
|assigned by= A ticket is usually assigned to the LTOS Support Unit by EGI 2nd level user support or directly by informed users or site admins.<br />
<br />
|solved by= Yes. Tickets are typically solved in this unit. <br />
<br />
|responsible= The LTOS development team. <br />
<br />
|documentation= https://wiki.egi.eu/wiki/Long-tail_of_science<br />
<br />
|sortname= LTOS<br />
<br />
|type of issue= Other<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:LTOS_FAQ&diff=89704GGUS:LTOS FAQ2016-09-19T09:21:47Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= LTOS<br />
|purpose= The purpose of the LTOS SU is handle ticket assigned to it.<br />
<br />
|components= We support User Registration Portal. <br />
<br />
|service quality= According to https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels we will provide base QoS.<br />
<br />
|assigned by= No special permission.<br />
<br />
|solved by= Yes. <br />
<br />
|responsible= The person responsible for LTOS support is Roksana Różańska. <br />
<br />
|documentation= https://wiki.egi.eu/wiki/Long-tail_of_science<br />
<br />
|sortname= LTOS<br />
<br />
|type of issue=<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:LTOS_FAQ&diff=89695GGUS:LTOS FAQ2016-09-19T09:08:37Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= LTOS<br />
|purpose= The purpose of the LTOS SU is handle ticket assigned to it.<br />
<br />
|components= We support User Registration Portal. <br />
<br />
|service quality= According to https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels we will provide base QoS.<br />
<br />
|assigned by= No special permission.<br />
<br />
|solved by= Yes. Tickets are typically solved in LTOS Support.<br />
<br />
|responsible= The person responsible for LTOS support is Roksana Różańska. <br />
<br />
|documentation= https://wiki.egi.eu/wiki/Long-tail_of_science<br />
<br />
|sortname= LTOS<br />
<br />
|type of issue=<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:LTOS_FAQ&diff=89693GGUS:LTOS FAQ2016-09-19T09:07:48Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= LTOS<br />
|purpose= The purpose of the LTOS SU is handle ticket assigned to it.<br />
<br />
|components= We support User Registration Portal. <br />
<br />
|service quality= According to https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels we will provide base QoS.<br />
<br />
|assigned by=<br />
<br />
|solved by= Yes. Ticket are typically solved in LTOS Development Support.<br />
<br />
|responsible= The person responsible for LTOS support is Roksana Różańska. <br />
<br />
|documentation= https://wiki.egi.eu/wiki/Long-tail_of_science<br />
<br />
|sortname= LTOS<br />
<br />
|type of issue=<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:LTOS_FAQ&diff=89557GGUS:LTOS FAQ2016-09-15T07:15:39Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= LTOS<br />
|purpose= The purpose of the LTOS SU is handle ticket assigned to it.<br />
<br />
|components=<br />
<br />
|service quality= According to https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels we will provide base QoS.<br />
<br />
|assigned by=<br />
<br />
|solved by=<br />
<br />
|responsible=<br />
<br />
|documentation= <br />
<br />
|sortname= LTOS<br />
<br />
|type of issue=<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=GGUS:LTOS_FAQ&diff=89556GGUS:LTOS FAQ2016-09-15T07:15:19Z<p>Agpul: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= LTOS<br />
|purpose= The purpose od the LTOS SU is handle ticket assigned to it.<br />
<br />
|components=<br />
<br />
|service quality= According to https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels we will provide base QoS.<br />
<br />
|assigned by=<br />
<br />
|solved by=<br />
<br />
|responsible=<br />
<br />
|documentation= <br />
<br />
|sortname= LTOS<br />
<br />
|type of issue=<br />
}}</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76634Long-tail of science pilot User story2015-01-27T12:57:49Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/Register into Portal<br> ===<br />
<br />
1. The entry page of Portal: <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication through EduGain, X509, ... <br />
<br />
3. Registration requirements:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option available for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case of problems/additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid<br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he/she is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal <br />
<br />
2. Access is blocked when initial allocation is over <br />
<br />
*Notification and encouragement to full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs <br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation): <br />
<br />
*Scientific paper <br />
*Project that is using EGI <br />
*...<br />
<br />
=== Additions: ===<br />
<br />
*The User Registration Portal needs to generate DNs for new users, and be ready to communicate the list of user DNs to VOMS<br></div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76633Long-tail of science pilot User story2015-01-27T12:56:06Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/Register into Portal<br> ===<br />
<br />
1. The entry page of Portal: <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication through EduGain, X509, ... <br />
<br />
3. Registration requirements:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option available for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case of problems/additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid<br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he/she is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal <br />
<br />
2. Access in blocked when initial allocation is over <br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs <br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation): <br />
<br />
*Scientific paper <br />
*Project that is using EGI <br />
*...<br />
<br />
=== Additions: ===<br />
<br />
*The User Registration Portal needs to generate DNs for new users, and be ready to communicate the list of user DNs to VOMS<br></div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76632Long-tail of science pilot User story2015-01-27T12:55:33Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/Register into Portal<br> ===<br />
<br />
1. The entry page of Portal: <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication through EduGain, X509, ... <br />
<br />
3. Registration requirements:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option available for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case of problems/additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid<br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal <br />
<br />
2. Access in blocked when initial allocation is over <br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs <br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation): <br />
<br />
*Scientific paper <br />
*Project that is using EGI <br />
*...<br />
<br />
=== Additions: ===<br />
<br />
*The User Registration Portal needs to generate DNs for new users, and be ready to communicate the list of user DNs to VOMS<br></div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76631Long-tail of science pilot User story2015-01-27T12:50:50Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/Register into Portal<br> ===<br />
<br />
1. The entry page of Portal: <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication through EduGain, X509, ... <br />
<br />
3. Registration requirements:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option available for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid <br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal <br />
<br />
2. Access in blocked when initial allocation is over <br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs <br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation): <br />
<br />
*Scientific paper <br />
*Project that is using EGI <br />
*...<br />
<br />
=== Additions: ===<br />
<br />
*The User Registration Portal needs to generate DNs for new users, and be ready to communicate the list of user DNs to VOMS<br></div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76630Long-tail of science pilot User story2015-01-27T12:50:16Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/Register into Portal<br> ===<br />
<br />
1. The entry page of Portal: <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication through EduGain, X509, ... <br />
<br />
3. Registration requirements:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option available for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid <br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal <br />
<br />
2. Access in blocked when initial allocation is over <br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs <br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation): <br />
<br />
*Scientific paper <br />
*Project that is using EGI <br />
*...<br />
<br />
=== Additions: ===<br />
<br />
*The User Registration Portal eeds to generate DNs for new users, and be ready to communicate the list of user DNs to VOMS<br></div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76628Long-tail of science pilot User story2015-01-27T12:37:30Z<p>Agpul: /* Step 1: User Login/Register into Portal */</p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/Register into Portal<br> ===<br />
<br />
1. The entry page of Portal:<br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication through EduGain, X509, ... <br />
<br />
3. Registration requirements:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option available for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid <br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal<br />
<br />
2. Access in blocked when initial allocation is over<br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs<br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation):<br />
<br />
*Scientific paper<br />
*Project that is using EGI<br />
*...</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76626Long-tail of science pilot User story2015-01-27T11:50:51Z<p>Agpul: /* Step 1: User Login/register into Portal */</p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/Register into Portal<br> ===<br />
<br />
1. The entry page of Portal <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ... <br />
<br />
3. Registration requirement:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option avaialbe for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid <br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal<br />
<br />
2. Access in blocked when initial allocation is over<br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs<br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation):<br />
<br />
*Scientific paper<br />
*Project that is using EGI<br />
*...</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76616Long-tail of science pilot User story2015-01-27T08:23:12Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal<br> ===<br />
<br />
1. The entry page of Portal <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ... <br />
<br />
3. Registration requirement:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option avaialbe for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid <br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. User has a link to SGs <br />
<br />
2. User sees allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal<br />
<br />
2. Access in blocked when initial allocation is over<br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs<br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation):<br />
<br />
*Scientific paper<br />
*Project that is using EGI<br />
*...</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76615Long-tail of science pilot User story2015-01-27T07:46:13Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal<br> ===<br />
<br />
1. The entry page of Portal <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ... <br />
<br />
3. Registration requirement:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option avaialbe for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid <br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. Users have a link to SGs <br />
<br />
2. Users see allocation with default (seed reasources): <br />
<br />
*Max <br />
*Single form: register in eGRANT <br />
*Special, central pool for EGI-seed resource <br />
*In request: describe what he is doing <br />
*Allow for more than one request<br />
<br />
=== Step 4: User is using services ===<br />
<br />
1. Portal display summary of the used rsources or may provide direct link to the view in Accounting Portal<br />
<br />
2. Access in blocked when initial allocation is over<br />
<br />
*Notification and uncouragement to request full resources request<br />
<br />
=== Step 5: User uses feedback form ===<br />
<br />
1. Interface encourage to write to EGI and express his/her needs<br />
<br />
=== Step 6: User report results supported by EGI ===<br />
<br />
1. User uses form to report result supported by EGI (it is his/her obligation):<br />
<br />
*Scientific paper<br />
*Project that is using EGI<br />
*...</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76614Long-tail of science pilot User story2015-01-27T07:38:04Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal<br> ===<br />
<br />
1. The entry page of Portal <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ... <br />
<br />
3. Registration requirement:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option avaialbe for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added: <br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken <br />
<br />
3. Included the date for how long the affiliation is valid <br />
<br />
=== Step 3: User requests initial resources/services ===<br />
<br />
1. Users have a link to SGs <br />
<br />
2. Users see allocation with default (seed reasources):<br />
<br />
*Max<br />
*Single form: register in eGRANT<br />
*Special, central pool for EGI-seed resource<br />
*In request: describe what he is doing<br />
*Allow for more than one request</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76613Long-tail of science pilot User story2015-01-27T07:33:22Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal<br> ===<br />
<br />
1. The entry page of Portal <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ... <br />
<br />
3. Registration requirement:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option avaialbe for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed: <br />
<br />
*Country/NGI <br />
*Related site (optional) <br />
*Institution (including department) <br />
*Address <br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources <br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added <br />
<br />
=== Step 2.1: Affilaition is verified ===<br />
<br />
1. Operationa Staff is veryfing affilaition added:<br />
<br />
*In case problems/need additional information - communication via user e-mail<br />
<br />
2. E-mail notification to user about decision taken<br />
<br />
3. Included the date for how long the affiliation is valid</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76612Long-tail of science pilot User story2015-01-27T07:29:54Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal<br> ===<br />
<br />
1. The entry page of Portal <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ... <br />
<br />
3. Registration requirement:<br> <br />
<br />
*Required fields: Full name, country, validated email address <br />
*Optional fields: ResearchGate profile, LinkedIn profile, ... <br />
*Acceptance of general Usage Policy <br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created <br />
<br />
*Option avaialbe for verified user are visible but nonactive<br />
<br />
4. Additions: <br />
<br />
*User should confirm the APU of LTOS VO <br />
*User should describe in request what he/she will be doing<br />
<br />
=== Step 2: User adds his/her affiliation ===<br />
<br />
1. Information needed:<br />
<br />
*Country/NGI<br />
*Related site (optional)<br />
*Institution (including department)<br />
*Address<br />
*Web-page of the institution (with list of Staff)<br />
<br />
2. Verified affilaition of the user is required to obtain access to resources<br />
<br />
*More than one affilaition might be possible<br />
<br />
3. For non-Staff supervisor name, e-mail shoul be added</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76611Long-tail of science pilot User story2015-01-27T07:27:08Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal<br> ===<br />
<br />
1. The entry page of Portal <br />
<br />
*Basic info about EGI offer <br />
*Info about similar national options for access <br />
*Encouragement to register <br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ... <br />
<br />
3. Registration requirement:<br><br />
<br />
*Required fields: Full name, country, validated email address<br />
*Optional fields: ResearchGate profile, LinkedIn profile, ...<br />
*Acceptance of general Usage Policy<br />
*At this stage account is created instantly (without any verification)<br />
<br />
4. Result: Simple account in the portal is created<br />
<br />
*Option avaialbe for verified user are visible but nonactive<br />
<br />
4. Additions:<br />
<br />
*User should confirm the APU of LTOS VO<br />
*User should describe in request what he/she will be doing</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76610Long-tail of science pilot User story2015-01-27T07:22:55Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal<br> ===<br />
<br />
1. The entry page of Portal<br />
<br />
*Basic info about EGI offer<br />
*Info about similar national options for access <br />
*Encouragement to register<br />
*Login and Register option easy visible<br />
<br />
2. Login option include local account and authentication thought EduGain, X509, ...<br />
<br />
3.</div>Agpulhttps://wiki.egi.eu/w/index.php?title=Long-tail_of_science_pilot_User_story&diff=76609Long-tail of science pilot User story2015-01-27T07:19:26Z<p>Agpul: </p>
<hr />
<div>= User Story for 1st phase LToS =<br />
<br />
=== Step 1: User Login/register into Portal ===</div>Agpul