You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are legitimate reasons for the TAC chair to want to pull a previously allocated proposal e.g., oversubscription to a cycle.
To implement this we need a DELETE call in AllocatedProposalResource that removes the specified proposal from the "allocatedProposals" list in the cycle, and refunds any "resource" back to the pool of "resources" (observing time, ...).
The proposal remains "submitted" to the cycle, and the reviews remain in-tact, its just no longer allocated.
It would be nice to have a field somewhere outlining the reasons for the withdrawal from the TAC chair, which could be fed-back to the PI.
The text was updated successfully, but these errors were encountered:
There are legitimate reasons for the TAC chair to want to pull a previously allocated proposal e.g., oversubscription to a cycle.
To implement this we need a DELETE call in AllocatedProposalResource that removes the specified proposal from the "allocatedProposals" list in the cycle, and refunds any "resource" back to the pool of "resources" (observing time, ...).
The proposal remains "submitted" to the cycle, and the reviews remain in-tact, its just no longer allocated.
It would be nice to have a field somewhere outlining the reasons for the withdrawal from the TAC chair, which could be fed-back to the PI.
The text was updated successfully, but these errors were encountered: