Expertiza_Wiki - User contributions [en]

MainPage

2018-02-28T15:17:39Z

Ralwan:

==Expertiza==
* [[Expertiza documentation]]

==Course-Specific Topics==

* [[CSC/ECE 517 Summer 2008]]
* [[CSC/ECE 517 Fall 2010]]
* [[CSC/ECE 517 Fall 2011]]
* [[CSC/ECE 517 Fall 2012]]
* [[CSC/ECE 517 Fall 2013]]
* [[CSC/ECE 517 Fall 2014]]
* [[CSC/ECE 517 Fall 2015]]
* [[CSC/ECE 517 Fall 2016]]
* [[CSC/ECE 517 Spring 2014]]
* [[CSC/ECE 517 Spring 2015]]
* [[CSC/ECE 517 Spring 2016]]
* [[CSC/ECE 517 Spring 2017]]
* [[CSC/ECE 517 Fall 2017]]
* [[CSC 456 Spring 2011|CSC 456 Spring 2012]]
* [[ECE 633]]
* [[KCU]]
* [[Progress reports]]

==Application Behavior==
* [[Grading]]

==Metaprogramming==
* [[CSC/ECE_517_Spring_2013/ch1b_1k_hf|Lecture on Metaprogramming]]

==Development==

''Expertiza now has a Java dependency, so the machine you are using to develop Expertiza on should have the JVM installed.''

