<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Akpawar</id>
	<title>Expertiza_Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Akpawar"/>
	<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Special:Contributions/Akpawar"/>
	<updated>2026-09-11T19:00:36Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118015</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118015"/>
		<updated>2018-11-02T15:52:54Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======'''Tree_display_controller.rb File'''======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======= '''List.html.erb file''' ======&lt;br /&gt;
This file has been modified so that the tree_display.jsx file is able to access the sub-tab which is recently been clicked so that the function within display.jsx is able to expand the sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#list.html.erb&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Manage content&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;%= link_to 'Manage Notifications', notifications_url %&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;tree_display&amp;quot; params=&amp;quot;#{@reactjsParams}&amp;quot; data-menu-item= '&amp;lt;%= &amp;quot;#{@current_controller}&amp;quot; %&amp;gt;'&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|intial Manage Page]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;center&amp;quot; style=&amp;quot;width: auto; margin-left: auto; margin-right: auto;&amp;quot;&amp;gt;'''Intial Manage  Page'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;center&amp;quot; style=&amp;quot;width: auto; margin-left: auto; margin-right: auto;&amp;quot;&amp;gt;'''Review Rubric Page'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;center&amp;quot; style=&amp;quot;width: auto; margin-left: auto; margin-right: auto;&amp;quot;&amp;gt;'''Meta Rubric Page'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118013</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118013"/>
		<updated>2018-11-02T15:48:28Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|intial Manage Page]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;center&amp;quot; style=&amp;quot;width: auto; margin-left: auto; margin-right: auto;&amp;quot;&amp;gt;'''Intial Manage  Page'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;center&amp;quot; style=&amp;quot;width: auto; margin-left: auto; margin-right: auto;&amp;quot;&amp;gt;'''Review Rubric Page'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;center&amp;quot; style=&amp;quot;width: auto; margin-left: auto; margin-right: auto;&amp;quot;&amp;gt;'''Meta Rubric Page'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118012</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118012"/>
		<updated>2018-11-02T15:46:29Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|intial Manage Page]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;center&amp;quot; style=&amp;quot;width: auto; margin-left: auto; margin-right: auto;&amp;quot;&amp;gt;'''Intial Load Page'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118009</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118009"/>
		<updated>2018-11-02T15:44:31Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|intial Manage Page]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118008</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118008"/>
		<updated>2018-11-02T15:43:57Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|alt=Alt|intial Manage Page]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118007</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118007"/>
		<updated>2018-11-02T15:42:56Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|thumb|intial Manage Page]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118006</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118006"/>
		<updated>2018-11-02T15:42:09Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|thumb|{intial Manage Page]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118004</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118004"/>
		<updated>2018-11-02T15:39:27Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;u&amp;gt;intial Manage Page&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118002</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118002"/>
		<updated>2018-11-02T15:33:51Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''goto_controller():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
======'''list():'''====== &lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118001</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118001"/>
		<updated>2018-11-02T15:32:27Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
'''goto_controller()''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
'''list()''' :&lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
def list&lt;br /&gt;
    @current_controller = params[:current_controller]&lt;br /&gt;
    redirect_to controller: :content_pages, action: :view if current_user.nil?&lt;br /&gt;
    redirect_to controller: :student_task, action: :list if current_user.try(:student?)&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118000</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=118000"/>
		<updated>2018-11-02T15:30:31Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
'''goto_controller()''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
'''list()''' :&lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117999</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117999"/>
		<updated>2018-11-02T15:29:28Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
'''goto_controller()''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
'''list()''' :&lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117998</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117998"/>
		<updated>2018-11-02T15:28:45Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117997</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117997"/>
		<updated>2018-11-02T15:27:58Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . The Function looks for which sub-tab has been clicked and expands the state of the clicked sub-tab.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.This Function also handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
__TOC__&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt; This function generates instance variable which contains the params variable current value and makes that value available to the list.html.erb file.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117995</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117995"/>
		<updated>2018-11-02T15:23:03Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;{intial Manage Page}&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117994</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117994"/>
		<updated>2018-11-02T15:22:23Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|caption=&amp;quot;intial Manage Page&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117993</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117993"/>
		<updated>2018-11-02T15:20:04Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|&amp;quot;intial Manage Page&amp;quot;]]&lt;br /&gt;
