Right now the state of a Submission really only varies between active (Open) and inactive (Closed) by way of the active attribute on the Submission model.
In order for Rebecca to directly control which Submissions appear in the Assessor's Recently Closed List we'd like to create a way to categorize closed Submissions by whether or not we plan on proceeding with an interview.
The thought is we could add an attribute to the Submission schema designating whether we are proceeding with it or not. Then, in the list of Recently Closed Submissions, it would only display Closed Submissions from candidates we plan on interviewing. This effectively turns the Recently Closed Submissions list into a List of Candidates You May Interview... So we may also want to change the name of the list in the template.
Right now the state of a Submission really only varies between active (Open) and inactive (Closed) by way of the
activeattribute on the Submission model.In order for Rebecca to directly control which Submissions appear in the Assessor's Recently Closed List we'd like to create a way to categorize closed Submissions by whether or not we plan on proceeding with an interview.
The thought is we could add an attribute to the Submission schema designating whether we are proceeding with it or not. Then, in the list of Recently Closed Submissions, it would only display Closed Submissions from candidates we plan on interviewing. This effectively turns the Recently Closed Submissions list into a List of Candidates You May Interview... So we may also want to change the name of the list in the template.