Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 14 Next »

Goals

  • Develop the Recommendation page for the reviewers of the application

JIRAs

key summary type created updated due assignee reporter priority status resolution
Refresh

Requirements

RequirementImportanceNotes

The Reviewers need access to this page.

Must Have

Option to select "Recommend" or "Not Recommend"

  • For a Tenure and Promotion application, there needs to be a vote for the Tenure part and a vote for the Promotion part so there would need to be a pair of recommend/not recommend radio buttons


Must HaveThe DPC is the only committee not required to select an option; all others are

Chair of the committee is required to upload a recommendation report with the exception of the Chancellor, who can opt to only recommend or not recommend.

  • store the recommendations at the root of the google team drive
Must Have
Chair of the committee pushes the document to the next committee
via a "Review Complete" button		Must Have

See Workflow transitions screen

Committees must be able to view the recommendation
and recommendation report of the previous committees		Must HaveMove the reports to google drive

CampusRecommendationPositive VoteNegative VoteFile UploadReview Complete Button
DPCAllYes<whole number, zero or blank><whole number, zero or blank>requiredEnabled
DPCAllNo<whole number, zero or blank><whole number, zero or blank>requiredEnabled
DPCAllStrengths & Weaknesses<whole number, zero or blank><whole number, zero or blank>optionalEnabled
DPC ReduxAllYes<whole number, zero or blank><whole number, zero or blank>requiredEnabled
DPC ReduxAllNo<whole number, zero or blank><whole number, zero or blank>requiredEnabled
DPC ReduxAllStrengths & Weaknesses<whole number, zero or blank><whole number, zero or blank>requiredEnabled
DCAllYesn/a <hidden>n/a <hidden>requiredEnabled
DCAllNon/a <hidden>n/a <hidden>requiredEnabled
DeanAllYesn/a <hidden>n/a <hidden>requiredEnabled
DeanAllNon/a <hidden>n/a <hidden>requiredEnabled
ContractDeanNot CCsYes/Non/a <hidden>n/a <hidden>optionalEnabled
TRPCAllYes<whole number, zero or blank><whole number, zero or blank>requiredEnabled
TPRCAllNo<whole number, zero or blank><whole number, zero or blank>requiredEnabled
TPRC ReduxAllYes<whole number, zero or blank><whole number, zero or blank>requiredEnabled
TPRC ReduxAllNo<whole number, zero or blank><whole number, zero or blank>requiredEnabled
ChancellorAllYesn/a <hidden>n/a <hidden>optionalEnabled
ChancellorAllNon/a <hidden>n/a <hidden>optionalEnabled

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

How long is the typical recommendation report that's uploaded by a committee chair?

  • Does it require certain elements/information?
    • Yes/No votes
    • Justification

Better to upload the file because they work on it together, sometimes on google doc.

There's no required information for a recommendation report.

Can the current committee see the recommendation file of the previous committees?

Yes, they want to see the recommendation file and "Recommended" or "Not Recommended".

Only at DPC level they're not required to do a recommend/not recommend; they will upload a
file that could be strengths and weaknesses

  • No labels