Workflow after reviews after ratings have been sorted
Ponder asked what happens after review: How are we proceeding if a session gets accepted? -> Accepted screen How are we proceeding if a session gets rejected? -> Rejected screen Who is able to accept/reject sessions? -> admin, orga, coordinator
After all the reviewes have been performed on the Session Reviews screen all sessions can be sorted by Averge rating from highest to lowest. All sessions have a minimum of 2 Event ratings count. Sessions also each have a colour: orange, yellow, red or green (issue #81 (closed)).
Admins and orgas can then scan all the reviews and remove colour codes if appropriate. They can also add another (3rd or 4th) review if they judge it is needed for a given event.
At some agreed time Session Reviewes screen takes a final appearance (no need for coding, this is a social infrastructure decision).
On this Session reviews screen there are tick boxes for Accept and Reject each event. Events get a tick for accept or reject each (not both). This can be a dropdown as well, if that is easier. At the bottom of the page then there is button Accept and Reject selcted papers. Clicking that button moves selected papers to accepted or rejected screens. Papers with no tick stay on review screen and can still be worked on.
Accept or reject selection is visible to admin, orga, coordinator. All can perform selection (if it is a problem for coordinators to perform actions here, but not review events, exclude coordinators from this list).
On accepted screen: should be a button for sending out collective emails ('accept with notification' or similar) to submitters that their submissions have been accepted and instructions how they can register for the conference. at a later step accepted and registered papers should then move to the Registered screen for room and time scheduling. Each event should also have an option to be returned to the Session Review screen (unselected from accepted screen).
On rejected screen: should be a button for sending out collective emails ('reject with notification' or similar) to submitters that their submissions have been rejected and instructions how they can resubmit as individual papers.
Each event should also have an option to be returned to the Session Review screen (unselected from rejected screen).
Ideally there should be no events left on the Session Review screen. But for the few that are left admins, orgas and coordinators can view session details and find contacts of submitters and write to them concerning some special case (like: 'you are still in the selection pool, please wait, some other special msg).
Next task has to be the arrangement of Accepted screen for purposes of registration and scheduling, that is another story.