E2145. OSS Project Beige: Difference between revisions
No edit summary |
(second draft. updated wip feilds.) |
||
| Line 1: | Line 1: | ||
This page provides description of | This wiki page provides description of changes made under E2145 OSS assignment for Fall 2021, CSC/ECE 517. | ||
' | ==About Expertiza== | ||
[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages. | |||
==Problem Statement== | |||
When a participant updates the submission after the reading the review comments, the reviewer will have to review it again when the second review cycle starts. However, since the reviewer may have multiple submissions to review, some of which are updated, and some that are not, it becomes difficult for the reviewer to identify the updated submissions that need attention. Currently there is no way of identifying the difference between updated and stale submissions. | |||
==Proposed Solution== | |||
For identifying the submission status of the project in next review cycle, the reviewer should be able to quickly identify the submissions that need attention. This can be done in the UI of the reviewer’s page. The submissions can be color-coded using a scheme like the one used in the “Review Report” page. | |||
* <span style="color:red">Red</span> – If the review has not been started | |||
* <span style="color:orange">Orange</span> – If the review was started, but not completed | |||
* <span style="color:brown">Brown</span> – Submission has been reviewed | |||
This solution will allows reviewers to identify and prioritize their work without having to dig deep into individual submissions. | |||
==Tasks== | |||
The following would be the key tasks: | The following would be the key tasks: | ||
*Add a new model to track the status of a review | * Add a new model to track the status of a review | ||
*Upon change of review stage, update the data in the database. | * Upon change of review stage, update the data in the database. | ||
*Change color in the UI based on the status of the review. | * Change color in the UI based on the status of the review. | ||
==Implementation== | |||
===List of Changes=== | |||
WIP | |||
==Testing== | |||
===Rspec=== | |||
WIP | |||
===UI Testing=== | |||
WIP | |||
==References== | |||
#[https://github.com/expertiza/expertiza Expertiza on GitHub] | |||
#[https://github.com/WintersLt/expertiza GitHub Project Repository Fork] | |||
#[http://expertiza.ncsu.edu/ The live Expertiza website] | |||
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki] | |||
#[https://relishapp.com/rspec Rspec Documentation] | |||
Revision as of 20:47, 16 October 2021
This wiki page provides description of changes made under E2145 OSS assignment for Fall 2021, CSC/ECE 517.
About Expertiza
Expertiza is an open source project based on Ruby on Rails framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.
Problem Statement
When a participant updates the submission after the reading the review comments, the reviewer will have to review it again when the second review cycle starts. However, since the reviewer may have multiple submissions to review, some of which are updated, and some that are not, it becomes difficult for the reviewer to identify the updated submissions that need attention. Currently there is no way of identifying the difference between updated and stale submissions.
Proposed Solution
For identifying the submission status of the project in next review cycle, the reviewer should be able to quickly identify the submissions that need attention. This can be done in the UI of the reviewer’s page. The submissions can be color-coded using a scheme like the one used in the “Review Report” page.
- Red – If the review has not been started
- Orange – If the review was started, but not completed
- Brown – Submission has been reviewed
This solution will allows reviewers to identify and prioritize their work without having to dig deep into individual submissions.
Tasks
The following would be the key tasks:
- Add a new model to track the status of a review
- Upon change of review stage, update the data in the database.
- Change color in the UI based on the status of the review.
Implementation
List of Changes
WIP
Testing
Rspec
WIP
UI Testing
WIP