Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2019 - E1984. Improve self-review Link peer review & self-review to derive grades

2019-11-12T02:29:13Z

Amanend:

==E1984. Improve self-review Link peer review & self-review to derive grades==

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

__TOC__

===Problem Statement and Overview===

The Expertiza allows Instructors to create assignments with allowing self-review option to Students. Each member has to evaluate their submission with the same criteria as the peer review. Currently these scores are not used at all in the final scores for the submsission. The task here is to improve the self-review system pertaining to give it a weightage in the final scores for the submissions. Some of the objectives we try to achieve for this project are as follows –

*Provide a formula that takes both the peer review score and self-review score into account for calculating the composite score.
*The composite score should get higher as the self-review score gets closer to the peer review score.
*Make sure that the peer review scores are not visible before the self-review submission.
*Display the composite score on the “View Scores” page.
*Display the self-review scores in the "View Scores" and heat map of peer-reviews, showing that they are a different type of review.

The need for the self-review section is to know how well the students can judge their work and understand how to evaluate their flaws and rectify them. Also, if they can score themselves close to their peers, then it means that they have good self-assessment skills and they are being honest about what they think of their work.

===Code Changes Flow===

[[File:E1926_code_flow.png]]

===Use case===

[[File:E1926_use_case.jpg]] [[File:E1926_use_case_2.jpg]]

*Actors:

1. Instructor: This actor is responsible for creating assignments and adding students to the assignment.
2. Student: This actor is responsible for submitting, self-reviewing and viewing the scores.

*Actions
1. Instructor: Create Assignment, Enable Self-Review.
2. Student: Login, Add work and Submit, Submit Self-Review, View Scores.

===Previous Process===

Previously, Expertiza allowed students to submit an assignment and provides a link for self-review. Once the self-reviewing was done, the submitted score gets stored in the database but was not used in calculating the overall score of the assignment for the student. Because of this, students can score themselves higher than what they should get. This helps students in no way. So, to make productive use of this score and to help students learn self-evaluating, we have made some changes in the review score calculation which is explained in the section below.

===New Process===

We are trying to derive a new formula that takes into account the self-review score and calculates a composite score, which will be the student's final score:

#[https://drive.google.com/file/d/19jp7UdLCTdMhLiqsBR_ArU7gIpxYfkx_/view?usp=sharing Notes for deriving the formula]

=== Testing ===
Test cases are as follows:
* Peer-reviews cannot be viewed before a self-review is completed.
* Peer-reviews can be viewed immediately when self-reviews are not required.
* The derived scores can be saved to the database.
* Self-review scores are displayed with peer-review scores
* Student can only see their own self-review

== Team and Resources ==

===Team_AABD:===
*Amit Mandliya (amandli@ncsu.edu)
*Ankit Manendra (amanend@ncsu.edu)
*Bharat Sinha (bsinha2@ncsu.edu)
*Daniel Mendez Lozada (dmendez@ncsu.edu)

