CSC/ECE 517 Spring 2013/Final Project E730 - Revision history

Mlhall3 at 00:54, 24 April 2013

2013-04-24T00:54:47Z

@@ Line 42: / Line 42: @@
 #Use a tool tip to display a given user’s reputation when the instructor hovers over the reviewer’s name with the mouse pointer.
 #Add Unit/Functional test cases to test the functionality of the algorithm.
@@ Line 120: / Line 157: @@
 [[File:view_nesting.jpg]]

Mlhall3 at 20:26, 23 April 2013

2013-04-23T20:26:28Z

← Older revision		Revision as of 20:26, 23 April 2013
Line 123:		Line 123:
	==Running the Code==		==Running the Code==

	First, download the scrubbed database to a location referred to here as "DB_PATH"		First, download the scrubbed database to a location referred to here as "DB_PATH".

			"PATH" is simply where you want to clone your repository to contain your working code.

	Next, reserve the "Ruby on Rails" image in VCL. Open a terminal window once the reservation is ready.		Next, reserve the "Ruby on Rails" image in VCL. Open a terminal window once the reservation is ready.

Mlhall3 at 20:24, 23 April 2013

2013-04-23T20:24:35Z

← Older revision		Revision as of 20:24, 23 April 2013
Line 119:		Line 119:
	After examining the code in detail, a diagram of the view nesting was created, which would prove useful to anyone further modifying the reputation code and display, or any other aspect related to displaying scores.		After examining the code in detail, a diagram of the view nesting was created, which would prove useful to anyone further modifying the reputation code and display, or any other aspect related to displaying scores.

	[[File:view_nesting.~~bmp~~]]		[[File:view_nesting.jpg]]

	==Running the Code==		==Running the Code==

Mlhall3 at 20:22, 23 April 2013

2013-04-23T20:22:18Z

← Older revision		Revision as of 20:22, 23 April 2013
Line 113:		Line 113:
	#Ensure that weighted scores are displayed only after deadline, else unweighted scores need to be displayed.		#Ensure that weighted scores are displayed only after deadline, else unweighted scores need to be displayed.

			==View Nesting==

			One of the primary difficulties encountered in altering the view to correctly display the reputation was in determining which view should contain the view code. This was difficult due to the way the views were nested, and rendered as partials. In addition, it was not always clear what variables were available to a view (due simply to not knowing the entry point into the view because of this nesting) or what parameters were accessible.

			After examining the code in detail, a diagram of the view nesting was created, which would prove useful to anyone further modifying the reputation code and display, or any other aspect related to displaying scores.

			[[File:view_nesting.bmp]]

	==Running the Code==		==Running the Code==

Mlhall3 at 00:24, 23 April 2013

2013-04-23T00:24:59Z

← Older revision		Revision as of 00:24, 23 April 2013
Line 119:		Line 119:
	Next, reserve the "Ruby on Rails" image in VCL. Open a terminal window once the reservation is ready.		Next, reserve the "Ruby on Rails" image in VCL. Open a terminal window once the reservation is ready.

			#rvm use 1.8.7
	#mkdir /PATH/project3		#mkdir /PATH/project3
	#cd /PATH/project3		#cd /PATH/project3
Line 124:		Line 125:
	#git clone http://github.com/ashrayn/expertiza.git		#git clone http://github.com/ashrayn/expertiza.git
	#cd expertiza		#cd expertiza
	#git ~~fetch origin e730-reputation:e730-reputation~~		#git stash
	#git checkout e730-reputation		#git checkout e730-reputation
	~~#rvm use 1.8.7~~
	#sudo rvm gemset empty		#sudo rvm gemset empty
	#gem install bundle		#gem install bundle

Mlhall3 at 23:11, 22 April 2013

2013-04-22T23:11:29Z

← Older revision		Revision as of 23:11, 22 April 2013
Line 117:		Line 117:

	First, download the scrubbed database to a location referred to here as "DB_PATH"		First, download the scrubbed database to a location referred to here as "DB_PATH"
			Next, reserve the "Ruby on Rails" image in VCL. Open a terminal window once the reservation is ready.

	#mkdir /PATH/project3		#mkdir /PATH/project3
	#cd /PATH/project3		#cd /PATH/project3

Mlhall3 at 23:09, 22 April 2013

2013-04-22T23:09:53Z

