Misc.

NRAO Interactive Services Modification Request 2 S2 2011

---

---

1. Introduction

Misc. changes to the system.

2. Background

3. Requirements

• Student Support (from JeffMangum)
  • Validation check of proposals which have students as Co-Is: This is the change listed below. To summarize, the validation check, when it detects that no SOS proposal is associated with an observing proposal which has a student Co-I (who is also a US citizen), could pop-up a note which suggests to the proposer that they consider submitting an SOS proposal. To summarize, the process would be something like this:
    • Proposal with student as co-PI but which does not include a request for SOS funds is validated.
    • Validation response responds as usual, but with the additional note: "Your proposal qualifies for our Student Observing Support (SOS) program. Please consider adding an application for SOS support to your proposal. This should take only a few minutes to complete. See the SOS program information at https://science.nrao.edu/opportunities/student-programs/sos for further information."
• Additional field entry for SOS Proposal Principal Investigator: This is a request from the Users Committee which is meant to paper-over the issue of NRAO staff being PIs of observing proposals which request SOS funds. We need a (possibly) separate PI for the SOS grant that will in most cases be a proposal Co-I from the student's school or institute (which is what the help text associated with this field should state).
• Routine PST Framework upgrades
• QueryFilter Proposal XML updates to include Reviews information
• Account merging email updates to inform Socorro and GBT software groups
• Update the Dashboard
  • Documentation. Change the links
    • [VLBA Observing Guides and Tools] <http://science.nrao.edu/vlba/obsprop>
  • Feedback. Please remove this page. The helpdesk can be used to provide feedback.
  • Polices. (DanaBalser will add text here.)
• Update Helpdesk. Use the following text for the main tab.

Welcome to the NRAO helpdesk.

Please use the helpdesk for questions concerning EVLA, VLBA, AIPS, CASA, Archive Access, and Proposal Submission.

[Login to the NRAO Helpdesk.] <https://help.nrao.edu/>

For questions concerning ALMA/NAASC use the [ALMA helpdesk.] <https://alma-help.nrao.edu>

• Automatic Email. Below is the email all authors on a proposal should receive after submission. This is for all telescopes.

**********************************************************************
         THIS IS AN ACKNOWLEDGEMENT OF YOUR PROPOSAL
**********************************************************************

Proposal ID: VLA/12A-111 (Regular)
Proposal Title: Testing General Relativity
PI: Albert Einstein

Your proposal submission has entered the NRAO system.

If you have any questions or concerns about your proposal submission,
please submit a ticket to the Proposal Submission department of the
NRAO Helpdesk at https://help.nrao.edu

**********************************************************************
         THIS IS AN AUTOMATED MESSAGE
********************************************************************** 

• Modify the legacy codes for the GBT to be Qxnnn (e.g., QA123) instead of Gxnnn (e.g., GA123). This should be done for all legacy codes generated for the GBT in the past. Any VLBI legacy code beginning with G should be untouched. (contact: GarethHunt)
• Make the proposal code (TEL/YYA-NNN) serial numbers unique. There should be a single sequence of numbers (NNN) starting from 001. At present, GBT/11A-001, VLA/11A-001, VLBA/11A-001, and VLBI/11A-001 are all present. Assuming that the first four proposals submitted in 12A are for the GBT, VLA, GBT, VLBA (in that order), they should (for example) be created with proposal codes GBT/12A-001, VLA/12A-002, GBT/12-003, VLBA/12A-004 so that the serial numbers are unique. (contact: GarethHunt)

4. Design

Technical lead should provide a brief description of how this will be implemented in the code.

5. Deployment Checklist

Documentation? Systems/hardware/networking things needed for deployment?

6. Test Plan

6.1 Internal Testing

6.2 Sponsor Testing

6.3 Integration/Regression Tests

---

Signatures

APPROVED: I acknowledge that my request is fully contained in this MR, and if the Open Sky (or other NIS or PST developers) deliver exactly what I specified, I will be happy.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written	- - - - -
Checked	- - - - -
Approved by Scientific Sponsor	- - - - -
Accepted/Delivered by Sponsor	- - - - -

Symbols:

• Use %X% if MR is not complete (will display )
• Use %Y% if MR iscomplete (will display )

---

Discussion Area

-- DanaBalser - 2011-05-27