Difference: ALMACalMSCreation (2 vs. 3)

Revision 32019-08-07 - MartinZwaan

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DRAFT procedure for creating ALMA MSs upon user request

Line: 17 to 17
  The user requests the calibrated data via a helpdesk ticket. The helpdesk ticket should contain the MOUS UID(s) (up to 10) of the data to calibrate. The ticket is
Changed:
<
<
received by designated EU ARC personel who hands on the MOUS UID together
>
>
received by designated EU ARC personnel who hands on the MOUS UID together
 with the ALMA user id is by email to AOG.

AOG verifies that the user is entitled to access the data on the day of the request

Line: 36 to 36
 sequentially.

AOG takes the resulting URL(s) and communicates them to the user via a standard email

Changed:
<
<
using the user's email on record with the EU ARC personel in CC who handed on the request.
>
>
using the user's email on record with the EU ARC personnel in CC who handed on the request.
 
Changed:
<
<
The EU ARC personel then closes the helpdesk ticket.
>
>
The EU ARC personnel then closes the helpdesk ticket.
 

Detailed Procedure

Create email to AOG after receipt of a request via helpdesk

Changed:
<
<
For each requested MOUS, the helpdesk personel should send one email to AOG.
>
>
For each requested MOUS, the helpdesk personnel should send one email to AOG.
  The email should have the following format:
Line: 88 to 88
  If the user is entitled, AOG also checks if the MOUS is in state delivered.
Changed:
<
<

Reply to helpdesk personel in case the user is not entitled

>
>

Reply to helpdesk personnel in case the user is not entitled

  If AOG determines that the user is not entitled at the moment to access the data, AOG replies to the request email and writes the text
Line: 101 to 101
  This concludes AOG's involvement.
Changed:
<
<
The helpdesk personel replies via helpdesk to the user using the following text:
>
>
The helpdesk personnel replies via helpdesk to the user using the following text:
 
You presently do not have access permission for the requested data.
Please wait until the data becomes public.
Changed:
<
<

Reply to helpdesk personel in case the user or the MOUS does not exist

>
>

Reply to helpdesk personnel in case the user or the MOUS does not exist

  If AOG determines that the data is faulty, i.e. the MOUS UID or the user id is invalid, AOG replies to the request email and writes the text
Line: 125 to 125
  above the quoted original email text.
Changed:
<
<
The helpdesk personel can then communcate with the user and try to fix the information.
>
>
The helpdesk personnel can then communcate with the user and try to fix the information.
 
Changed:
<
<

Reply to helpdesk personel in case the MOUS is not in state delivered

>
>

Reply to helpdesk personnel in case the MOUS is not in state delivered

  If AOG determines that the MOUS UID is not in state delivered, AOG replies to the request email and writes the text
Line: 138 to 138
  above the quoted original email text.
Changed:
<
<
The helpdesk personel can then investigate further the status of the MOUS and tell the user what can be done.
>
>
The helpdesk personnel can then investigate further the status of the MOUS and tell the user what can be done.
 

Creation and staging of the MS(s)

Line: 236 to 236
 

Email to the PI after successful completion of stagecalms

Once stagecalms has completed (which can take hours), AOG should create an email and send it to the user

Changed:
<
<
with the EU ARC helpdesk personel and dpetry@eso.org in CC.
>
>
with the EU ARC helpdesk personnel and dpetry@eso.org in CC.
  The format of the email should be the following:
Line: 265 to 265
 The staged data will be automatically deleted after 28 days by a cronjob on almasciencedev.
Changed:
<
<

Helpdesk personel closes helpdesk ticket

>
>

Helpdesk personnel closes helpdesk ticket

  Once the helpdesk person receives the email with the download link from AOG, he./she copies and pastes the email into a last comment on the ticket and closes the ticket.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding ARC TWiki? Send feedback