* [[Setting Up a Development Machine]]
* [[Creating a Linux Development Environment for Expertiza - Installation Guide]]
* [[Using git and github for projects]]
* [[Using heroku to deploy your projects]]
* [[How to Begin a Project from the Current Expertiza Repository]]
* [[Git]]
* [[How to Change a User's Password on a Development Machine]]
* [[Debugging Rails]]
* [http://rajanalwan.com/ui_guidelines/ Design Template]

==Production==
* [[Deploying to Production]]
* [[Downloading Production Data]]
* [[Accessing the Production Server]]

==Testing==
* [[Using Cucumber with Expertiza]]
* [[Rails Testing Overview]]
* [[Expertiza Continuous Integration]]

==References==
* [[Object-Oriented Design and Programming]]

Expertiza documentation

2018-02-28T15:17:01Z

Ralwan:

[[Image:715px-EXPERTIZA.png|715px]]

= Welcome to the Expertiza project! =

The Expertiza project is software to create reusable learning objects through peer review. It also supports team projects, and the submission of almost any document type, including URLs and wiki pages.

== Short Powerpoint introductions ==
*My [http://research.csc.ncsu.edu/efg/expertiza/presentations/ELI_11_wiki_textbook.ppt presentation] on using Expertiza to support wiki-textbook creation, at the 2011 EDUCAUSE Learning Initiative conference, February 15, 2011
*My [http://research.csc.ncsu.edu/efg/expertiza/presentations/Purdue_TLT_2009.ppt plenary talk] at the Purdue TLT Conference on April 22, 2009
*We invite you to view the original [http://research.csc.ncsu.edu/efg/expertiza/presentations/Expertiza-short.htm rationale] for the system.
*You can walk through a [http://research.csc.ncsu.edu/efg/expertiza/presentations/Expertiza%20in%20Action.ppt virtual demo] of the system.

== Papers ==
*A [http://innovateonline.info/index.php?view=article&id=365 prose rendition] of the rationale was published in [http://innovateonline.info/ Innovate] in 2007. (To view it, you need to register, and you will receive e-mail each time a new issue of this very interesting and useful journal is published.)
*Other papers on Expertiza can be found [http://research.csc.ncsu.edu/efg/expertiza/papers/ here].

== Video presentations ==

*An [http://connectpro86502729.na6.acrobat.com/p99048610/ overview] of Expertiza ("Software support for teamwork and authentic assessment [http://research.csc.ncsu.edu/efg/expertiza/presentations/TLT_Live.ppt (slides)]") from the TLT Group's Friday Live, September 24, 2010
*[https://sas.elluminate.com/site/external/recording/playback/link/dropin.jnlp?sid=2008350&suid=D.2D2E269EE524FD263F89DA6872A41E Student-authored wiki textbooks: Composition and review] from the 2011 Global Education Consortium, November 18, 2011
*This [http://educause.mediasite.com/mediasite/SilverlightPlayer/Default.aspx?peid=cdeebca6d1a34610923bcabd4c2d2fd91d session from EDUCAUSE ELI 2011] describes how Expertiza can be used to review wiki-textbook contributions. It is an earlier version of the presentation above that includes a live demo.
*This Innovate [http://breeze.uliveandlearn.com/p10263667/ Webcast] from July 2007 includes the rationale and a demo of the system.
*A six-minute [http://www.youtube.com/watch?v=hVpS7qvC5Zs interview] from the 2009 Lilly Conference on College Teaching describes the goals and realization of the project. (Note: Background noise may be distracting.)
*This Innovate [http://breeze.uliveandlearn.com/p84785847/ Ideagora] discussion from January 2009 describes the social-networking features planned for Expertiza.
*[https://sas.elluminate.com/site/external/jwsdetect/playback.jnlp?psid=2009-03-17.1032.M.F13AAE88367AEE982449E713075D42.vcr Forming and managing student teams and peer feedback in Expertiza], a presentation at the UNC TLT conference in March 2009.

== Documentation ==

*An [http://research.csc.ncsu.edu/efg/expertiza/reports/Instructor_documentation.doc instructor manual], explaining how to create an deploy an assignment in Expertiza.
*An [http://research.csc.ncsu.edu/efg/expertiza/presentations/videos/instructor.swf instructor video], slightly dated, showing how to create and deploy an assignment
*A [http://rajanalwan.com/ui_guidelines/ design document] for the application.
* A guide for [[Creating_Custom_Rubric]]
*For students, a [http://research.csc.ncsu.edu/efg/expertiza/presentations/student_documentation.ppt Powerpoint] or [http://research.csc.ncsu.edu/efg/expertiza/presentations/student_documentation.pdf PDF] presentation explaining how to submit and review an assignment with Expertiza.
*For students, a [http://research.csc.ncsu.edu/efg/expertiza/presentations/videos/student.swf video] showing how to use the system to submit and review an assignment.
*For students, a [http://research.csc.ncsu.edu/efg/expertiza/presentations/student_wiki_documentation.ppt Powerpoint] or [http://research.csc.ncsu.edu/efg/expertiza/presentations/student_wiki_documentation.pdf PDF] presentation explaining how to submit and review wiki pages with Expertiza.
*For students, a [http://courses.ncsu.edu/csc517/common/homework/topic-signup-team-formation.ppt Powerpoint] or [http://courses.ncsu.edu/csc517/common/homework/topic-signup-team-formation.pdf PDF] presentation explaining how to form teams and sign up for topics.

== Developers section ==
''Expertiza now has a Java dependency, so the machine you are using to develop Expertiza on should have the JVM installed.''
=== Development Environment Setup Guides ===
* [[Creating a Linux Development Environment for Expertiza - Installation Guide]]
**[http://wiki.expertiza.ncsu.edu/index.php/Development:Setup:Linux:Debian Development setup for Ubuntu/Debian]
* [[Development:Setup:OSX]]
*[http://wiki.expertiza.ncsu.edu/index.php/Development:Setup:Linux:RHEL Development setup for Linux RHEL ]
*[[Developing Expertiza on the VCL]]
*Developing Expertiza on Virtual Box
** [https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uEUmNKVncxRUhUVVE/view?usp=sharing Download the VirtualBox Ubuntu image here]
** [https://drive.google.com/open?id=1YlqiSsbZl8TfPuQmIFG7TYo2npWzqqu4 or try the Lubuntu image here if the Ubuntu image is too heavy for your PC/Laptop ]
*Docker image (Only if you are familiar with docker. You will need it if you choose Expertiza to do OSS project.)
** Please follow the instruction in https://hub.docker.com/r/winbobob/expertiza-fall2016/

=== Database Guides ===
*[[Deploying and importing production data with capistrano]]
*[[Documentation on Database Tables]]
=== Git ===
*[[Version Control with the Git repository]]
*[http://wiki.expertiza.ncsu.edu/index.php/How_to_Begin_a_Project_from_the_Current_Expertiza_Repository How to Begin a Project from the Current Expertiza Repository]

=== Ruby and Rails ===
*[[Restart Instructions for Expertiza]]
*[[Deploying Expertiza to Production]]
*[[Gem dependencies]]
*[[http://wiki.expertiza.ncsu.edu/index.php?title=Using_Cucumber_with_Expertiza Using Cucumber with Expertiza]]

=== Misc ===
*[[Setting up and using TA functionality]]
*[[Restart instructions for Wiki]]

=== Final Projects on Expertiza for Fall 2015 ===
[https://docs.google.com/document/d/1t0keeNQ2kP0NmcgIrtQXGi5K_GhQYcKzEVWJPPRBOHE/edit?pli=1 The Expertiza Final Project Submission] 

== Links ==
[http://expertiza.ncsu.edu The Expertiza application] 
[http://research.csc.ncsu.edu/efg/expertiza/papers Papers on Expertiza] 
[http://research.csc.ncsu.edu/efg/expertiza/presentations/Expertiza-short.htm PowerPoint Presentation - The Expertiza platform] 
[http://www.csc.ncsu.edu/news/463 Expertiza Platform Takes Honorable Mention in Gertrude Cox Awards]

== Acknowledgments ==

This material is based upon work supported by the National Science Foundation under Grant No. 0536558. Additional funding from the NCSU Learning in a Technology-Rich Environment (LITRE) program, the NCSU Faculty Center for Teaching and Learning, the NCSU STEM Initiative, and the Center for Advanced Computing and Communication.

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-12-08T15:48:59Z

Ralwan: /* Test Plan */

= Purpose =
The implementation of a badging system provides a boosted visual motivation for the students to work towards achieving that badge. This has the ability to improve the overall class performance.

Team: Ankit Jain

Rajan Alwan

Riken Shah

Sanya Kathuria

Mentor - Zhewei Hu,(zhu6@ncsu.edu)

= Problem Statement =
The aim of this project is to implement a badging system for Expertiza where certain students are awarded badges when certain criteria are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Flowchart Of the System =

[[File:UMLDiagram1.png]]

= Description of the Badges =

=== Why develop Badge-System? ===

The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for an assignment.

=== What does the badge-system do? ===
We have developed two badges — "Good Reviewer" and "Good Teammate" but the design has been developed in such a way that the badging system can be easily extended to include more badges in the future.
The "Good Reviewer" badge will be awarded to students who receive very high review grades. The "Good Teammate" badge will be awarded to team members who receive very high teammate review scores. By default, the "threshold" for earning these badges is set to a score of 95, but this value is configurable on a per-assignment basis by the instructor.
A new "Badges" tab will be added for instructors on the "Edit Assignment" page where instructors can add badges and configure the badge criteria for a given assignment. Badges a student has earned can be seen when they view their "Task List" page, and an instructor will be able to view all badges earned by students when they view the "Participants List" page.

=== What are the badges and Who will be awarded?===

==== '''Good Reviewer''' ====
===== Icon =====

[[File:goodReviewer2.png]]

===== Who will be Awarded =====
“Good reviewer” is the badge that one student receives very high review grades assigned by teaching staff (by default 95).

==== '''Good Teammate ====
===== Icon =====

[[File:goodTeammate.png]]

===== Who will be Awarded =====
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receives very high teammate review scores (by default 95).

== '''How do we make badges configurable?''' ==
The criterion to assign badge should be configurable. After creating a new assignment, the threshold for the badges can be specified in assignments/edit page.
The below image shows the how the page looks like.

[[File:PR1.PNG]]

= Modified Files =

=== Tables to be Modified ===

# We have created a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We have created a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We have created a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key

=== Files to be Modified ===
# We have inserted the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We have inserted the new code related to “Good Reviewer” badge to review_response_map.rb
# We have added badges to student_task/list page and a new column named Badge.
# We have added badges to participants/list for the instructor to view.
# We have added a tab to edit the badge attributes on the assignments#edit page.

= How does it look like? =

=== Rationale behind the implementation : ===
1. As per requirement, the badges need to be displayed in the list view for both instructors and students. And thus, the list.html.erb has been chosen as the views to be modified.

2. The controllers student_task_controller.rb and participants_controller.rb are invoking the views as shown below. Thus, this list method in both the controllers need to be refactored to figure out what badges the team or an individual student needs to be awarded.

3. All business logic regarding badge assignment criteria will be put in teammate_review_response_map.rb and review_response_map.rb created for “Good teammate” and “Good reviewer” badge respectively.

=== When only one Badge is assigned : ===

[[File:PR2.PNG]]

=== Assigning both the badges together : ===

[[File:PR3.PNG]]

= Test Plan =
We have developed the project using the TDD methodology. We have thoroughly tested all the functionalities we have implemented by writing automated test cases in features/specs/badge_system_spec.rb file in Expertiza.

The following are the testing scenarios and how we went along implementing them:

# The assignments#edit page has a tab named badges.
## We login using instructor6
## Visit the assignments#edit page
## Try to click the Badges tab

# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
## The badges tab is entered
## The input field for Good Reviewer Threshold is filled with 96 from 95
## The input field for Good Teammate Threshold is filled with 97 from 95
## Check whether these values reflect in the database

# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default).
## We change to student display
## Obtain teammate review score from the AwardedBadge model's get_teammate_review_score method that we defined
## Obtain threshold for that assignment
## If the threshold is lower, we expect to see a Good Teammate badge on the page

# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
## We change to student display
## Obtain review score from the ReviewGrade model's grade_for_reviewer attribute
## Obtain threshold for that assignment
## If the threshold is lower, we expect to see a Good Reviewer badge on the page

# Instructor can view all badges assigned to all participants.
## Login as instructor6
## Visit the participants#list page
## Expect to see the badges column in the page

[[File:PR4.PNG]]

[[File:PR5.PNG]]

[[File:PR6.PNG]]

'''Command to run the testcase file :'''
rspec badge_system_spec.rb

= Other References =

See the screencast at https://youtu.be/WtPns8mG2K8.

Pull request is available from https://github.com/rikenshah/expertiza.

= Future Improvements =
Currently, the average score of all the reviews for each assignment is computed dynamically and not stored anywhere in the database. This incurs huge latency in loading the pages which query the score. This is the reason why "Review Score" page from instructor view takes a long time to load.

For the topper badge, we need to query the average score of all the teams for all the assignments in a particular course and decide whether the current user is the member of the team having the highest score in any of these assignments. This involves a large number of computations and increases the home page load time of student view by an unacceptably large margin. Currently, a project is underway to fix this problem by storing the scores of teams in the database. Once this task is completed, we can refactor our Top Score method to take advantage of this change. This will significantly reduce the latency of the Top Score badge for both student and Instructor view.

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-12-08T14:58:15Z

Ralwan:

= Purpose =
The implementation of a badging system provides a boosted visual motivation for the students to work towards achieving that badge. This has the ability to improve the overall class performance.

Team: Ankit Jain

Rajan Alwan

Riken Shah

Sanya Kathuria

Mentor - Zhewei Hu,(zhu6@ncsu.edu)

= Problem Statement =
The aim of this project is to implement a badging system for Expertiza where certain students are awarded badges when certain criteria are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Flowchart Of the System =

[[File:UMLDiagram1.png]]

= Description of the Badges =

=== Why develop Badge-System? ===

The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for an assignment.

=== What does the badge-system do? ===
We have developed two badges — "Good Reviewer" and "Good Teammate" but the design has been developed in such a way that the badging system can be easily extended to include more badges in the future.
The "Good Reviewer" badge will be awarded to students who receive very high review grades. The "Good Teammate" badge will be awarded to team members who receive very high teammate review scores. By default, the "threshold" for earning these badges is set to a score of 95, but this value is configurable on a per-assignment basis by the instructor.
A new "Badges" tab will be added for instructors on the "Edit Assignment" page where instructors can add badges and configure the badge criteria for a given assignment. Badges a student has earned can be seen when they view their "Task List" page, and an instructor will be able to view all badges earned by students when they view the "Participants List" page.

=== What are the badges and Who will be awarded?===

==== '''Good Reviewer''' ====
===== Icon =====

[[File:goodReviewer2.png]]

===== Who will be Awarded =====
“Good reviewer” is the badge that one student receives very high review grades assigned by teaching staff (by default 95).

==== '''Good Teammate ====
===== Icon =====

[[File:goodTeammate.png]]

===== Who will be Awarded =====
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receives very high teammate review scores (by default 95).

== '''How do we make badges configurable?''' ==
The criterion to assign badge should be configurable. After creating a new assignment, the threshold for the badges can be specified in assignments/edit page.
The below image shows the how the page looks like.

[[File:PR1.PNG]]

= Modified Files =

=== Tables to be Modified ===

# We have created a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We have created a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We have created a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key

=== Files to be Modified ===
# We have inserted the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We have inserted the new code related to “Good Reviewer” badge to review_response_map.rb
# We have added badges to student_task/list page and a new column named Badge.
# We have added badges to participants/list for the instructor to view.
# We have added a tab to edit the badge attributes on the assignments#edit page.

= How does it look like? =

=== Rationale behind the implementation : ===
1. As per requirement, the badges need to be displayed in the list view for both instructors and students. And thus, the list.html.erb has been chosen as the views to be modified.

2. The controllers student_task_controller.rb and participants_controller.rb are invoking the views as shown below. Thus, this list method in both the controllers need to be refactored to figure out what badges the team or an individual student needs to be awarded.

3. All business logic regarding badge assignment criteria will be put in teammate_review_response_map.rb and review_response_map.rb created for “Good teammate” and “Good reviewer” badge respectively.

=== When only one Badge is assigned : ===

[[File:PR2.PNG]]

=== Assigning both the badges together : ===

[[File:PR3.PNG]]

= Test Plan =
We have developed the project using the TDD methodology. We have thoroughly tested all the functionalities we have implemented by writing automated test cases in features/specs/badge_system_spec.rb file in Expertiza.

To start off, we have tested the following scenarios:

# The assignments#edit page has a tab named badges.
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default).
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

[[File:PR4.PNG]]

[[File:PR5.PNG]]

[[File:PR6.PNG]]

'''Command to run the testcase file :'''
rspec badge_system_spec.rb

= Other References =

See the screencast at https://youtu.be/WtPns8mG2K8.

Pull request is available from https://github.com/rikenshah/expertiza.

= Future Improvements =
Currently, the average score of all the reviews for each assignment is computed dynamically and not stored anywhere in the database. This incurs huge latency in loading the pages which query the score. This is the reason why "Review Score" page from instructor view takes a long time to load.

For the topper badge, we need to query the average score of all the teams for all the assignments in a particular course and decide whether the current user is the member of the team having the highest score in any of these assignments. This involves a large number of computations and increases the home page load time of student view by an unacceptably large margin. Currently, a project is underway to fix this problem by storing the scores of teams in the database. Once this task is completed, we can refactor our Top Score method to take advantage of this change. This will significantly reduce the latency of the Top Score badge for both student and Instructor view.

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-15T14:16:55Z

Ralwan: /* Use Case Diagram */

= Purpose =
The implementation of a badging system provides a boosted visual motivation for the students to work towards achieving that badge. This has the ability to improve the overall class performance.

= Problem Statement =
The aim of this project is to implement a badging system for expertiza where certain students are awarded with badges when certain criterias are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Use Case Diagram =

[[File:UMLDiagram1.png]]

= Description of the Badges =
The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for a assignment. The badges we are going to build are as follows,

== '''Good Reviewer''' ==
[[File:goodReviewer2.png]]

=== Who will be Awarded ===
“Good reviewer” is the badge that one student receive very high review grades assigned by teaching staff (by default 95).

== '''Good Teammate ==
[[File:goodTeammate.png]]

=== Who will be Awarded ===
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receive very high teammate review scores (by default 95).

= Modified Files =

=== Tables to be Modified ===

# We’ll be creating a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We’ll be creating a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We’ll be creating a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key

=== Files to be Modified ===
# We’ll be inserting the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We’ll be inserting the new code related to “Good Reviewer” badge to review_response_map.rb
# We’ll be adding badges to student_task/list page and a new column named Badge.
# We’ll be adding badges to participants/list for instructor to view.
# We’ll be adding a tab to edit the badge attributes in the assignments#edit page.

= Test Plan =
The project is going to be developed using the TDD methodology. To start off, we’ll be testing the following scenarios:

# The assignments#edit page has a tab named badges
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default)
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

File:UMLDiagram1.png

2017-11-15T14:16:44Z

Ralwan:

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-15T14:09:30Z

Ralwan:

= Purpose =
The implementation of a badging system provides a boosted visual motivation for the students to work towards achieving that badge. This has the ability to improve the overall class performance.

= Problem Statement =
The aim of this project is to implement a badging system for expertiza where certain students are awarded with badges when certain criterias are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Use Case Diagram =

[[File:UMLDiagram.png]]

= Description of the Badges =
The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for a assignment. The badges we are going to build are as follows,

== '''Good Reviewer''' ==
[[File:goodReviewer2.png]]

=== Who will be Awarded ===
“Good reviewer” is the badge that one student receive very high review grades assigned by teaching staff (by default 95).

== '''Good Teammate ==
[[File:goodTeammate.png]]

=== Who will be Awarded ===
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receive very high teammate review scores (by default 95).

= Modified Files =

=== Tables to be Modified ===

# We’ll be creating a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We’ll be creating a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We’ll be creating a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key

=== Files to be Modified ===
# We’ll be inserting the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We’ll be inserting the new code related to “Good Reviewer” badge to review_response_map.rb
# We’ll be adding badges to student_task/list page and a new column named Badge.
# We’ll be adding badges to participants/list for instructor to view.
# We’ll be adding a tab to edit the badge attributes in the assignments#edit page.

= Test Plan =
The project is going to be developed using the TDD methodology. To start off, we’ll be testing the following scenarios:

# The assignments#edit page has a tab named badges
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default)
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

File:UMLDiagram.png

2017-11-15T14:09:11Z

Ralwan:

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-15T14:08:50Z

Ralwan:

= Purpose =
The implementation of a badging system provides a boosted visual motivation for the students to work towards achieving that badge. This has the ability to improve the overall class performance.

= Problem Statement =
The aim of this project is to implement a badging system for expertiza where certain students are awarded with badges when certain criterias are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Use Case Diagram =

[[File:goodReviewer2.png]]

= Description of the Badges =
The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for a assignment. The badges we are going to build are as follows,

== '''Good Reviewer''' ==
[[File:goodReviewer2.png]]

=== Who will be Awarded ===
“Good reviewer” is the badge that one student receive very high review grades assigned by teaching staff (by default 95).

== '''Good Teammate ==
[[File:goodTeammate.png]]

=== Who will be Awarded ===
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receive very high teammate review scores (by default 95).

= Modified Files =

=== Tables to be Modified ===

# We’ll be creating a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We’ll be creating a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We’ll be creating a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key

=== Files to be Modified ===
# We’ll be inserting the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We’ll be inserting the new code related to “Good Reviewer” badge to review_response_map.rb
# We’ll be adding badges to student_task/list page and a new column named Badge.
# We’ll be adding badges to participants/list for instructor to view.
# We’ll be adding a tab to edit the badge attributes in the assignments#edit page.

= Test Plan =
The project is going to be developed using the TDD methodology. To start off, we’ll be testing the following scenarios:

# The assignments#edit page has a tab named badges
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default)
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-08T03:11:43Z

Ralwan:

= Problem Statement =
The aim of this project is to implement a badging system for expertiza where certain students are awarded with badges when certain criterias are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Description of the Badges =
The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for a assignment. The badges we are going to build are as follows,

== '''Good Reviewer''' ==
[[File:goodReviewer2.png]]

=== Who will be Awarded ===
“Good reviewer” is the badge that one student receive very high review grades assigned by teaching staff (by default 95).

== '''Good Teammate ==
[[File:goodTeammate.png]]

=== Who will be Awarded ===
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receive very high teammate review scores (by default 95).

= Modified Files =

=== Tables to be Modified ===

# We’ll be creating a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We’ll be creating a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We’ll be creating a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key

=== Files to be Modified ===
# We’ll be inserting the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We’ll be inserting the new code related to “Good Reviewer” badge to review_response_map.rb
# We’ll be adding badges to student_task/list page and a new column named Badge.
# We’ll be adding badges to participants/list for instructor to view.
# We’ll be adding a tab to edit the badge attributes in the assignments#edit page.

= Test Plan =
The project is going to be developed using the TDD methodology. To start off, we’ll be testing the following scenarios:

# The assignments#edit page has a tab named badges
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default)
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

File:GoodTeammate.png

2017-11-08T03:10:22Z

Ralwan:

File:GoodReviewer2.png

2017-11-08T03:10:01Z

Ralwan:

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-08T03:06:49Z

Ralwan:

= Problem Statement =
The aim of this project is to implement a badging system for expertiza where certain students are awarded with badges when certain criterias are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Description of the Badges =
The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for a assignment. The badges we are going to build are as follows,

== '''Good Reviewer''' ==

=== Who will be Awarded ===
“Good reviewer” is the badge that one student receive very high review grades assigned by teaching staff (by default 95).

== '''Good Teammate ==
=== Who will be Awarded ===
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receive very high teammate review scores (by default 95).

= Modified Files =

=== Tables to be Modified ===

# We’ll be creating a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We’ll be creating a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We’ll be creating a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key

=== Files to be Modified ===
# We’ll be inserting the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We’ll be inserting the new code related to “Good Reviewer” badge to review_response_map.rb
# We’ll be adding badges to student_task/list page and a new column named Badge.
# We’ll be adding badges to participants/list for instructor to view.
# We’ll be adding a tab to edit the badge attributes in the assignments#edit page.

= Test Plan =
The project is going to be developed using the TDD methodology. To start off, we’ll be testing the following scenarios:

# The assignments#edit page has a tab named badges
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default)
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-08T03:06:33Z

Ralwan:

= Problem Statement =
The aim of this project is to implement a badging system for expertiza where certain students are awarded with badges when certain criterias are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Description of the Badges =
The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for a assignment. The badges we are going to build are as follows,

== '''Good Reviewer''' ==

=== Who will be Awarded ===
“Good reviewer” is the badge that one student receive very high review grades assigned by teaching staff (by default 95).

== '''Good Teammate ==
=== Who will be Awarded ===
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receive very high teammate review scores (by default 95).

= Modified Files =

=== Tables to be Modified ===

# We’ll be creating a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We’ll be creating a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We’ll be creating a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key
=== FILES TO BE MODIFIED ===
# We’ll be inserting the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We’ll be inserting the new code related to “Good Reviewer” badge to review_response_map.rb
# We’ll be adding badges to student_task/list page and a new column named Badge.
# We’ll be adding badges to participants/list for instructor to view.
# We’ll be adding a tab to edit the badge attributes in the assignments#edit page.

= Test Plan =
The project is going to be developed using the TDD methodology. To start off, we’ll be testing the following scenarios:

# The assignments#edit page has a tab named badges
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default)
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-08T03:06:03Z

Ralwan:

= Problem Statement =
The aim of this project is to implement a badging system for expertiza where certain students are awarded with badges when certain criterias are met which may include exceptional academic performance in assignments, project submissions etc. We will be using Credly to make Badges. We will be working on building two badges:

# Good Reviewer
# Good Teammate

= Description of the Badges =
The use of badges will encourage students to have a visual motivation based on their achievements and thus perform better. For every assignment in Expertiza, we have students perform differently on a scale of 100 based on the reviews their projects receive from their peers. The topper badges will be used to honor the team(s) which scores the maximum for a assignment. The badges we are going to build are as follows,

== '''Good Reviewer''' ==

=== Who will be Awarded ===
“Good reviewer” is the badge that one student receive very high review grades assigned by teaching staff (by default 95).

== '''Good Teammate ==
=== Who will be Awarded ===
In Expertiza students are required to give reviews to the work of other teams. This is evaluated on a scale of 100% by the teaching staff. “Good teammate” is the badge that each team member receive very high teammate review scores (by default 95).

= MODIFIED FILES =

=== TABLES TO BE MODIFIED ===

# We’ll be creating a table named “badges”, with the following attributes:
## id: primary key
## name: varchar
## description: varchar
# We’ll be creating a mapping table named “assignment_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## assignment_id: foreign key
## threshold: int
# We’ll be creating a mapping table named “awarded_badges”, with the following attributes:
## id: primary key
## badge_id: foreign key
## participant_id: foreign key
=== FILES TO BE MODIFIED ===
# We’ll be inserting the new code related to “Good Teammate” badge to teammate_review_response_map.rb.
# We’ll be inserting the new code related to “Good Reviewer” badge to review_response_map.rb
# We’ll be adding badges to student_task/list page and a new column named Badge.
# We’ll be adding badges to participants/list for instructor to view.
# We’ll be adding a tab to edit the badge attributes in the assignments#edit page.

= Test Plan =
The project is going to be developed using the TDD methodology. To start off, we’ll be testing the following scenarios:

# The assignments#edit page has a tab named badges
# In the badges tab, allow the instructor to change the threshold value of the badges, above which the badges will be awarded to the students.
# Assign the “Good Teammate” badge to a student when the student receives a very high average teammate review grade (higher than 95 by default)
# Assign the “Good Reviewer” badge to a student when the student receives a very high review grades assigned by teaching staff (higher than 95 by default).
# Instructor can view all badges assigned to all participants.

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-08T02:42:22Z

Ralwan: /* Problem Statement */

CSC/ECE 517 Fall 2017/E17A2. Lightweight badging system based on Credly

2017-11-08T02:42:10Z

Ralwan:

CSC/CSC 517 Fall 2017/ProjectPurple

2017-11-02T23:10:49Z

Ralwan:

== E1778 OSS project Purple: UI fixes for assignment creation ==

This page provides the documentation of the UI fixes for assignment creation in Expertiza.

===Problem Statement===
Expertiza allows the instructor to enable and disable different features to be used in an assignment. Some of these setting e.g., allow peer review to be done in iterations, allow third party to assess the quality of the peer feedback, can be changed from manage>assignment and click on edit icon. Some of the UI to enable and disable these features were broken and the aim of this project was to fix the following issues.

The following issues were fixed in this project:
* Issue [https://github.com/expertiza/expertiza/issues/972 #972]: While editing an assignment, changing the number of review rounds doesn't work in Expertiza.
* Issue [https://github.com/expertiza/expertiza/issues/961 #961]: Once an assignment is duplicated from another assignment with metareview enabled, metareview deadline cannot be disabled.

* Issue [https://github.com/expertiza/expertiza/issues/295 #295]: was already fixed before the start of this project.

===Issue Fix===
A working demo of the fixed issues can be found [https://youtu.be/ysVeHlrlKo8 here]. The changed code can be found in the pull request made [https://github.com/expertiza/expertiza/pull/1033 here].

The first two actions of enabling and disabling metareviews show the fixed issue #961. The action of reducing the rounds of reviews shows our fix to issue #972.

====Issue [https://github.com/expertiza/expertiza/issues/972 #972]====
=====Initial Approach=====
The main problem as stated in the problem statement is that .last() does not exist for the array. This method was used to identify the last element in the array of elements. This was solved by identifying the last element as the (array.length - 1)th element of the array.

=====Actual problem=====
The issue was the instructor was not able to change the rounds of reviews for an assignment. The reason for this issue was found to be the actual rounds of reviews was overridden by the maximum of submissions and review count in the database. This constraint was introduced to restrict the instructor from resetting the rounds of reviews lesser than the submissions count. The constraint was not necessary for some scenarios which should have allowed the instructor to reset.

=====Solution=====

To solve this scenario, we introduced a warning message with a confirmation option to allow the instructor to override the rounds of reviews.

=====Intuition behind fix=====

After realizing the actual location of the code that was causing the bug, we realized that assuming the current rounds of reviews by the maximum amongst the submissions count, reviews count, and the rounds of reviews led to a scenario where even when the instructor wanted to update the rounds of reviews, he wasn't allowed to do so. This was a problem because, there would have been a certain situation where the instructor had to override the existing value because of a previous error (maybe even typographical). Thus, a confirmation message with a warning was the way to go.

====Issue [https://github.com/expertiza/expertiza/issues/961 #961]====
=====Problem=====

The problem was the need for metareview could not be disabled while editing an assignment. This was because the DueDate table was not updated with the necessary cascade actions.

=====Solution=====

This issue was solved by implementing the cascade action manually in the update action in the assignment controller.

=====Intuition behind fix=====

After realizing that the issue was caused by the cascade action not being implemented, implementing it was the way to go. After the implementation in the update action of the Assignment controller, the instructor was able to update the metareview required or not checkbox.

===Test Plan===

====To replicate issue [https://github.com/expertiza/expertiza/issues/972 #972]====
# Go to the edit action in the assignments controller. (http://localhost:3000/assignments/(#assignment_id)/edit)
# Click on the due dates tab.
# Change number of rounds of reviews to a value less than 3. (At this stage, our fix would throw a confirmation message with a warning)
# Upon pressing submit, the rounds of reviews will not be updated. (In our fix, the rounds of reviews will only change upon accepting the confirmation)

====To replicate issue [https://github.com/expertiza/expertiza/issues/961 #961]====

# Go to the edit action in the assignments controller. (http://localhost:3000/assignments/(#assignment_id)/edit)
# Click on the due dates tab.
# Uncheck the metareviews allowed checkbox.
# Upon submission, the update will not be visible. (Our fix would allow this action and the update will be visible)

===References===

#[https://github.com/expertiza/expertiza Expertiza GitHub]
#[https://github.com/rajanalwan/expertiza GitHub Project Fork Repository]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/pull/1033 Pull request link]
#[https://youtu.be/ysVeHlrlKo8 Video of fix]

CSC/CSC 517 Fall 2017/ProjectPurple

2017-11-02T23:10:02Z

Ralwan:

== E1778 OSS project Purple: UI fixes for assignment creation ==

This page provides the documentation of the UI fixes for assignment creation in Expertiza.

===Problem Statement===
Expertiza allows the instructor to enable and disable different features to be used in an assignment. Some of these setting e.g., allow peer review to be done in iterations, allow third party to assess the quality of the peer feedback, can be changed from manage>assignment and click on edit icon. Some of the UI to enable and disable these features were broken and the aim of this project was to fix the following issues.

The following issues were fixed in this project:
* Issue [https://github.com/expertiza/expertiza/issues/972 #972]: While editing an assignment, changing the number of review rounds doesn't work in Expertiza.
* Issue [https://github.com/expertiza/expertiza/issues/961 #961]: Once an assignment is duplicated from another assignment with metareview enabled, metareview deadline cannot be disabled.

* Issue [https://github.com/expertiza/expertiza/issues/295 #295]: was already fixed before the start of this project.

===Issue Fix===
A working demo of the fixed issues can be found [https://youtu.be/ysVeHlrlKo8 here].

The first two actions of enabling and disabling metareviews show the fixed issue #961. The action of reducing the rounds of reviews shows our fix to issue #972.

====Issue [https://github.com/expertiza/expertiza/issues/972 #972]====
=====Initial Approach=====
The main problem as stated in the problem statement is that .last() does not exist for the array. This method was used to identify the last element in the array of elements. This was solved by identifying the last element as the (array.length - 1)th element of the array.

=====Actual problem=====
The issue was the instructor was not able to change the rounds of reviews for an assignment. The reason for this issue was found to be the actual rounds of reviews was overridden by the maximum of submissions and review count in the database. This constraint was introduced to restrict the instructor from resetting the rounds of reviews lesser than the submissions count. The constraint was not necessary for some scenarios which should have allowed the instructor to reset.

=====Solution=====

To solve this scenario, we introduced a warning message with a confirmation option to allow the instructor to override the rounds of reviews.

=====Intuition behind fix=====

After realizing the actual location of the code that was causing the bug, we realized that assuming the current rounds of reviews by the maximum amongst the submissions count, reviews count, and the rounds of reviews led to a scenario where even when the instructor wanted to update the rounds of reviews, he wasn't allowed to do so. This was a problem because, there would have been a certain situation where the instructor had to override the existing value because of a previous error (maybe even typographical). Thus, a confirmation message with a warning was the way to go.

====Issue [https://github.com/expertiza/expertiza/issues/961 #961]====
=====Problem=====

The problem was the need for metareview could not be disabled while editing an assignment. This was because the DueDate table was not updated with the necessary cascade actions.

=====Solution=====

This issue was solved by implementing the cascade action manually in the update action in the assignment controller.

=====Intuition behind fix=====

After realizing that the issue was caused by the cascade action not being implemented, implementing it was the way to go. After the implementation in the update action of the Assignment controller, the instructor was able to update the metareview required or not checkbox.

===Test Plan===

====To replicate issue [https://github.com/expertiza/expertiza/issues/972 #972]====
# Go to the edit action in the assignments controller. (http://localhost:3000/assignments/(#assignment_id)/edit)
# Click on the due dates tab.
# Change number of rounds of reviews to a value less than 3. (At this stage, our fix would throw a confirmation message with a warning)
# Upon pressing submit, the rounds of reviews will not be updated. (In our fix, the rounds of reviews will only change upon accepting the confirmation)

====To replicate issue [https://github.com/expertiza/expertiza/issues/961 #961]====

# Go to the edit action in the assignments controller. (http://localhost:3000/assignments/(#assignment_id)/edit)
# Click on the due dates tab.
# Uncheck the metareviews allowed checkbox.
# Upon submission, the update will not be visible. (Our fix would allow this action and the update will be visible)

===References===

#[https://github.com/expertiza/expertiza Expertiza GitHub]
#[https://github.com/rajanalwan/expertiza GitHub Project Fork Repository]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/pull/1033 Pull request link]
#[https://youtu.be/ysVeHlrlKo8 Video of fix]

CSC/CSC 517 Fall 2017/ProjectPurple

2017-11-02T23:09:31Z

Ralwan:

== E1778 OSS project Purple: UI fixes for assignment creation ==

This page provides the documentation of the UI fixes for assignment creation in Expertiza.

===Problem Statement===
Expertiza allows the instructor to enable and disable different features to be used in an assignment. Some of these setting e.g., allow peer review to be done in iterations, allow third party to assess the quality of the peer feedback, can be changed from manage>assignment and click on edit icon. Some of the UI to enable and disable these features were broken and the aim of this project was to fix the following issues.

The following issues were fixed in this project:
* Issue [https://github.com/expertiza/expertiza/issues/972 #972]: While editing an assignment, changing the number of review rounds doesn't work in Expertiza.
* Issue [https://github.com/expertiza/expertiza/issues/961 #961]: Once an assignment is duplicated from another assignment with metareview enabled, metareview deadline cannot be disabled.

* Issue [https://github.com/expertiza/expertiza/issues/295 #295]: was already fixed before the start of this project.

===Issue Fix===
A working demo of the fixed issues can be found [https://youtu.be/ysVeHlrlKo8 here].

The first two actions of enabling and disabling metareviews show the fixed issue #961. The action of reducing the rounds of reviews shows our fix to issue #972.

====Issue [https://github.com/expertiza/expertiza/issues/972 #972]====
=====Initial Approach=====
The main problem as stated in the problem statement is that .last() does not exist for the array. This method was used to identify the last element in the array of elements. This was solved by identifying the last element as the (array.length - 1)th element of the array.

=====Actual problem=====
The issue was the instructor was not able to change the rounds of reviews for an assignment. The reason for this issue was found to be the actual rounds of reviews was overridden by the maximum of submissions and review count in the database. This constraint was introduced to restrict the instructor from resetting the rounds of reviews lesser than the submissions count. The constraint was not necessary for some scenarios which should have allowed the instructor to reset.

=====Solution=====

To solve this scenario, we introduced a warning message with a confirmation option to allow the instructor to override the rounds of reviews.

=====Intuition behind fix=====

After realizing the actual location of the code that was causing the bug, we realized that assuming the current rounds of reviews by the maximum amongst the submissions count, reviews count, and the rounds of reviews led to a scenario where even when the instructor wanted to update the rounds of reviews, he wasn't allowed to do so. This was a problem because, there would have been a certain situation where the instructor had to override the existing value because of a previous error (maybe even typographical). Thus, a confirmation message with a warning was the way to go.

====Issue [https://github.com/expertiza/expertiza/issues/961 #961]====
=====Problem=====

The problem was the need for metareview could not be disabled while editing an assignment. This was because the DueDate table was not updated with the necessary cascade actions.

=====Solution=====

This issue was solved by implementing the cascade action manually in the update action in the assignment controller.

=====Intuition behind fix=====

After realizing that the issue was caused by the cascade action not being implemented, implementing it was the way to go. After the implementation in the update action of the Assignment controller, the instructor was able to update the metareview required or not checkbox.

===Test Plan===

====To replicate issue [https://github.com/expertiza/expertiza/issues/972 #972]====

1. Go to the edit action in the assignments controller. (http://localhost:3000/assignments/(#assignment_id)/edit)
2. Click on the due dates tab.
3. Change number of rounds of reviews to a value less than 3. (At this stage, our fix would throw a confirmation message with a warning)
4. Upon pressing submit, the rounds of reviews will not be updated. (In our fix, the rounds of reviews will only change upon accepting the confirmation)

====To replicate issue [https://github.com/expertiza/expertiza/issues/961 #961]====

1. Go to the edit action in the assignments controller. (http://localhost:3000/assignments/(#assignment_id)/edit)
2. Click on the due dates tab.
3. Uncheck the metareviews allowed checkbox.
4. Upon submission, the update will not be visible. (Our fix would allow this action and the update will be visible)

===References===

#[https://github.com/expertiza/expertiza Expertiza GitHub]
#[https://github.com/rajanalwan/expertiza GitHub Project Fork Repository]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/pull/1033 Pull request link]
#[https://youtu.be/ysVeHlrlKo8 Video of fix]

CSC/CSC 517 Fall 2017/ProjectPurple

2017-11-02T23:00:51Z

Ralwan:

== E1778 OSS project Purple: UI fixes for assignment creation ==

This page provides the documentation of the UI fixes for assignment creation in Expertiza.

===Problem Statement===
Expertiza allows the instructor to enable and disable different features to be used in an assignment. Some of these setting e.g., allow peer review to be done in iterations, allow third party to assess the quality of the peer feedback, can be changed from manage>assignment and click on edit icon. Some of the UI to enable and disable these features were broken and the aim of this project was to fix the following issues.

The following issues were fixed in this project:
* Issue [https://github.com/expertiza/expertiza/issues/972 #972]: While editing an assignment, changing the number of review rounds doesn't work in Expertiza.
* Issue [https://github.com/expertiza/expertiza/issues/961 #961]: Once an assignment is duplicated from another assignment with metareview enabled, metareview deadline cannot be disabled.

* Issue [https://github.com/expertiza/expertiza/issues/295 #295]: was already fixed before the start of this project.

===Issue Fix===
A working demo of the fixed issues can be found [https://youtu.be/ysVeHlrlKo8 here].

The first two actions of enabling and disabling metareviews show the fixed issue #961. The action of reducing the rounds of reviews shows our fix to issue #972.

====Issue [https://github.com/expertiza/expertiza/issues/972 #972]====
=====Initial Approach=====
The main problem as stated in the problem statement is that .last() does not exist for the array. This method was used to identify the last element in the array of elements. This was solved by identifying the last element as the (array.length - 1)th element of the array.

=====Actual problem=====
The issue was the instructor was not able to change the rounds of reviews for an assignment. The reason for this issue was found to be the actual rounds of reviews was overridden by the maximum of submissions and review count in the database. This constraint was introduced to restrict the instructor from resetting the rounds of reviews lesser than the submissions count. The constraint was not necessary for some scenarios which should have allowed the instructor to reset.

=====Solution=====

To solve this scenario, we introduced a warning message with a confirmation option to allow the instructor to override the rounds of reviews.

=====Intuition behind fix=====

After realizing the actual location of the code that was causing the bug, we realized that assuming the current rounds of reviews by the maximum amongst the submissions count, reviews count, and the rounds of reviews led to a scenario where even when the instructor wanted to update the rounds of reviews, he wasn't allowed to do so. This was a problem because, there would have been a certain situation where the instructor had to override the existing value because of a previous error (maybe even typographical). Thus, a confirmation message with a warning was the way to go.

====Issue [https://github.com/expertiza/expertiza/issues/961 #961]====
=====Problem=====

The problem was the need for metareview could not be disabled while editing an assignment. This was because the DueDate table was not updated with the necessary cascade actions.

=====Solution=====

This issue was solved by implementing the cascade action manually in the update action in the assignment controller.

=====Intuition behind fix=====

After realizing that the issue was caused by the cascade action not being implemented, implementing it was the way to go. After the implementation in the update action of the Assignment controller, the instructor was able to update the metareview required or not checkbox.

===References===

#[https://github.com/expertiza/expertiza Expertiza GitHub]
#[https://github.com/rajanalwan/expertiza GitHub Project Fork Repository]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/pull/1033 Pull request link]
#[https://youtu.be/ysVeHlrlKo8 Video of fix]

CSC/CSC 517 Fall 2017/ProjectPurple

2017-11-02T22:57:49Z

Ralwan:

== E1778 OSS project Purple: UI fixes for assignment creation ==

This page provides the documentation of the UI fixes for assignment creation in Expertiza.

===Problem Statement===
Expertiza allows the instructor to enable and disable different features to be used in an assignment. Some of these setting e.g., allow peer review to be done in iterations, allow third party to assess the quality of the peer feedback, can be changed from manage>assignment and click on edit icon. Some of the UI to enable and disable these features were broken and the aim of this project was to fix the following issues.

The following issues were fixed in this project:
* Issue [https://github.com/expertiza/expertiza/issues/972 #972]: While editing an assignment, changing the number of review rounds doesn't work in Expertiza.
* Issue [https://github.com/expertiza/expertiza/issues/961 #961]: Once an assignment is duplicated from another assignment with metareview enabled, metareview deadline cannot be disabled.

* Issue [https://github.com/expertiza/expertiza/issues/295 #295]: was already fixed before the start of this project.

===Issue Fix===
A working demo of the fixed issues can be found [https://youtu.be/ysVeHlrlKo8 here].

The first two actions of enabling and disabling metareviews show the fixed issue #961. The action of reducing the rounds of reviews shows our fix to issue #972.

====Issue [https://github.com/expertiza/expertiza/issues/972 #972]====
=====Initial Approach=====
The main problem as stated in the problem statement is that .last() does not exist for the array. This method was used to identify the last element in the array of elements. This was solved by identifying the last element as the (array.length - 1)th element of the array.

=====Actual problem=====
The issue was the instructor was not able to change the rounds of reviews for an assignment. The reason for this issue was found to be the actual rounds of reviews was overridden by the maximum of submissions and review count in the database. This constraint was introduced to restrict the instructor from resetting the rounds of reviews lesser than the submissions count. The constraint was not necessary for some scenarios which should have allowed the instructor to reset.

=====Solution=====

To solve this scenario, we introduced a warning message with a confirmation option to allow the instructor to override the rounds of reviews.

=====Intuition behind fix=====

After realizing the actual location of the code that was causing the bug, we realized that assuming the current rounds of reviews by the maximum amongst the submissions count, reviews count, and the rounds of reviews led to a scenario where even when the instructor wanted to update the rounds of reviews, he wasn't allowed to do so. This was a problem because, there would have been a certain situation where the instructor had to override the existing value because of a previous error (maybe even typographical). Thus, a confirmation message with a warning was the way to go.

====Issue [https://github.com/expertiza/expertiza/issues/961 #961]====
=====Problem=====

The problem was the need for metareview could not be disabled while editing an assignment. This was because the DueDate table was not updated with the necessary cascade actions.

===References===

#[https://github.com/expertiza/expertiza Expertiza GitHub]
#[https://github.com/rajanalwan/expertiza GitHub Project Fork Repository]
#[http://expertiza.ncsu.edu/ Expertiza website]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
#[https://github.com/expertiza/expertiza/pull/1033 Pull request link]

CSC/CSC 517 Fall 2017/ProjectPurple

2017-10-28T14:59:27Z

Ralwan:

CSC/CSC 517 Fall 2017/ProjectPurple

2017-10-28T14:56:56Z

Ralwan:

CSC/CSC 517 Fall 2017/ProjectPurple

2017-10-28T03:18:38Z

Ralwan:

CSC/CSC 517 Fall 2017/ProjectPurple

2017-10-28T03:11:54Z

Ralwan:

CSC/CSC 517 Fall 2017/ProjectPurple

2017-10-28T02:54:15Z

Ralwan: /* Actual problem */

CSC/CSC 517 Fall 2017/ProjectPurple

2017-10-27T18:34:19Z

Ralwan: Created page with "== E1778 OSS project Purple: UI fixes for assignment creation == This page provides the documentation of the UI fixes for assignment creation in Expertiza. ===Problem Statemen..."