E1785 OSS project Beige: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 13: Line 13:
'''What needs to be done: '''  
'''What needs to be done: '''  


The reviewer should know which submissions are updated since he/she submitted the review. This can be done in UI of the reviewer’s page. The submissions can be color-coded using a scheme like the one used in the “Review Report” page.
The reviewer should be able to know the status of any review he/she is doing. This can be done in UI of the reviewer’s page. The submissions can be color-coded using a scheme similar to the one used in the “Review Report” page for the instructor in expertiza. The color coding scheme implemented by us is: <br>


Red – If the review has not been started<br>
Red – If the review has not been started<br>
Orange – If the review was started, but not completed<br>
Orange – If the review was started, but not completed<br>
Brown – Submission has been reviewed  
Brown – Submission has been reviewed<br>
 
Since the logic for the links of “View”,”Begin”,”Update”,”Edit” are already present, the 'Begin' link is visible only when the review has not started, so the link is 'Red' to indicate review has not yet been started. Similarly the 'Edit' and 'Update' links are visible only after the reviewer has opened the project to be reviewed at least once. So both these links can be colored 'Yellow' to indicate that the review was started but not yet completed. The 'View' link is visible only after the review was submitted, so the link can be coloured 'Brown' indicating that no further action is required on the reviewers behalf. Hence, by just colouring the links displayed to the reviewer we were able to indicate the status of the review being done.


'''Solutions Implemented and Delivered'''
'''Solutions Implemented and Delivered'''

Revision as of 11:44, 1 November 2018

E1785.UI features related to revision time

This page provides a description of the Expertiza based OSS project.

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 reviewer reviews a submission, the participant updates the submission if they find the review comments useful. Once the submission is updated, 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 would be useful for him / her to be able to quickly identify the submissions that need attention. Currently, there is no way of doing this.

What needs to be done:

The reviewer should be able to know the status of any review he/she is doing. This can be done in UI of the reviewer’s page. The submissions can be color-coded using a scheme similar to the one used in the “Review Report” page for the instructor in expertiza. The color coding scheme implemented by us is:

Red – If the review has not been started
Orange – If the review was started, but not completed
Brown – Submission has been reviewed

Since the logic for the links of “View”,”Begin”,”Update”,”Edit” are already present, the 'Begin' link is visible only when the review has not started, so the link is 'Red' to indicate review has not yet been started. Similarly the 'Edit' and 'Update' links are visible only after the reviewer has opened the project to be reviewed at least once. So both these links can be colored 'Yellow' to indicate that the review was started but not yet completed. The 'View' link is visible only after the review was submitted, so the link can be coloured 'Brown' indicating that no further action is required on the reviewers behalf. Hence, by just colouring the links displayed to the reviewer we were able to indicate the status of the review being done.

Solutions Implemented and Delivered

The lines in bold in the below snippet are the colour codes we added which will add button colour in the review page.

Changes:

                       <%= link_to "View", {:controller => 'response', :action => 'view', :id => @latest_response.id} %>

<% if @assignment.get_current_stage(topic_id) != "Finished" %> <%- # show the link as edit when latest review is done in current deadline -%> <%- # show link as update when latest review is done in different deadline than current phase -%> <% if (last_response_round == current_round)%>

                         <% if (!@latest_response.is_submitted) %>
                             <%= link_to "Edit", {:controller => 'response', :action => 'edit', :id => @latest_response.id} %>
                         <%end%>

<% else %> <%= link_to "Update", {:controller => 'response', :action => 'new', :id => map.map_id} %> <%= link_to "Update", {:controller => 'response', :action => 'new', :id => map.map_id} %>

                     <% end %>
                   <% end %>

<%= " -- latest update at #{@latest_response.updated_at.strftime("%a, %b %d, %Y %I:%M:%S %p")}" %>

         <%end%>
           <% elsif @assignment.get_current_stage(topic_id) != "Complete" && @assignment.can_review(topic_id) %>

<%= link_to "Begin", {:controller => 'response', :action => 'new', :id => map.id} %> <%= link_to "Begin", {:controller => 'response', :action => 'new', :id => map.id} %>   

           <% else %>

Begin


Files Updated:

app/views/student_review/_responses.html.erb

Screenshots of new implementation: