You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
Agenda:
- There is currently no way for the TTA member to makes changes to a proposal with the Proposal State of In Review. (There is no option to resubmit a modified Observatory Copy, as it must be saved first to trigger the re-submit button and any saved changes are applied to the Author Copy and not the Observatory Copy.)
- Proposed changes:
- Saves to the Observatory Copy should not affect the Author Copy
- Modification by TTA Member:
- TTA member modifies Author Copy and can resubmit (triggers notifications) at any time, regardless of Solicitation being Open or Closed and regardless of Proposal State.
- TTA member modifies Observatory Copy and re-submits at any time (triggers notifications), regardless of Solicitation being Open or Closed and regardless of Proposal State.
- TTA member saves Observatory Copy without resubmitting, regardless of Solicitation being Open or Closed and regardless of Proposal State. No notification is triggered (currently)
- This work is scheduled for STT-863
- Can a Proposal with Proposal State of Hidden be Withdrawn?
- Behavior of a Withdrawn Proposal
- Withdrawn proposals should not be displayed in Review Process Configuration, ISRs, etc or in the OSR reviews.
- In Review → Withdrawn is a valid State Model transitions. Currently, the UI still displays a proposal if it went Submitted→ In Review → Withdrawn during the Vetting and ISRs. This is obviously not desirable.
- It works properly for OSR proposals.
- Presumably, the withdrawn proposal is not even shown for the TTA member.
- Should system restrict the ability to Withdraw a proposal for a TTA member, for example, until Review Process Configuration is Finalized? Though we likely have the Policy to never Withdrawn once the reviews have actually started, we might by some accident, find ourselves in an awkward state.
- For example, the Primary, Second etc save reviews. Then the proposal is Withdrawn. The ISRs cannot be finalized and so essentially Consensus is locked out.
- Concern: the state transitions for the Review Process stall because of a Proposal that is Withdrawn at some point and can never have its ISRs finalized.
- Do we need an additional check on the Proposal State during the review process transitions to protect against this?
- Policy Discussion with Toney R.
- Keeping Technical Reviews for Large Proposals
- Would like ability to specify at Solicitation configuration a granularity to what proposals will have a review
- e.g., Astrometry, VLBI, subarrays
- Review of Past Disposition Letters at Consensus → No