... Initial Manage Page&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117991</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117991"/>
		<updated>2018-11-02T15:15:45Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png|&amp;quot;intial Manage Page&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|&amp;quot;When clicked on Review Rubric&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png|&amp;quot;when clicked on Meta Review Rubric&amp;quot;]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117988</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117988"/>
		<updated>2018-11-02T15:13:27Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:meta.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:Meta.png&amp;diff=117986</id>
		<title>File:Meta.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:Meta.png&amp;diff=117986"/>
		<updated>2018-11-02T15:12:30Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117985</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117985"/>
		<updated>2018-11-02T15:00:22Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png]]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117984</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117984"/>
		<updated>2018-11-02T14:59:37Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:Manage.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:Manage.png&amp;diff=117983</id>
		<title>File:Manage.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:Manage.png&amp;diff=117983"/>
		<updated>2018-11-02T14:58:39Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:InitialLoad.png&amp;diff=117980</id>
		<title>File:InitialLoad.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:InitialLoad.png&amp;diff=117980"/>
		<updated>2018-11-02T14:50:50Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: uploaded a new version of &amp;amp;quot;File:InitialLoad.png&amp;amp;quot;: Reduced size&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;E8141- pics- InitialLoad&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117979</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117979"/>
		<updated>2018-11-02T14:47:59Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117978</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117978"/>
		<updated>2018-11-02T14:47:11Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|50px]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117977</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117977"/>
		<updated>2018-11-02T14:46:56Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|frame|50px]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117976</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117976"/>
		<updated>2018-11-02T14:46:38Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|frame|100px]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117974</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117974"/>
		<updated>2018-11-02T14:46:05Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: /* Solution Screenshots */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|Frame|100px]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117973</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117973"/>
		<updated>2018-11-02T14:45:47Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: /* Solution Screenshots */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|100px]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117971</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117971"/>
		<updated>2018-11-02T14:44:10Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|InitialLoad.png|100px]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117969</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117969"/>
		<updated>2018-11-02T14:43:04Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|InitialLoad.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117968</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117968"/>
		<updated>2018-11-02T14:42:40Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png|300px|]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117967</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117967"/>
		<updated>2018-11-02T14:41:25Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: /* Solution Screenshots */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:InitialLoad.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:InitialLoad.png&amp;diff=117966</id>
		<title>File:InitialLoad.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:InitialLoad.png&amp;diff=117966"/>
		<updated>2018-11-02T14:40:57Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: E8141- pics- InitialLoad&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;E8141- pics- InitialLoad&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117964</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117964"/>
		<updated>2018-11-02T14:32:58Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: /* Solution Screenshots */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:screenshot.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117963</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117963"/>
		<updated>2018-11-02T14:31:21Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot from 2018-11-02 01-29-10.png|300px|]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117961</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117961"/>
		<updated>2018-11-02T14:16:36Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:Screenshot_from_2018-11-02_01-29-10.png&amp;diff=117946</id>
		<title>File:Screenshot from 2018-11-02 01-29-10.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:Screenshot_from_2018-11-02_01-29-10.png&amp;diff=117946"/>
		<updated>2018-11-02T07:00:10Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: uploaded a new version of &amp;amp;quot;File:Screenshot from 2018-11-02 01-29-10.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117942</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117942"/>
		<updated>2018-11-02T06:50:44Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