===References===
* [https://github.com/expertiza/expertiza/pull/1611 URL to pull request]
* [https://www.researchgate.net/profile/Paul_Vossen/publication/333022439_SCORING_MODELS_FOR_PEER_ASSESSMENT_IN_TEAM-BASED_LEARNING_PROJECTS/links/5cd6d6b4299bf14d958a4b99/SCORING-MODELS-FOR-PEER-ASSESSMENT-IN-TEAM-BASED-LEARNING-PROJECTS.pdf Scoring models for peer assessment in team-based learning projects]
* [http://tinyurl.com/PiTeamMate Tools for enabling developmental feedback and teamwork grading by peer assessment: PeerAssessPro™]

CSC/ECE 517 Fall 2019 - E1984. Improve self-review Link peer review & self-review to derive grades

2019-11-12T02:22:29Z

Amanend:

==E1984. Improve self-review Link peer review & self-review to derive grades==

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

__TOC__

===Problem Statement and Overview===

The Expertiza allows Instructors to create assignments with allowing self-review option to Students. Each member has to evaluate their submission with the same criteria as the peer review. Currently these scores are not used at all in the final scores for the submsission. The task here is to improve the self-review system pertaining to give it a weightage in the final scores for the submissions. Some of the objectives we try to achieve for this project are as follows –

*Provide a formula that takes both the peer review score and self-review score into account for calculating the composite score.
*The composite score should get higher as the self-review score gets closer to the peer review score.
*Make sure that the peer review scores are not visible before the self-review submission.
*Display the composite score on the “View Scores” page.
*Display the self-review scores in the "View Scores" and heat map of peer-reviews, showing that they are a different type of review.

The need for the self-review section is to know how well the students can judge their work and understand how to evaluate their flaws and rectify them. Also, if they can score themselves close to their peers, then it means that they have good self-assessment skills and they are being honest about what they think of their work.

===Code Changes Flow===

[[File:E1926_code_flow.png]]

===Previous Process===

Previously, Expertiza allowed students to submit an assignment and provides a link for self-review. Once the self-reviewing was done, the submitted score gets stored in the database but was not used in calculating the overall score of the assignment for the student. Because of this, students can score themselves higher than what they should get. This helps students in no way. So, to make productive use of this score and to help students learn self-evaluating, we have made some changes in the review score calculation which is explained in the section below.

===New Process===

We are trying to derive a new formula that takes into account the self-review score and calculates a composite score, which will be the student's final score:

#[https://drive.google.com/file/d/19jp7UdLCTdMhLiqsBR_ArU7gIpxYfkx_/view?usp=sharing Notes for deriving the formula]

=== Testing ===
Test cases are as follows:
* Peer-reviews cannot be viewed before a self-review is completed.
* Peer-reviews can be viewed immediately when self-reviews are not required.
* The derived scores can be saved to the database.
* Self-review scores are displayed with peer-review scores
* Student can only see their own self-review

===Reference===

[https://github.com/expertiza/expertiza/pull/1611 URL for pull request]

CSC/ECE 517 Fall 2019 - E1984. Improve self-review Link peer review & self-review to derive grades

2019-11-12T02:20:16Z

Amanend:

==E1984. Improve self-review Link peer review & self-review to derive grades==

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

__TOC__

===Problem Statement and Overview===

The Expertiza allows Instructors to create assignments with allowing self-review option to Students. Each member has to evaluate their submission with the same criteria as the peer review. Currently these scores are not used at all in the final scores for the submsission. The task here is to improve the self-review system pertaining to give it a weightage in the final scores for the submissions. Some of the objectives we try to achieve for this project are as follows –

*Provide a formula that takes both the peer review score and self-review score into account for calculating the composite score.
*The composite score should get higher as the self-review score gets closer to the peer review score.
*Make sure that the peer review scores are not visible before the self-review submission.
*Display the composite score on the “View Scores” page.
*Display the self-review scores in the "View Scores" and heat map of peer-reviews, showing that they are a different type of review.

The need for the self-review section is to know how well the students can judge their work and understand how to evaluate their flaws and rectify them. Also, if they can score themselves close to their peers, then it means that they have good self-assessment skills and they are being honest about what they think of their work.

===Code Changes Flow===

[[File:E1926_code_flow.png]]

===Previous Process===

Previously, Expertiza allowed students to submit an assignment and provides a link for self-review. Once the self-reviewing was done, the submitted score gets stored in the database but was not used in calculating the overall score of the assignment for the student. Because of this, students can score themselves higher than what they should get. This helps students in no way. So, to make productive use of this score and to help students learn self-evaluating, we have made some changes in the review score calculation which is explained in the section below.

===New Process===

We are trying to derive a new formula that takes into account the self-review score and calculates a composite score, which will be the student's final score:

#[https://drive.google.com/file/d/19jp7UdLCTdMhLiqsBR_ArU7gIpxYfkx_/view?usp=sharing Notes for deriving the formula]

== Testing ==
Test cases are as follows:
* Peer-reviews cannot be viewed before a self-review is completed.
* Peer-reviews can be viewed immediately when self-reviews are not required.
* The derived scores can be saved to the database.
* Self-review scores are displayed with peer-review scores
* Student can only see their own self-review

===Reference===

[https://github.com/expertiza/expertiza/pull/1611 URL for pull request]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-29T23:15:30Z

Amanend:

__TOC__

==About Expertiza==

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Description ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded. Currently, the homepage shows 3 tabs: Courses, Assignments and Questionnaires. Suppose a user clicks on the "courses" tab and then from the "Manage Content Tab" -> "Questionnaires", clicks on any of the options, then it will redirect to the same page and not the one which was selected. This needs to be fixed such that upon click, it opens up the corresponding rubric page with that particular rubric section expanded and also the respective tab (courses/assignments/questionnaires) must be highlighted.

==== Problem Cause (The grubby details) ====
The Manage Content page has three tabs in it namely: "Courses","Assignments" and "Questionnaires".
And the application has a feature of storing the 'Last open tab' in its session. Suppose a user was in 'Assignments' tab under 'Manage Content' Section, and when the user switches to some other tab (By clicking on Home for instance), and comes back on 'Manage Content' section (by clicking on 'Manage...' menu button), he is directed back on the 'Assignments' tab only (the tab that was opened before leaving the 'Manage Content' section).

The problem however, with this feature is that it dominates the natural flow of the application in the following scenario:
Lets say after leaving the 'Manage Content' section as mentioned above, the user clicks 'Manage...>Questionnaires', but even at this point, the user is directed again directed to 'Assignments' tab under 'Manage Content'

==== How to reproduce ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

==== Flowchart for correct behavior====

[[File:Fc issue1.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx'''
- Created "ComponentDidMount" method under this script file which is a react lifecycle function and this is invoked immediately after a component is inserted into the tree. The setState method sets the expanded attribute to true for expanding the relative grid of the rubric. This method will trigger an extra rendering but it will happen before the browser updates the screen. This function will help determine which sub-menu item is selected and expands the corresponding rubric by updating the state of the table row.
<pre>
componentDidMount: function() {
rubBuffer = ["Review", "Metareview", "Author Feedback", "Teammate Review", "Assignment Survey", "Global Survey", "Course Survey"];

selMenuItem = document.getElementById("tree_display").getAttribute("data-menu-item");
selMenuItemInd = rubBuffer.indexOf(selMenuItem);

if(rubBuffer[selMenuItemInd] === this.props.name) {
if (selMenuItemInd !== -1) {
this.setState({
expanded: true
}, function () {
this.props.rowClicked(this.props.id, true, this.props.newParams)
})
}
}
},
</pre>

'''app/controllers/tree_display_controller.rb'''
- This is the main controller which calls the respective tab upon selection. The 'last_open_tab' holds on the tab clicked under 'Questionnaire'. For every goto_controller call, the tab number sent along in the parameter refers to the respective order of tabs that appear on the homepage.
The changes in the goto_controller will allow the function to keep a track of which tab was last opened by using a new argument i.e. last_open_tab and setting its values to the integer value corresponding to the relative ordering of the tabs on the page . For e.g., if the Questionnaires tab is clicked then a value of 3 will be passed as a parameter since the position of the Questionnaires tab is 3 on the page.
<pre>
def goto_controller(name_parameter, prevTab)
node_object = TreeFolder.find_by(name: name_parameter)
session[:root] = FolderNode.find_by(node_object_id: node_object.id).id
if(prevTab!=nil)
session[:last_open_tab] = prevTab
end
redirect_to controller: 'tree_display', action: 'list', currCtlr: name_parameter
end

def goto_questionnaires
goto_controller('Questionnaires','3')
end
</pre>

==== ScreenCast====

Here is a screencast of the tested functionality after the fix: [https://drive.google.com/open?id=1E2qDwcVvJBi_ybNdIqx6hykDmYVWqu6Y Fixed Issue #1186]

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Description ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== Problem Cause (The grubby details) ====
The problem which we are trying to resolve arises because of the fact that all the rubrics, questionnaires, surveys, etc have been made available for all the instructors to view. Because there was no limitation the code uses the same to code to render lists across the different users. This raises an issue that one instructor can if they want to edit other instructor's surveys when they were only supposed to view them
Currently, if a non-authorized user clicks on edit he is redirected to the same page with an error. A better approach would be to not show the edit button at all and thus we have fixed this user experience.

==== How to reproduce ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

==== Flowchart for correct behavior: ====

[[File:Fc uc2.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx:'''
- This code wait for the page to load and then try to find the user id embedded in the HTML sent from the backend. It then sets this id in a variable available across the app using javascript.
<pre>
let app_variables = {
currentUserId: null
};

window.addEventListener('load', e => {
let treeDisplayDiv = document.querySelector('#tree_display');
if (treeDisplayDiv) {
app_variables.currentUserId = document.querySelector('#tree_display').dataset.userId;
}
});
</pre>

We then pass the instructor's id coming from the API into the Component as props so that it is accessible inside out component for validation.
<pre>
instructor_id={entry.instructor_id}
</pre>

The check which is helping us achieve this is
<pre>
instructor_id={entry.instructor_id}
</pre>

'''app/controllers/controller2:'''
<pre>
(app_variables.currentUserId == null || this.props.instructor_id == app_variables.currentUserId)
</pre>

For API changes 
'''app/controllers/tree_display_controller.rb'''
<pre>
"instructor_id" => child.get_instructor_id,
</pre>

'''app/models/questionnaire_node.rb'''

This function added to the model which simply returns instructor_id associated with that particular questionnaire or survey.
<pre>
def get_instructor_id
Questionnaire.find_by(id: self.node_object_id).try(:instructor_id)
end
</pre>

==Deployment==
This application with the mentioned changes have been deployed to the following URL: [http://152.46.19.166:8080 http://152.46.19.166:8080]
* We have used VCL for deployment.
* Username: instructor6
* Password: password

==Team Members==
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

Mentor: Carmen Bentley (cnaiken@ncsu.edu)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/issues/1186 Issue Number 1186]
#[https://github.com/expertiza/expertiza/issues/696 Issue Number 696]
#[https://reactjs.org/docs/react-component.html ReactJS Documentation]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-29T01:30:32Z

Amanend:

__TOC__

==About Expertiza==

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Description ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded. Currently, the homepage shows 3 tabs: Courses, Assignments and Questionnaires. Suppose a user clicks on the "courses" tab and then from the "Manage Content Tab" -> "Questionnaires", clicks on any of the options, then it will redirect to the same page and not the one which was selected. This needs to be fixed such that upon click, it opens up the corresponding rubric page with that particular rubric section expanded and also the respective tab (courses/assignments/questionnaires) must be highlighted.

==== Problem Cause (The grubby details) ====
The Manage Content page has three tabs in it namely: "Courses","Assignments" and "Questionnaires".
And the application has a feature of storing the 'Last open tab' in its session. Suppose a user was in 'Assignments' tab uner 'Manage Content' Section, and when the user switches to some other tab (By clicking on Home for instance), and comes back on 'Manage Content' section (by clicking on 'Manage...' menu button), he is directed back on the 'Assignments' tab only (the tab that was opened before leaving the 'Manage Content' section).

The problem however, with this feature is that it dominates the natural flow of the application in the following scenario:
Lets say after leaving the 'Manage Content' section as mentioned above, the user clicks 'Manage...>Questionnaires', but even at this point, the user is directed again directed to 'Assignments' tab under 'Manage Content'

==== How to reproduce ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

==== Flowchart for correct behavior====

[[File:Fc issue1.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx'''
- Created "ComponentDidMount" method under this script file which is a react lifecycle function and this is invoked immediately after a component is inserted into the tree. The setState method sets the expanded attribute to true for expanding the relative grid of the rubric. This method will trigger an extra rendering but it will happen before the browser updates the screen. This function will help determine which sub-menu item is selected and expands the corresponding rubric by updating the state of the table row.
<pre>
componentDidMount: function() {
rubBuffer = ["Review", "Metareview", "Author Feedback", "Teammate Review", "Assignment Survey", "Global Survey", "Course Survey"];

selMenuItem = document.getElementById("tree_display").getAttribute("data-menu-item");
selMenuItemInd = rubBuffer.indexOf(selMenuItem);

if(rubBuffer[selMenuItemInd] === this.props.name) {
if (selMenuItemInd !== -1) {
this.setState({
expanded: true
}, function () {
this.props.rowClicked(this.props.id, true, this.props.newParams)
})
}
}
},
</pre>

'''app/controllers/tree_display_controller.rb'''
- This is the main controller which calls the respective tab upon selection. The 'last_open_tab' holds on the tab clicked under 'Questionnaire'. For every goto_controller call, the tab number sent along in the parameter refers to the respective order of tabs that appear on the homepage.
The changes in the goto_controller will allow the function to keep a track of which tab was last opened by using a new argument i.e. last_open_tab and setting its values to the integer value corresponding to the relative ordering of the tabs on the page . For e.g., if the Questionnaires tab is clicked then a value of 3 will be passed as a parameter since the position of the Questionnaires tab is 3 on the page.
<pre>
def goto_controller(name_parameter, prevTab)
node_object = TreeFolder.find_by(name: name_parameter)
session[:root] = FolderNode.find_by(node_object_id: node_object.id).id
if(prevTab!=nil)
session[:last_open_tab] = prevTab
end
redirect_to controller: 'tree_display', action: 'list', currCtlr: name_parameter
end

def goto_questionnaires
goto_controller('Questionnaires','3')
end
</pre>

==== ScreenCast====

Here is a screencast of the tested functionality after the fix: [https://drive.google.com/open?id=1E2qDwcVvJBi_ybNdIqx6hykDmYVWqu6Y Fixed Issue #1186]

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Description ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== How to reproduce ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

==== Flowchart for correct behavior: ====

[[File:Fc uc2.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx:'''
- This code wait for the page to load and then try to find the user id embedded in the HTML sent from the backend. It then sets this id in a variable available across the app using javascript.
<pre>
let app_variables = {
currentUserId: null
};

window.addEventListener('load', e => {
let treeDisplayDiv = document.querySelector('#tree_display');
if (treeDisplayDiv) {
app_variables.currentUserId = document.querySelector('#tree_display').dataset.userId;
}
});
</pre>

We then pass the instructor's id coming from the API into the Component as props so that it is accessible inside out component for validation.
<pre>
instructor_id={entry.instructor_id}
</pre>

The check which is helping us achieve this is
<pre>
instructor_id={entry.instructor_id}
</pre>

'''app/controllers/controller2:'''
<pre>
(app_variables.currentUserId == null || this.props.instructor_id == app_variables.currentUserId)
</pre>

For API changes 
'''app/controllers/tree_display_controller.rb'''
<pre>
"instructor_id" => child.get_instructor_id,
</pre>

'''app/models/questionnaire_node.rb'''

This function added to the model which simply returns instructor_id associated with that particular questionnaire or survey.
<pre>
def get_instructor_id
Questionnaire.find_by(id: self.node_object_id).try(:instructor_id)
end
</pre>

==Deployment==
This application with the mentioned changes have been deployed to the following URL: [http://152.46.19.166:8080 http://152.46.19.166:8080]
* We have used VCL for deployment.

==Team Members==
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

Mentor: Carmen Bentley (cnaiken@ncsu.edu)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/issues/1186 Issue Number 1186]
#[https://github.com/expertiza/expertiza/issues/696 Issue Number 696]
#[https://reactjs.org/docs/react-component.html ReactJS Documentation]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-28T19:39:02Z

Amanend:

__TOC__

==About Expertiza==

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Description ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded. Currently, the homepage shows 3 tabs: Courses, Assignments and Questionnaires. Suppose a user clicks on the "courses" tab and then from the "Manage Content Tab" -> "Questionnaires", clicks on any of the options, then it will redirect to the same page and not the one which was selected. This needs to be fixed such that upon click, it opens up the corresponding rubric page with that particular rubric section expanded and also the respective tab (courses/assignments/questionnaires) must be highlighted.

==== Problem Cause (The grubby details) ====
The Manage Content page has three tabs in it namely: "Courses","Assignments" and "Questionnaires".
And the application has a feature of storing the 'Last open tab' in its session. Suppose a user was in 'Assignments' tab uner 'Manage Content' Section, and when the user switches to some other tab (By clicking on Home for instance), and comes back on 'Manage Content' section (by clicking on 'Manage...' menu button), he is directed back on the 'Assignments' tab only (the tab that was opened before leaving the 'Manage Content' section).

The problem however, with this feature is that it dominates the natural flow of the application in the following scenario:
Lets say after leaving the 'Manage Content' section as mentioned above, the user clicks 'Manage...>Questionnaires', but even at this point, the user is directed again directed to 'Assignments' tab under 'Manage Content'

==== How to reproduce ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

==== Flowchart for correct behavior====

[[File:Fc issue1.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx'''
- Created "ComponentDidMount" method under this script file which is a react lifecycle function and this is invoked immediately after a component is inserted into the tree. The setState method sets the expanded attribute to true for expanding the relative grid of the rubric. This method will trigger an extra rendering but it will happen before the browser updates the screen. This function will help determine which sub-menu item is selected and expands the corresponding rubric by updating the state of the table row.
<pre>
componentDidMount: function() {
rubBuffer = ["Review", "Metareview", "Author Feedback", "Teammate Review", "Assignment Survey", "Global Survey", "Course Survey"];

selMenuItem = document.getElementById("tree_display").getAttribute("data-menu-item");
selMenuItemInd = rubBuffer.indexOf(selMenuItem);

if(rubBuffer[selMenuItemInd] === this.props.name) {
if (selMenuItemInd !== -1) {
this.setState({
expanded: true
}, function () {
this.props.rowClicked(this.props.id, true, this.props.newParams)
})
}
}
},
</pre>

'''app/controllers/tree_display_controller.rb'''
- This is the main controller which calls the respective tab upon selection. The 'last_open_tab' holds on the tab clicked under 'Questionnaire'. For every goto_controller call, the tab number sent along in the parameter refers to the respective order of tabs that appear on the homepage.
The changes in the goto_controller will allow the function to keep a track of which tab was last opened by using a new argument i.e. last_open_tab and setting its values to the integer value corresponding to the relative ordering of the tabs on the page . For e.g., if the Questionnaires tab is clicked then a value of 3 will be passed as a parameter since the position of the Questionnaires tab is 3 on the page.
<pre>
def goto_controller(name_parameter, prevTab)
node_object = TreeFolder.find_by(name: name_parameter)
session[:root] = FolderNode.find_by(node_object_id: node_object.id).id
if(prevTab!=nil)
session[:last_open_tab] = prevTab
end
redirect_to controller: 'tree_display', action: 'list', currCtlr: name_parameter
end

def goto_questionnaires
goto_controller('Questionnaires','3')
end
</pre>

==== ScreenCast====

Here is a screencast of the tested functionality after the fix: [https://drive.google.com/open?id=1IHeW8_ThMVb4Nxkf71XgAYooFQKANX6b Fixed Issue #1186]

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Description ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== How to reproduce ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

==== Flowchart for correct behavior: ====

[[File:Fc uc2.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx:'''
- This code wait for the page to load and then try to find the user id embedded in the HTML sent from the backend. It then sets this id in a variable available across the app using javascript.
<pre>
let app_variables = {
currentUserId: null
};

window.addEventListener('load', e => {
let treeDisplayDiv = document.querySelector('#tree_display');
if (treeDisplayDiv) {
app_variables.currentUserId = document.querySelector('#tree_display').dataset.userId;
}
});
</pre>

We then pass the instructor's id coming from the API into the Component as props so that it is accessible inside out component for validation.
<pre>
instructor_id={entry.instructor_id}
</pre>

The check which is helping us achieve this is
<pre>
instructor_id={entry.instructor_id}
</pre>

'''app/controllers/controller2:'''
<pre>
(app_variables.currentUserId == null || this.props.instructor_id == app_variables.currentUserId)
</pre>

For API changes 
'''app/controllers/tree_display_controller.rb'''
<pre>
"instructor_id" => child.get_instructor_id,
</pre>

'''app/models/questionnaire_node.rb'''

This function added to the model which simply returns instructor_id associated with that particular questionnaire or survey.
<pre>
def get_instructor_id
Questionnaire.find_by(id: self.node_object_id).try(:instructor_id)
end
</pre>

==Deployment==
This application with the mentioned changes have been deployed to the following URL: [http://152.46.19.166:8080 http://152.46.19.166:8080]
* We have used VCL for deployment.

==Team Members==
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

Mentor: Carmen Bentley (cnaiken@ncsu.edu)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/issues/1186 Issue Number 1186]
#[https://github.com/expertiza/expertiza/issues/696 Issue Number 696]
#[https://reactjs.org/docs/react-component.html ReactJS Documentation]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-27T01:47:41Z

Amanend:

__TOC__

==About Expertiza==

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Description ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded.

==== Problem Cause (The grubby details) ====
The Manage Content page has three tabs in it namely: "Courses","Assignments" and "Questionnaires".
And the application has a feature of storing the 'Last open tab' in its session. Suppose a user was in 'Assignments' tab uner 'Manage Content' Section, and when the user switches to some other tab (By clicking on Home for instance), and comes back on 'Manage Content' section (by clicking on 'Manage...' menu button), he is directed back on the 'Assignments' tab only (the tab that was opened before leaving the 'Manage Content' section).

The problem however, with this feature is that it dominates the natural flow of the application in the following scenario:
Lets say after leaving the 'Manage Content' section as mentioned above, the user clicks 'Manage...>Questionnaires', but even at this point, the user is directed again directed to 'Assignments' tab under 'Manage Content'

==== How to reproduce ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

==== Flowchart for correct behavior====

[[File:Fc issue1.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx'''
- ComponentDidMount method is added under this script file which is invoked immediately after a component is inserted into the tree. The setState method sets the expanded attribute to true for expanding the relative grid of the rubric. This method will trigger an extra rendering but it will happen before the browser updates the screen.
<pre>
componentDidMount: function() {
rubBuffer = ["Review", "Metareview", "Author Feedback", "Teammate Review", "Assignment Survey", "Global Survey", "Course Survey"];

selMenuItem = document.getElementById("tree_display").getAttribute("data-menu-item");
selMenuItemInd = rubBuffer.indexOf(selMenuItem);

if(rubBuffer[selMenuItemInd] === this.props.name) {
if (selMenuItemInd !== -1) {
this.setState({
expanded: true
}, function () {
this.props.rowClicked(this.props.id, true, this.props.newParams)
})
}
}
},
</pre>

'''app/controllers/tree_display_controller.rb'''
- This is the main controller which calls the respective tab upon selection. The 'last_open_tab' holds on the tab clicked under 'Questionnaire'. For every goto_controller call, the tab number sent along in the parameter refers to the respective order of tabs that appear on the homepage.
<pre>
def goto_controller(name_parameter, prevTab)
node_object = TreeFolder.find_by(name: name_parameter)
session[:root] = FolderNode.find_by(node_object_id: node_object.id).id
if(prevTab!=nil)
session[:last_open_tab] = prevTab
end
redirect_to controller: 'tree_display', action: 'list', currCtlr: name_parameter
end

def goto_questionnaires
goto_controller('Questionnaires','3')
end
</pre>

==== ScreenCast====

Here is a screencast of the tested functionality after the fix: [https://drive.google.com/open?id=1IHeW8_ThMVb4Nxkf71XgAYooFQKANX6b Fixed Issue #1186]

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Description ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== How to reproduce ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

==== Flowchart for correct behavior: ====

[[File:Fc uc2.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx:'''
- This code wait for the page to load and then try to find the user id embedded in the HTML sent from the backend. It then sets this id in a variable available across the app using javascript.
<pre>
let app_variables = {
currentUserId: null
};

window.addEventListener('load', e => {
let treeDisplayDiv = document.querySelector('#tree_display');
if (treeDisplayDiv) {
app_variables.currentUserId = document.querySelector('#tree_display').dataset.userId;
}
});
</pre>

We then pass the instructor's id coming from the API into the Component as props so that it is accessible inside out component for validation.
<pre>
instructor_id={entry.instructor_id}
</pre>

The check which is helping us achieve this is
<pre>
instructor_id={entry.instructor_id}
</pre>

'''app/controllers/controller2:'''
<pre>
(app_variables.currentUserId == null || this.props.instructor_id == app_variables.currentUserId)
</pre>

For API changes 
'''app/controllers/tree_display_controller.rb'''
<pre>
"instructor_id" => child.get_instructor_id,
</pre>

'''app/models/questionnaire_node.rb'''

This function added to the model which simply returns instructor_id associated with that particular questionnaire or survey.
<pre>
def get_instructor_id
Questionnaire.find_by(id: self.node_object_id).try(:instructor_id)
end
</pre>

==Team Members==
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

Mentor: Carmen Bentley (cnaiken@ncsu.edu)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/issues/1186 Issue Number 1186]
#[https://github.com/expertiza/expertiza/issues/696 Issue Number 696]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-27T01:47:07Z

Amanend:

__TOC__

==About Expertiza==

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Description ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded.

==== Problem Cause (The grubby details) ====
The Manage Content page has three tabs in it namely: "Courses","Assignments" and "Questionnaires".
And the application has a feature of storing the 'Last open tab' in its session. Suppose a user was in 'Assignments' tab uner 'Manage Content' Section, and when the user switches to some other tab (By clicking on Home for instance), and comes back on 'Manage Content' section (by clicking on 'Manage...' menu button), he is directed back on the 'Assignments' tab only (the tab that was opened before leaving the 'Manage Content' section).

The problem however, with this feature is that it dominates the natural flow of the application in the following scenario:
Lets say after leaving the 'Manage Content' section as mentioned above, the user clicks 'Manage...>Questionnaires', but even at this point, the user is directed again directed to 'Assignments' tab under 'Manage Content'

==== How to reproduce ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

==== Flowchart for correct behavior====

[[File:Fc issue1.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx'''
- ComponentDidMount method is added under this script file which is invoked immediately after a component is inserted into the tree. The setState method sets the expanded attribute to true for expanding the relative grid of the rubric. This method will trigger an extra rendering but it will happen before the browser updates the screen.
<pre>
componentDidMount: function() {
rubBuffer = ["Review", "Metareview", "Author Feedback", "Teammate Review", "Assignment Survey", "Global Survey", "Course Survey"];

selMenuItem = document.getElementById("tree_display").getAttribute("data-menu-item");
selMenuItemInd = rubBuffer.indexOf(selMenuItem);

if(rubBuffer[selMenuItemInd] === this.props.name) {
if (selMenuItemInd !== -1) {
this.setState({
expanded: true
}, function () {
this.props.rowClicked(this.props.id, true, this.props.newParams)
})
}
}
},
</pre>

'''app/controllers/tree_display_controller.rb'''
- This is the main controller which calls the respective tab upon selection. The 'last_open_tab' holds on the tab clicked under 'Questionnaire'. For every goto_controller call, the tab number sent along in the parameter refers to the respective order of tabs that appear on the homepage.
<pre>
def goto_controller(name_parameter, prevTab)
node_object = TreeFolder.find_by(name: name_parameter)
session[:root] = FolderNode.find_by(node_object_id: node_object.id).id
if(prevTab!=nil)
session[:last_open_tab] = prevTab
end
redirect_to controller: 'tree_display', action: 'list', currCtlr: name_parameter
end

def goto_questionnaires
goto_controller('Questionnaires','3')
end
</pre>

==== ScreenCast====

Here is a screencast of the tested functionality after the fix: [https://drive.google.com/open?id=1IHeW8_ThMVb4Nxkf71XgAYooFQKANX6b Fixed Issue #1186]

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Details ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== How to reproduce ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

==== Flowchart for correct behavior: ====

[[File:Fc uc2.png]]

====Major Fixes Done ====

'''app/assets/javascripts/tree_display.jsx:'''
- This code wait for the page to load and then try to find the user id embedded in the HTML sent from the backend. It then sets this id in a variable available across the app using javascript.
<pre>
let app_variables = {
currentUserId: null
};

window.addEventListener('load', e => {
let treeDisplayDiv = document.querySelector('#tree_display');
if (treeDisplayDiv) {
app_variables.currentUserId = document.querySelector('#tree_display').dataset.userId;
}
});
</pre>

We then pass the instructor's id coming from the API into the Component as props so that it is accessible inside out component for validation.
<pre>
instructor_id={entry.instructor_id}
</pre>

The check which is helping us achieve this is
<pre>
instructor_id={entry.instructor_id}
</pre>

'''app/controllers/controller2:'''
<pre>
(app_variables.currentUserId == null || this.props.instructor_id == app_variables.currentUserId)
</pre>

For API changes 
'''app/controllers/tree_display_controller.rb'''
<pre>
"instructor_id" => child.get_instructor_id,
</pre>

'''app/models/questionnaire_node.rb'''

This function added to the model which simply returns instructor_id associated with that particular questionnaire or survey.
<pre>
def get_instructor_id
Questionnaire.find_by(id: self.node_object_id).try(:instructor_id)
end
</pre>

==Team Members==
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

Mentor: Carmen Bentley (cnaiken@ncsu.edu)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/issues/1186 Issue Number 1186]
#[https://github.com/expertiza/expertiza/issues/696 Issue Number 696]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-27T00:26:49Z

Amanend:

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-26T17:17:00Z

Amanend: /* Fixes Done */

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-26T17:01:43Z

Amanend:

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-26T16:47:32Z

Amanend:

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-26T16:44:52Z

Amanend:

==E1972. OSS project J. Skellington: Accessing Assignment Rubrics==

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

__TOC__

==About Expertiza==

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Details: ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded.

==== How to reproduce: ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

==== Flowchart for correct behavior: ====

[[File:Fc issue1.png]]

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Details: ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== How to reproduce: ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

==== Flowchart for correct behavior: ====

[[File:Fc uc2.png]]

==Team Members==
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/issues/1186 Issue Number 1186]
#[https://github.com/expertiza/expertiza/issues/696 Issue Number 696]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-26T16:39:51Z

Amanend:

==E1972. OSS project J. Skellington: Accessing Assignment Rubrics==

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

__TOC__

===Team Members===
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Details: ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded.

==== How to reproduce: ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

==== Flowchart for correct behavior: ====

[[File:Fc issue1.png]]

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Details: ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== How to reproduce: ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

==== Flowchart for correct behavior: ====

[[File:Fc uc2.png]]

===References===

#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/issues/1186 Issue Number 1186]
#[https://github.com/expertiza/expertiza/issues/696 Issue Number 696]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-26T16:29:34Z

Amanend: /* Problem Statement */

File:Fc uc2.png

2019-10-26T16:28:06Z

Amanend:

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-26T15:59:39Z

Amanend: /* Problem Statement */

File:Fc issue1.png

2019-10-26T15:58:30Z

Amanend: uploaded a new version of "File:Fc issue1.png"

File:Fc issue1.png

2019-10-26T15:57:31Z

Amanend:

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-23T03:47:09Z

Amanend:

==E1972. OSS project J. Skellington: Accessing Assignment Rubrics==

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

__TOC__

===Team Members===
Ankit Manendra (amanend@ncsu.edu)

Bharat Sinha (bsinha2@ncsu.edu)

Gurman Singh (gsingh23@ncsu.edu )

===About Expertiza===

[http://expertiza.ncsu.edu/ Expertiza] is an open source project based on [http://rubyonrails.org/ Ruby on Rails] framework. Expertiza allows the instructor to create new assignments and customize new or existing assignments. It also allows the instructor to create a list of topics the students can sign up for. Students can form teams in Expertiza to work on various projects and assignments. Students can also peer review other students' submissions. Expertiza supports submission across various document types, including the URLs and wiki pages.

== Problem Statement ==

=== Task 1 : Inappropriate redirection when Managing Questionnaire types ===

==== Details: ====
Each of the options for Manage>Questionnaires> does not appropriately link you to the Questionnaires tab with that section of Questionnaires expanded.

==== How to reproduce: ====
If you are on the assignment tab and select to Manage…>Questionnaires> [some option], this will send you to the assignment tab. It is believed that the redirect will always send you to the view that was previously displayed. Change the tab to course or questionnaire and then it just sends you to that tab instead.

=== Task 2: Instructors can make changes to each others’ rubrics ===

==== Details: ====
Currently, rubric lists show all public rubrics and there is no option to restrict the view as in assignments and courses. This should be fixed by only displaying the option to edit (pencil) when the rubric belongs to the user. This clearly indicates that the user has the ability or not to edit this rubric.

==== How to reproduce: ====
Log in and Manage…>Questionnaires>Rubrics. Then click on one of the rubric types to show a list of rubrics and click through the edit options to reveal the flash error when you try and edit a rubric that is not yours.

CSC/ECE 517 Fall 2019

2019-10-23T02:13:38Z

Amanend:

* [[CSC/ECE 517 Fall 2019 - Project E1947. Refactor quiz_questionnaire_controller.rb]]
* [[CSC/ECE 517 Fall 2019 - Project E1965. Review report should link to the usual view for reviews]]
* [[CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics]]

CSC/ECE 517 Fall 2019 - E1972. OSS project J. Skellington: Accessing Assignment Rubrics

2019-10-23T02:00:41Z

Amanend: Created page with "==E1972. OSS project J. Skellington: Accessing Assignment Rubrics== This page provides a description of the Expertiza based OSS project. __TOC__ ===Team Members=== Ankit Man..."