...
There is a pulldown menu to copy the previous set of reviewers to a new cycle, available when you create or edit a cycle. It doesn't function properly, but the extent of the problems are not yet clear. More testing necessary.
Reset Review Flags:
Requested By: email/slack
Actions: Simple query to set 'accept_reviews' to false for all reviewers
Reported To: email/slack
Comments:
As with the reviewer copying, this need is likely the result of a bug in the software that doesn't appropriately update this information for the appropriate reviewers (especailly in the cases where the person has performed multiple types of reviews over time). This could provide a further simplification of the process if it were addressed.
Post Deadline Summaries:
Requested by: Schedule for the Cycle
...
Script: disposition_letters.sql
Reported to: email/slack
Comments:
There is a prototype program for this, but it is not yet well exercised. It is in need of some refinement for setup, and incorporation into the code repository.
Panel Normalization Flags Fix:
Requested By: email/slack
Actions: manual table exploration to identify the problems with individual reviewers
Reported To: email/slack
Comments:
One source of these problems is that the pre-normalization check doesn't consider the 'closed' flag in the database, which is what is typically used when a reviewer drops out. Proposed fix:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
Reported To: TTA Mailing List
Comments:
It is entirely possible that the GBT time allocation data could be obtained without resort to the larger data file generated by Anand. In addition, that file has far more data than is required for our purposes. A more limited query would serve us better, and would relieve Anand of the task of retrieving it from the DSS system (via a protected endpoint).
...