[[File:Screenshot from 2018-11-02 01-29-10.png|200px|]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:Screenshot_from_2018-11-02_01-29-10.png&amp;diff=117941</id>
		<title>File:Screenshot from 2018-11-02 01-29-10.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:Screenshot_from_2018-11-02_01-29-10.png&amp;diff=117941"/>
		<updated>2018-11-02T06:49:01Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117940</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117940"/>
		<updated>2018-11-02T06:47:55Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;br /&gt;
[[File:Screenshot from 2018-11-02 01-29-10.png]]&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117939</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117939"/>
		<updated>2018-11-02T06:42:05Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx File======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
======Tree_display_controller.rb File======&lt;br /&gt;
In this file , there are two functions been updated viz. '''goto_controller()''' and ''' list()'''. &lt;br /&gt;
'''goto_controller''' :&lt;br /&gt;
&amp;lt;li&amp;gt; The modification in goto_controller enables the function to keep a track of which tab was last opened by adding a new parameter viz. '''last_open_tab''' and setting its  values to the integer value corresponding to the position of the tab on the web page . example , if the Questionnaires tab is opened then a value of 3 will be assigned to the last_opened_tab parameter as the position of the Questionnaires tab is 3 on the web page.&lt;br /&gt;
'''list''' :&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#Adding of the parameter &lt;br /&gt;
def goto_controller(name_parameter, last_open_tab)&lt;br /&gt;
    node_object = TreeFolder.find_by(name: name_parameter)&lt;br /&gt;
    session[:root] = FolderNode.find_by(node_object_id: node_object.id).id&lt;br /&gt;
    session[:last_open_tab] = last_open_tab unless last_open_tab.nil?&lt;br /&gt;
    redirect_to controller: 'tree_display', action: 'list', current_controller: name_parameter&lt;br /&gt;
  end&lt;br /&gt;
#Setting of the Parameter&lt;br /&gt;
def goto_questionnaires&lt;br /&gt;
    goto_controller('Questionnaires', '3')&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117936</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117936"/>
		<updated>2018-11-02T06:26:22Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
======Tree_display.jsx======&lt;br /&gt;
This File was been modified by adding a function on line 478 viz. '''componentDidMount: function()''' . This Function handles the direction of the control from Questionnaires tab to the Review Rubrics Tab when Review Rubrics tab is being clicked.&lt;br /&gt;
======Function Code Snippet======&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 componentDidMount: function() {&lt;br /&gt;
      selectedMenuItem = document.getElementById(&amp;quot;tree_display&amp;quot;).getAttribute(&amp;quot;data-menu-item&amp;quot;);&lt;br /&gt;
      rubricArray = [&amp;quot;Review&amp;quot;, &amp;quot;Metareview&amp;quot;, &amp;quot;Author Feedback&amp;quot;, &amp;quot;Teammate Review&amp;quot;, &amp;quot;Course Survey&amp;quot;, &amp;quot;Assignment Survey&amp;quot;, &amp;quot;Global Survey&amp;quot;];&lt;br /&gt;
      selectedMenuItemIndex = rubricArray.indexOf(selectedMenuItem);&lt;br /&gt;
&lt;br /&gt;
      if(selectedMenuItemIndex !== -1 &amp;amp;&amp;amp; rubricArray[selectedMenuItemIndex] === this.props.name) {&lt;br /&gt;
          this.setState({&lt;br /&gt;
              expanded: true&lt;br /&gt;
          }, function() {&lt;br /&gt;
              this.props.rowClicked(this.props.id, true,this.props.newParams)&lt;br /&gt;
          })&lt;br /&gt;
      }&lt;br /&gt;
    },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
======Solution Screenshots======&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117906</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117906"/>
		<updated>2018-11-02T05:19:11Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
=====old code snippet=====&lt;br /&gt;
&lt;br /&gt;
=====Solution Description=====&lt;br /&gt;
&lt;br /&gt;
=====New Code snippet=====&lt;br /&gt;
&lt;br /&gt;
=====Solution Screenshots=====&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117905</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117905"/>
		<updated>2018-11-02T05:18:05Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
======old code snippet======&lt;br /&gt;
&lt;br /&gt;
======Solution Description======&lt;br /&gt;
&lt;br /&gt;
======New Code snippet======&lt;br /&gt;
&lt;br /&gt;
======Solution Screenshots======&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117900</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117900"/>
		<updated>2018-11-02T05:08:18Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
===== old code snippet=====&lt;br /&gt;
&lt;br /&gt;
=====Solution Description======&lt;br /&gt;
&lt;br /&gt;
===== New Code snippet =====&lt;br /&gt;
&lt;br /&gt;
===== Solution Screenshots======&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117897</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117897"/>
		<updated>2018-11-02T05:06:53Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== &lt;br /&gt;
&lt;br /&gt;
When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
&lt;br /&gt;
===== old code snippet: =====&lt;br /&gt;
&lt;br /&gt;
=====Solution Description:  ======&lt;br /&gt;
&lt;br /&gt;
===== New Code snippet =====&lt;br /&gt;
&lt;br /&gt;
===== Solution Screenshots ======&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117896</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117896"/>
		<updated>2018-11-02T05:05:55Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
====Issue 1==== When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
===== old code snippet: =====&lt;br /&gt;
&lt;br /&gt;
=====Solution Description:  ======&lt;br /&gt;
&lt;br /&gt;
===== New Code snippet =====&lt;br /&gt;
&lt;br /&gt;
===== Solution Screenshots ======&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117895</id>
		<title>CSC/ECE 517 Fall 2018/E1841 Issues Related to Rubrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2018/E1841_Issues_Related_to_Rubrics&amp;diff=117895"/>
		<updated>2018-11-02T05:02:25Z</updated>

		<summary type="html">&lt;p&gt;Akpawar: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==E1553 : Issues Related to Rubrics==&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Introdution===&lt;br /&gt;
Expertiza is an Peer Review Web Application System. It allows multiple students to participate in various assignments posted by the Instructor and provides a platform to all the students to conduct a peer review on the work done by their peers. Expertiza is an opensource project written in Ruby on Rails and React.js. We as a team have targeted some specific issues related to this project and Have tried Our best to fix them.&lt;br /&gt;
=== Problem Statement===&lt;br /&gt;
&lt;br /&gt;
====What it Does ====&lt;br /&gt;
In Expertiza, instructors (also admin, super admin and TAs) can create rubrics (they are called questionnaires in DB, there are different types like review rubric, teammate review rubric, etc.  Each rubric may have one or many criteria (called questions in DB). For each criterion, it may have 0 to many suggestions.&lt;br /&gt;
&lt;br /&gt;
====Fixes Required====&lt;br /&gt;
&amp;lt;li&amp;gt; If an instructor has created an assignment with specific review rubric and reviews have been performed using the same rubric. After that if an instructor changes the rubric to more reasonable one, the reviews performed earlier won’t work. You need to fix this issue. An instructor should be warned about changing the rubric if there are outstanding reviews. Maybe it would be better to ask the instructor whether to delete previous reviews, &amp;amp; if so, tell the students to redo those reviews because the rubric has changed.&lt;br /&gt;
&amp;lt;li&amp;gt;After an instructor has created an assignment and if an assignment is rubric-varying-by-round and then mistakenly changed to be not varying by round, and then corrected to be varying-by-round again, the formative rubric is applied to all rounds. Of course this is incorrect; the summative rubric should be re-enabled for the summative round. The problem is that when you make an assignment rubric-varying-by-round, the Javascript just assumes that the summative review is the same as the formative review. AJAX should be added to fetch the summative review ID from the db (it’s still there, because we assume the assignments_questionnaires table entry hasn’t been removed). You need to fix this issue.&lt;br /&gt;
&amp;lt;li&amp;gt;Log in as an instructor into the expertiza system. If you try to select &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot;, it should pull up a list of review rubrics. But actually, it just takes you to the main Questionnaires page. The exact same error is happening for &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Author feedback&amp;quot;, etc. You need to figure out what causes the error and fix it.&lt;br /&gt;
&lt;br /&gt;
=== Current Functionality===&lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to create an Assignment with a specific rubric set for the assignment. &lt;br /&gt;
&amp;lt;li&amp;gt; Instructor able to populate an Assignment with multiple rubrics&lt;br /&gt;
&amp;lt;li&amp;gt; Display of the Main tabs&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Solutions ===&lt;br /&gt;
&amp;lt;li&amp;gt; ==== Issue 1. ==== : When one tries to select  &amp;quot;Manage &amp;gt; Questionnaires &amp;gt; Review rubrics&amp;quot; , it just takes back to the Questionnaires Main page rather than displaying the Review rubrics page.&lt;br /&gt;
===== old code snippet: =====&lt;br /&gt;
&lt;br /&gt;
=====Solution Description:  ======&lt;br /&gt;
&lt;br /&gt;
===== New Code snippet =====&lt;br /&gt;
&lt;br /&gt;
===== Solution Screenshots ======&lt;/div&gt;</summary>
		<author><name>Akpawar</name></author>
	</entry>
</feed>