Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2017/oss M1706

2017-04-05T15:19:32Z

Jbcrick: /* Student View */

===Description===

===Tasks to be completed===

===Current Implementation===

===UML Diagram===

===Proposed Design===

'''TASK 1''' -

'''TASK 2''' -

==== Design Pattern Used ====

====Features to be added====

====Gems to be used====

===Metrics View===

====Instructor View====

====Student View====

===Testing Plan===

====Files Changed and Added====

====Models====

====Controllers====

====Views====

===Important Links===

Link to Github repository :

Link to Pull request :

===References===

CSC/ECE 517 Spring 2017/oss M1706

2017-04-05T15:19:20Z

Jbcrick: /* Instructor View */

===Description===

===Tasks to be completed===

===Current Implementation===

===UML Diagram===

===Proposed Design===

'''TASK 1''' -

'''TASK 2''' -

==== Design Pattern Used ====

====Features to be added====

====Gems to be used====

===Metrics View===

====Instructor View====

====Student View====

[[File:E1677ins1.PNG]]

===Testing Plan===

====Files Changed and Added====

====Models====

====Controllers====

====Views====

===Important Links===

Link to Github repository :

Link to Pull request :

===References===

CSC/ECE 517 Spring 2017/oss M1706

2017-04-05T15:19:05Z

Jbcrick: Created page with " ===Description=== ===Tasks to be completed=== ===Current Implementation=== ===UML Diagram=== ===Proposed Design=== '''TASK 1''' - '''TASK 2''' - ==== Design Patt..."

===Description===

===Tasks to be completed===

===Current Implementation===

===UML Diagram===

===Proposed Design===

'''TASK 1''' -

'''TASK 2''' -

==== Design Pattern Used ====

====Features to be added====

====Gems to be used====

===Metrics View===

====Instructor View====

[[File:E1677ins2.PNG]]

====Student View====

[[File:E1677ins1.PNG]]

===Testing Plan===

====Files Changed and Added====

====Models====

====Controllers====

====Views====

===Important Links===

Link to Github repository :

Link to Pull request :

===References===

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:52:44Z

Jbcrick: /* New Method: get_topic_bg_color() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id,
deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id,
deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id,
deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id:
assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and
!selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and
selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' +
get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id:
topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:51:59Z

Jbcrick: /* New Method: check_topic_due_date_value() */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:51:07Z

Jbcrick: /* New Method: get_topic_deadline() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id,
deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id:
assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and
!selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and
selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' +
get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id:
topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:50:42Z

Jbcrick: /* New Method: get_suggested_topics() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id:
assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and
!selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and
selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' +
get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id:
topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:50:23Z

Jbcrick: /* New Method: get_intelligent_topic_row() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and
!selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and
selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' +
get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id:
topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:50:01Z

Jbcrick: /* New Method: get_intelligent_topic_row() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and
!selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and
selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' + get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id:
topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:48:54Z

Jbcrick: /* New Method: get_topic_bg_color() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' + get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id:
topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:46:59Z

Jbcrick: /* New Method: get_topic_bg_color() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' + get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id: topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:45:59Z

Jbcrick: /* Introduction */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = []
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics, max_team_size)
row_html = ''
if !selected_topics.nil? && !selected_topics.empty?
selected_topics.each do |selected_topic|
row_html = if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
'<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
'<tr bgcolor="lightgray">'
else
'<tr id="topic_' + topic.id.to_s + '">'
end
end
else
row_html = '<tr id="topic_' + topic.id.to_s + '" style="background-color:' + get_topic_bg_color(topic, max_team_size) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic, max_team_size)
calculation = (400 * (1 - (Math.tanh(2 * [max_team_size.to_f / Bid.where(topic_id: topic.id).count, 1].min - 1) + 1) / 2)).to_i.to_s
'rgb(' + calculation + ',' + calculation + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && !participants.empty?
chooser_present = false
participants.each do |participant|
next unless topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
name_html += 'No choosers.' unless chooser_present
end
name_html.html_safe
end
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:43:45Z

Jbcrick: /* Introduction */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki>def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-23T01:03:53Z

Jbcrick:

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

==== New Test for Helper Classes: spec/helpers/sign_up_sheet_helper_spec.rb ====
Implemented positive and negative test cases for all the methods in sign_up_sheet_helper.rb

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

====Helper File Changes====
There is no change in the expected behaviour.
* '''get_suggested_topics''': Retrieve list of topics suggested by signed in user for an assignment.
* '''get_intelligent_topic_row''': Render Intelligent Row in bidding based topic selection.
* '''get_topic_bg_color''': Render background color for row based on signed in user and status of the topic.
* '''render_participant_info''': Render Participant Info based on topic, assignment and participants.

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T19:07:54Z

Jbcrick: /* Running the Project Locally */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==
Those who contributed to the project could run the project locally by going to a terminal window, navigating to the project folder and running the single command:

rails server

If the project was to be run again after changes to project code have been made, the commands to run from the terminal window would be as follows:

bundle install
rails s

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T19:05:59Z

Jbcrick: /* Running the Project Locally */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==
Those who contributed to the project could run the project locally by going to a terminal window, navigating to the project folder and running the single command:

rails server

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:57:58Z

Jbcrick: /* Introduction */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:55:39Z

Jbcrick:

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki>def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki>def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki>def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki>def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki>def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:54:26Z

Jbcrick: /* Introduction */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

==== New Method: check_topic_due_date_value() ====
<nowiki>def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki>def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki>def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki>def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki>def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki>def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:51:49Z

Jbcrick: /* Introduction */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

==== New Method: check_topic_due_date_value() ====

<nowiki>def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====

<nowiki>def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====

<nowiki>def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====

<nowiki>def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====

def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end

==== New Method: render_participant_info() ====

<nowiki>def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:51:00Z

Jbcrick: /* New Method: render_participant_info() */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

==== New Method: check_topic_due_date_value() ====

def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end

==== New Method: get_topic_deadline() ====

def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end

==== New Method: get_suggested_topics() ====

def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end

==== New Method: get_intelligent_topic_row() ====

def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end

==== New Method: get_topic_bg_color() ====

def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end

==== New Method: render_participant_info() ====

<nowiki>def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:50:17Z

Jbcrick: /* Introduction */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder).

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

==== New Method: check_topic_due_date_value() ====

def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end

==== New Method: get_topic_deadline() ====

def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end

==== New Method: get_suggested_topics() ====

def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end

==== New Method: get_intelligent_topic_row() ====

def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end

==== New Method: get_topic_bg_color() ====

def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end

==== New Method: render_participant_info() ====

def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:48:44Z

Jbcrick: /* New Method: check_topic_due_date_value() */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:48:24Z

Jbcrick: /* Introduction */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:47:23Z

Jbcrick: /* New Method: check_topic_due_date_value() */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:46:52Z

Jbcrick: /* New Method: check_topic_due_date_value() */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:46:01Z

Jbcrick: /* Introduction */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:45:36Z

Jbcrick: /* Refactor the update_due_dates from AssignmentForm using the DRY principle */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:44:26Z

Jbcrick: /* New Function: get_intelligent_topic_row() */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:43:49Z

Jbcrick: /* Change to new redirect method rather using controller and action explicitly. */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:42:48Z

Jbcrick: /* remove_assignment_from_course moved to model */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:42:11Z

Jbcrick: /* Refactoring Update function */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:41:34Z

Jbcrick: /* check_topic_due_date_value() function */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:41:11Z

Jbcrick: /* Refactoring Edit function */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:38:09Z

Jbcrick: /* Introduction */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T18:36:21Z