← Older revision		Revision as of 23:09, 22 April 2013
Line 112:		Line 112:
	#Ensure that only the instructor can mark a review as rogue.		#Ensure that only the instructor can mark a review as rogue.
	#Ensure that weighted scores are displayed only after deadline, else unweighted scores need to be displayed.		#Ensure that weighted scores are displayed only after deadline, else unweighted scores need to be displayed.


			==Running the Code==

			First, download the scrubbed database to a location referred to here as "DB_PATH"
			#mkdir /PATH/project3
			#cd /PATH/project3
			#unset SSH_ASKPASS
			#git clone http://github.com/ashrayn/expertiza.git
			#cd expertiza
			#git fetch origin e730-reputation:e730-reputation
			#git checkout e730-reputation
			#rvm use 1.8.7
			#sudo rvm gemset empty
			#gem install bundle
			#sudo yum install aspell-devel
			#gem install raspell -v 1.3
			#bundle install
			#rake db:migrate
			#mysqladmin -uroot password admin
			#mysql -uroot -p pg_development < /DB_PATH/expertiza-scrubbed.sql
			#mysql -u root admin
			#SET PASSWORD FOR root@localhost=PASSWORD('');
			#create user expertiza@localhost identified by "";
			#grant all on pg_development.* to expertiza@localhost;
			#exit
			#./script/console
			#u = User.find_by_name("admin")
			#u.clear_password="admin"
			#u.clear_password_confirmation="admin"
			#u.save
			#quit
			#./script/server

Mlhall3 at 22:14, 22 April 2013

2013-04-22T22:14:24Z

← Older revision		Revision as of 22:14, 22 April 2013
Line 6:		Line 6:
	#Eric Lumpkin (eblumpki@ncsu.edu)		#Eric Lumpkin (eblumpki@ncsu.edu)
	#Ashray Nagaraju (ashray@ncsu.edu)		#Ashray Nagaraju (ashray@ncsu.edu)


	__TOC__		__TOC__

Mlhall3 at 22:13, 22 April 2013

2013-04-22T22:13:42Z

Mlhall3 at 22:00, 22 April 2013

2013-04-22T22:00:31Z

← Older revision		Revision as of 22:00, 22 April 2013
Line 35:		Line 35:


	==Proposed Design==		===Proposed Design===

	#Add a button by each review that will allow an instructor to delete reviews which have been determined to "rogue" (ie, an outlier in terms of the average review score.)		#Add a button by each review that will allow an instructor to delete reviews which have been determined to "rogue" (ie, an outlier in terms of the average review score.)

← Older revision		Revision as of 22:13, 22 April 2013
Line 38:		Line 38:

	#Add a button by each review that will allow an instructor to delete reviews which have been determined to "rogue" (ie, an outlier in terms of the average review score.)		#Add a button by each review that will allow an instructor to delete reviews which have been determined to "rogue" (ie, an outlier in terms of the average review score.)

	#Implement a toggle that allows an instructor to use either the equally weighted or reputation-based grading systems. This will allow the instructor to choose which weighting system to use at the assignment level. All reviews for a given assignment will use the same weighting system.		#Implement a toggle that allows an instructor to use either the equally weighted or reputation-based grading systems. This will allow the instructor to choose which weighting system to use at the assignment level. All reviews for a given assignment will use the same weighting system.

	#Use a tool tip to display a given user’s reputation when the instructor hovers over the reviewer’s name with the mouse pointer.		#Use a tool tip to display a given user’s reputation when the instructor hovers over the reviewer’s name with the mouse pointer.

	#Add Unit/Functional test cases to test the functionality of the algorithm.		#Add Unit/Functional test cases to test the functionality of the algorithm.

Line 61:		Line 58:

	#Login to Expertiza (Admin or an equivalent person).		#Login to Expertiza (Admin or an equivalent person).

	#Click on Create an assignment.		#Click on Create an assignment.

	#Enable weighted grading for the particular assignment by actuating an enabled toggle.		#Enable weighted grading for the particular assignment by actuating an enabled toggle.

	#Save the changes.		#Save the changes.

Line 83:		Line 77:

	#Login to Expertiza (Admin or an equivalent person).		#Login to Expertiza (Admin or an equivalent person).

	#Click on Create an assignment		#Click on Create an assignment

	#Hover the mouse over a score field.		#Hover the mouse over a score field.