Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:33:54Z

Jlbucha4: /* Files That Have Been Modified */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

Mentors may also be manually assigned after a topic is created as per the addition button for topics that need a mentor

[[File:FinalProjectAddMentorManual.png|175px|Screenshot demonstrating how to add a mentor to a topic manually.]]

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

[[File:FinalProjectTablesView.png|600px|thumb|Right|Interface view for the topic tables that show an you can manually add and remove mentors from this view]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That Have Been Modified==
The following files have been updated for this implementation:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/controllers/assignments_controller.rb assignments_controller.rb] - Used to unassign mentor with the X button
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

Config:
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/config/routes.rb routes.rb] - Added routes to controller for the add and remove mentor buttons

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:26:25Z

Jlbucha4: /* Files That Have Been Modified */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

Mentors may also be manually assigned after a topic is created as per the addition button for topics that need a mentor

[[File:FinalProjectAddMentorManual.png|175px|Screenshot demonstrating how to add a mentor to a topic manually.]]

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

[[File:FinalProjectTablesView.png|600px|thumb|Right|Interface view for the topic tables that show an you can manually add and remove mentors from this view]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That Have Been Modified==
The following files have been updated for this implementation:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:26:10Z

Jlbucha4: /* Files That May Be Modified */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

Mentors may also be manually assigned after a topic is created as per the addition button for topics that need a mentor

[[File:FinalProjectAddMentorManual.png|175px|Screenshot demonstrating how to add a mentor to a topic manually.]]

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

[[File:FinalProjectTablesView.png|600px|thumb|Right|Interface view for the topic tables that show an you can manually add and remove mentors from this view]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That Have Been Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

File:FinalProjectTablesView.png

2025-04-22T00:25:20Z

Jlbucha4: Jlbucha4 uploaded a new version of File:FinalProjectTablesView.png

== Summary ==
Shows the final table view of the topics

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:23:04Z

Jlbucha4: /* Implementation */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

Mentors may also be manually assigned after a topic is created as per the addition button for topics that need a mentor

[[File:FinalProjectAddMentorManual.png|175px|Screenshot demonstrating how to add a mentor to a topic manually.]]

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

[[File:FinalProjectTablesView.png|600px|thumb|Right|Interface view for the topic tables that show an you can manually add and remove mentors from this view]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:22:48Z

Jlbucha4: /* Implementation */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

Mentors may also be manually assigned after a topic is created as per the addition button for topics that need a mentor

[[File:FinalProjectAddMentorManual.png|175px|Screenshot demonstrating how to add a mentor to a topic manually.]]

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

[[File:FinalProjectTableView.png|600px|thumb|Right|Interface view for the topic tables that show an you can manually add and remove mentors from this view]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

File:FinalProjectTablesView.png

2025-04-22T00:21:47Z

Jlbucha4: Shows the final table view of the topics

== Summary ==
Shows the final table view of the topics

File:Mentor checkbox mockup.png

2025-04-22T00:20:54Z

Jlbucha4: Jlbucha4 reverted File:Mentor checkbox mockup.png to an old version

File:Mentor checkbox mockup.png

2025-04-22T00:19:35Z

Jlbucha4: Jlbucha4 uploaded a new version of File:Mentor checkbox mockup.png

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:17:59Z

Jlbucha4: /* Automatic Assignment of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

Mentors may also be manually assigned after a topic is created as per the addition button for topics that need a mentor

[[File:FinalProjectAddMentorManual.png|175px|Screenshot demonstrating how to add a mentor to a topic manually.]]

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:17:52Z

Jlbucha4: /* Automatic Assignment of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

Mentors may also be manually assigned after a topic is created as per the addition button for topics that need a mentor
[[File:FinalProjectAddMentorManual.png|175px|Screenshot demonstrating how to add a mentor to a topic manually.]]

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

File:FinalProjectAddMentorManual.png

2025-04-22T00:17:09Z

Jlbucha4: Showcase the icon used to add a mentor manually to a topic

== Summary ==
Showcase the icon used to add a mentor manually to a topic

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:09:02Z

Jlbucha4: /* Files That May Be Modified */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb views/sign_up_sheet/add_mentor_to_topic.html.erb] - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:08:44Z

Jlbucha4: /* Files That May Be Modified */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/topic_mentors/app/views/sign_up_sheet/add_mentor_to_topic.html.erb] views/sign_up_sheet/add_mentor_to_topic.html.erb - Used to assign a mentor to an existing topic
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:05:18Z

Jlbucha4: /* Removal of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|175px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:05:13Z

Jlbucha4: /* Removal of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|100px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:05:04Z

Jlbucha4: /* Removal of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|200px|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:04:53Z

Jlbucha4: /* Removal of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.

[[File:FinalProjectRemoveMentor.png|200px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:04:47Z

Jlbucha4: /* Removal of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.
[[File:FinalProjectRemoveMentor.png|200px|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:04:39Z

Jlbucha4: /* Removal of Mentors */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.
[[File:FinalProjectRemoveMentor.png|200px|thumb|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-22T00:04:11Z

Jlbucha4: /* Implementation */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Removal of Mentors====
Mentors that are assigned to teams are able to be removed manually or automatically when a team drops the topic and the mentor is the only one left on the team.

The manual removal of mentors can be achieved by clicking the 'X' next to their name as they appear in the 'Mentor' column as part of the Topics tab within certain assignments.
[[File:FinalProjectRemoveMentor.png|200px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

File:FinalProjectRemoveMentor.png

2025-04-22T00:03:45Z

Jlbucha4: This file showcases the 'X' next to a mentors name that can be removed from a topic

== Summary ==
This file showcases the 'X' next to a mentors name that can be removed from a topic

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-21T23:57:15Z

Jlbucha4: /* Project Overview */

__TOC__

==Background==
In Project E2504, implementation was added for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned. To expand the functionality of the mentor management system, we want to incorporate mentors into assignment topics.

==Project Overview==
The main objective of this project is to extend the mentor management system by having it collaborate with the assignment topics system. When an assignment with topics is created, topics are imported from a spreadsheet into the assignment table. This project will focus on including pre-selected mentors (entered in the spreadsheet) in the assignment table and having the mentor assigned to the team automatically upon topic selection. On top of this, mentors should be able to be unassigned from topics on command and automatically when there are no more member as part of a team.

==Implementation==

====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing topics to include mentors. This checkbox will toggle whether or not the mentors will be included in the assignment/import. This checkbox will also reload the table to include the additional column required for the mentor's name. Once saved, these mentor names will be stored as an additional attribute in the sign_up_topic.

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|Mockup illustrating the proposed location for the mentor checkbox within the user interface form.]]

It's important to note that this will not affect how teams and mentors are managed for projects where the entire class has the same project. That will still be handled by the mentors being assigned to a team once that team has reached half capacity. This feature will allow mentors to be associated with project topics in projects where each team has a different topic (e.g., ECE 517 Expertiza-based projects).

====Automatic Assignment of Mentors====
After a team has been created and is allowed to choose a topic from the assignment, the mentor who was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team (likely via the `TeamsUser` association) and ensuring their `can_mentor` participant value is true. Given the logic of the previous mentor management implementations, this ensures the participant on the team is recognized as a mentor.

The outcome should be that the assigned mentor appears associated with the team in relevant views.
[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|Screenshot demonstrating that the assigned mentor's information is now visible within the teams management view after automatic assignment.]]

This automatic assignment upon topic selection complements the existing logic where mentors are assigned when a team reaches half strength, as seen in the `MentorManagement` model: [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 MentorManagement#assign_mentor].

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are formed, there needs to be a minor change to the way that topics are imported into Expertiza (accessible from the Topics tab of an assignment, e.g., `http://152.7.178.121:8080/assignments/1028/edit`).

There should be an optional field in the import file (spreadsheet) that, when included, associates a mentor with a topic. This requires modifying the import logic to handle this optional mentor column.
[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the checkbox or instructions for the mentor column.]]

[[File:Imported_column_change.png|600px|thumb|Right|View showing the changes in the topic table data column after an import, displaying the imported mentor information associated with topics.]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|Confirmation view indicating the successful import of topics along with their assigned mentors.]]

The system should still support importing topics without mentors. Furthermore, there should be a way to manually add or edit the assigned mentor for a topic after it has been created or imported, whether it initially had a mentor or not.
[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding or editing an individual topic and assigning a mentor to it manually.]]

==Database==
We will likely leverage the existing `teams_users` table structure, potentially using the `duty_id` field or similar mechanisms to signify the mentor role within the context of a team, consistent with how other roles might be managed. The `SignUpTopic` model will need an attribute to store the pre-assigned mentor's identifier before a team signs up.

==Files That May Be Modified==
The following files are likely candidates for modification during this project:

Models:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] - Potentially modified to trigger mentor assignment upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] - To add an attribute for storing the assigned mentor identifier.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_sheet.rb SignUpSheet]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/team.rb Team]

Controller:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - To handle the new import format including the optional mentor column and the checkbox logic.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/sign_up_sheet_controller.rb sign_up_sheet_controller.rb]

Views:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit/_topics.html.erb views/assignments/edit/_topics.html.erb] - To display the mentor column when editing topics if the feature is enabled.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb views/import_file/start.html.erb] - To add the "include mentors" checkbox and potentially update instructions.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topics.html.erb views/sign_up_sheet/_add_topics.html.erb] - To include mentor information when adding/displaying topics.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_line.html.erb views/sign_up_sheet/_table_line.html.erb] - To display the mentor associated with a topic in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_table_header.html.erb views/sign_up_sheet/_table_header.html.erb] - To add a header for the mentor column in the sign-up sheet.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic_names.html.erb views/sign_up_sheet/_topic_names.html.erb] - Potentially adjust topic display.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_add_topic.html.erb views/sign_up_sheet/_add_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/import_file/_sign_up_topic.html.erb app/views/import_file/_sign_up_topic.html.erb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/new.html.erb app/views/sign_up_sheet/new.html.erb]

Helpers:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/helpers/import_topics_helper.rb import_topics_helper.rb]

Migrations:
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings db/migrate/20250301220548_create_meetings]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250301220548_create_meetings.rb db/migrate/20250301220548_create_meetings.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb db/migrate/20250415151755_add_mentor_id_to_sign_up_topics.rb]
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/db/schema.rb db/schema.rb]

==Testing==
===Test Plan===
The overarching purpose of these tests is to verify that the system correctly handles mentor assignments in projects where mentors are associated with topics. Tests should cover both success and failure scenarios for each feature. Key areas include:

* '''Storing Mentors with Topics:'''
** Ensuring that topics can hold information about their assigned mentors (e.g., via the new attribute in `SignUpTopic`).
* '''Assigning Mentors During Topic Sign-up:'''
** Confirming that when a team chooses a topic, the topic's pre-assigned mentor is automatically added to the team with the correct role/permissions.
* '''Compatibility with Existing Assignment Logic:'''
** Ensuring that the existing logic for assigning mentors (e.g., when teams reach half strength in non-topic-based assignments) remains unaffected or correctly integrated if applicable.
* '''Displaying Mentor Information:'''
** Validating that team views and topic views accurately show mentor information for mentored assignments and topics, and correctly hide or omit it otherwise.
* '''Importing Topics with Mentors:'''
** Checking that topics imported from files correctly capture and store mentor assignments when the mentor column is present.
** Verifying that topics are imported correctly when the mentor column is absent.
** Confirming the "Include mentors" checkbox correctly updates the UI (e.g., topic table columns) and influences the import behavior.
* '''Manual Mentor Assignment:''' Testing the ability to manually add or edit a mentor for a topic via the UI.

===Test Coverage===
Once tests are created and modifications are implemented, we will run the test suite and provide evidence (e.g., screenshots of coverage reports) demonstrating the extent to which the new and modified code paths are covered by automated tests. The goal is comprehensive coverage for the implemented features.

==Relevant Links==
* Github Repository: https://github.com/jmwinte3/expertiza
* E2504 Wiki (Previous Project): https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description Document: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===
- Ed Gehringer

=== Members ===
- Jacob Winters
- Alex Wakefield
- John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-08T01:52:08Z

Jlbucha4: /* Implementation */

CSC/ECE 517 Spring 2025

2025-04-08T00:46:30Z

Jlbucha4:

* [[CSC/ECE 517 Spring 2025 - E2503. Refactor the Team hierarchy]]
* [[CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management]]
* [[CSC/ECE 517 Spring 2025 - E2505. Testing Answer Tagging]]
* [[CSC/ECE 517 Spring 2025 - E2508. Reimplement bidding-algorithm web service]]
* [[CSC/ECE 517 Spring 2025 - E2509. Reimplement feedback_response_map.rb]]
* [[CSC/ECE 517 Spring 2025 - E2519. Implement view for results of bidding]]
* [[CSC/ECE 517 Spring 2025 - E2522. Enhancing UI Consistency in Expertiza 1]]
* [[CSC/ECE 517 Spring 2025 - E2520. Reimplement heatgrid UI for reviews]]
* [[CSC/ECE 517 Spring 2025 - E2517. Reimplement internationalization (frontend + backend)]]
* [[CSC/ECE 517 Spring 2025 - E2523: Enhancing UI Consistency in Expertiza 2]]
* [[CSC/ECE 517 Spring 2025 - E2515: Reimplement student_teams_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2501: Refactor review_mapping_helper.rb]]
* [[CSC/ECE 517 Spring 2025 - E2502: Refactor review_mapping_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2512. Reimplement responses controller]]
* [[CSC/ECE 517 Spring 2025 - E2510. Reimplement grades_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2507. Reimplement back end for submission records]]
* [[CSC/ECE 517 Spring 2025 - E2514. Reimplement student_quizzes_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2518. Reimplement password resets (frontend + backend)]]
* [[CSC/ECE 517 Spring 2025 - E2516. Reimplement teams_users_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2511. Reimplement participants_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2521. UI for View submissions/assign grades (except heatgrid)]]
* [[CSC/ECE 517 Spring 2025 - E2513. Reimplement sign_up_topic.rb as project_topic.rb]]
* [[CSC/ECE 517 Spring 2025 - E2506. Implement testing for new Bookmarks Controller]]

== Final Projects ==
* [[CSC/ECE 517 Spring 2025 - E2509 Refactoring and Enhancing the Feedback Response Map Controller]]
* [[CSC/ECE 517 Spring 2025 - E2539 Reimplement Student Task View (Frontend + Backend)]]
* [[CSC/ECE 517 Spring 2025 - E2521 UI for View submissions/assign grades (except heatgrid)]]
* [[CSC/ECE 517 Spring 2025 - E2524 Reimplement student review controller]]
* [[CSC/ECE 517 Spring 2025 - E2525 Reimplement review_mapping_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2526 Reimplement Teams and Participant hierarchies]]
* [[CSC/ECE 517 Spring 2025 - E2530 Reimplement Grades Controller (Frontend + Backend)]]
* [[CSC/ECE 517 Spring 2025 - E2538 Reimplementing Questionnaire Page in Expertiza]]
* [[CSC/ECE 517 Spring 2025 - E2534 UI for Assign Reviewers]]
* [[CSC/ECE 517 Spring 2025 - E2540 Integration of Assignment participant Frontend with participant controller Backend]]
* [[CSC/ECE 517 Spring 2025 - E2532. Reimplement Missing ResponseMap Subclasses]]
* [[CSC/ECE 517 Spring 2025 - E2542. Refactor review_bids_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2533. Reimplement the Team hierarchy]]
* [[CSC/ECE 517 Spring 2025 - E2531 Refactor participants_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2528 Testing for Survey Deployment]]
* [[CSC/ECE 517 Spring 2025 - E2514. Reimplement student_quizzes_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2516. Reimplement teams_users_controller.rb]]
* [[CSC/ECE 517 Spring 2025 - E2535 Reimplement User Profile Management (Frontend + Backend)]]
* [[CSC/ECE 517 Spring 2025 - E2536. Improve assessment360 controller]]
* [[CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics]]

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-01T18:50:15Z

Jlbucha4: Fixed Formatting of Links

__TOC__

==Background==
In Project E2504, you implemented a way for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned, such as Program 2.

==Project Overview==
Extend the system developed in Project E2504 to work for projects with topics, where the mentor is preassigned to the topic. Additionally, when a team chooses a topic, the mentor should then become the mentor for the team.

==Implementation==
TOTO: Add Implementation

==File Modified==
TODO: Add Files Modified

==Testing==
===Test Plan===
TODO: Add Test Plan
===Test Coverage===
TODO: Add Test coverage

==Relevant Links==
* Github: https://github.com/jmwinte3/expertiza
* E2504 Wiki: https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Project Description: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-01T18:49:52Z

Jlbucha4: Updated Links

__TOC__

==Background==
In Project E2504, you implemented a way for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned, such as Program 2.

==Project Overview==
Extend the system developed in Project E2504 to work for projects with topics, where the mentor is preassigned to the topic. Additionally, when a team chooses a topic, the mentor should then become the mentor for the team.

==Implementation==
TOTO: Add Implementation

==File Modified==
TODO: Add Files Modified

==Testing==
===Test Plan===
TODO: Add Test Plan
===Test Coverage===
TODO: Add Test coverage

==Relevant Links==
Github: https://github.com/jmwinte3/expertiza
E2504 Wiki: https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
Project Description: https://docs.google.com/document/d/1jjbqggRDiOHrxdsMlliY62JnP34bGTNHVWAZNz89kT8/edit?tab=t.0#heading=h.yeys674t35p3

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-01T18:22:36Z

Jlbucha4: Fixed Formatting of Testing

__TOC__

==Background==
In Project E2504, you implemented a way for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned, such as Program 2.

==Project Overview==
Extend the system developed in Project E2504 to work for projects with topics, where the mentor is preassigned to the topic. Additionally, when a team chooses a topic, the mentor should then become the mentor for the team.

==Implementation==
TOTO: Add Implementation

==File Modified==
TODO: Add Files Modified

==Testing==
===Test Plan===
TODO: Add Test Plan
===Test Coverage===
TODO: Add Test coverage

==Relevant Links==
TODO: Add links (Github, Wiki, Project Description, etc.)

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-01T18:21:46Z

Jlbucha4: Added Template to the page

__TOC__

==Background==
In Project E2504, you implemented a way for mentors to record their meetings with the teams they were mentoring. It worked for projects where mentors were automatically assigned, such as Program 2.

==Project Overview==
Extend the system developed in Project E2504 to work for projects with topics, where the mentor is preassigned to the topic. Additionally, when a team chooses a topic, the mentor should then become the mentor for the team.

==Implementation==
TOTO: Add Implementation

==File Modified==
TODO: Add Files Modified

==Testing==
* Test Plan
TODO: Add Test Plan
* Test Coverage
TODO: Add Test coverage

==Relevant Links==
TODO: Add links (Github, Wiki, Project Description, etc.)

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2527. Mentor-meeting management: assignments with topics

2025-04-01T18:09:24Z

Jlbucha4: Created page with "TODO: Create Wiki Page for Team Writeup"

TODO: Create Wiki Page for Team Writeup

CSC/ECE 517 Spring 2025

2025-04-01T18:09:04Z

Jlbucha4:

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-25T03:49:31Z

Jlbucha4:

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===
We have added tests for the teams controller, mailer model, and meetings controller that can be seen below.

[[File:Project2504MailerSpec.png]]
[[File:Project2504TeamSpec.png]]
[[File:Project2504ControllerSpec.png]]

With this, our implementations are covered and tested.

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

File:Project2504ControllerSpec.png

2025-03-25T03:49:02Z

Jlbucha4:

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-25T02:21:59Z

Jlbucha4: /* Testing and Validation */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===
We have added tests for the teams controller, mailer model, and meetings controller that can be seen below.

[[File:Project2504MailerSpec.png]]
[[File:Project2504TeamSpec.png]]

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-25T02:21:46Z

Jlbucha4:

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===
We have added tests for the teams controller, mailer model, and meetings controller that can be seen below.
[[File:Project2504MailerSpec.png]]
[[File:Project2504TeamsSpec.png]]

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

File:Project2504TeamSpec.png

2025-03-25T02:20:48Z

Jlbucha4:

File:Project2504MailerSpec.png

2025-03-25T02:20:11Z

Jlbucha4: Mailer Spec

== Summary ==
Mailer Spec

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-25T02:19:25Z

Jlbucha4: /* Testing and Validation */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===
We have added tests for the teams controller, mailer model, and meetings controller that can be seen below.

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:22:22Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:22:05Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png|thumb|750px|Screenshot of the Email Notification logic]]</center>

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:21:54Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png|thumb|500px|Screenshot of the Email Notification logic]]</center>

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:21:49Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png|thumb|100px|Screenshot of the Email Notification logic]]</center>

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:20:42Z

Jlbucha4: /* Testing and Validation */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===
Ensure all features, including notifications and meeting management, are thoroughly tested.

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:20:29Z

Jlbucha4: /* Refactor Existing Codebase */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===
Streamline logic for adding users/mentors and sending notifications. Refactor view code to improve readability and reusability.

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:20:04Z

Jlbucha4: /* Backend and Controller Updates */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===
Implement a new controller to handle Create, Read, Update, Delete (CRUD) operations for mentor meetings. Update models to manage mentor meetings and trigger notifications.

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:18:34Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles.

[[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:18:16Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles. [[File:Mentor_meetings_email_notification.png]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:17:34Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles. [[File:Mentor_meetings_email_notification.png Screenshot of the Email notification logic]]

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

CSC/ECE 517 Spring 2025 - E2504. Mentor-meeting management

2025-03-23T21:17:10Z

Jlbucha4: /* Email Notifications */

__TOC__

==Background==
Previously, mentors had to be manually assigned by reviewing team formations, a process that required frequent monitoring and manual intervention. The implementation of automatic mentor assignment significantly reduced this workload.

==Project Overview==
The mentor assignment system was introduced in 2023 to streamline the process of assigning mentors to teams within Expertiza, an open-source course management platform designed for collaborative learning in large Object-Oriented Programming assignments. The primary focus of this project is to enhance the mentor management system. Within Expertiza, mentors can be assigned to teams either manually or automatically. Automatic assignment is triggered when a team reaches more than 50% of its capacity.

== Challenges ==

* While the system successfully assigns mentors automatically, there is no functionality to notify teams and mentors via email when an assignment is made
** This feature needs to be implemented to ensure clear communication.

* The only available team listing is on the "Create Teams" page, where team members are displayed on separate lines, and mentors appear in an arbitrary position within the team structure.
** Improvements are needed to enhance clarity and usability in mentor assignment tracking.

== Tasks ==
=== Email Notifications ===
Create a way that notifies participants and mentors, by email, of when they have been assigned to a team.

=== Mentor Meeting Management ===
Dr. Gehringer expressed to us that the current view of mentor meetings took up too much space and proposed to us a mockup of how he would like the view to look, which can be seen below.
<center>[[File:MentorMeetingViewMockup.png|thumb|1000px|Mentor Meeting View Mockup]]</center>

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===
The Email Notification methods experienced a change to support SOLID Principles. Before, the code was not supporting the Single-Responsibility Principle, but now we have separated the parts of the 'add_member' method apart of the Team model. The current switch allows for an easier readability and understanding of code, while also following the SOLID Principles. [[File:Mentor_meetings_email_notification.png|thumb|1000px|Screenshot of the Email notification logic]]</center>

=== Mentor Meeting Management ===
The teams table for mentor meeting management was significantly enhanced with dynamic column manipulation, allowing users to add and remove meeting columns while preventing conflicts with scheduled meetings. Individual meeting deletion and improved reliability were implemented, along with a refactored meeting date display and input for better user experience. The table structure was optimized, incorporating editable meeting fields with a save feature, dynamic updates based on filter selections, and an actions column. To streamline column management, dropdowns were replaced with header buttons, a maximum of five meeting columns was enforced, and dynamic rendering was implemented based on participant data. The mentor logic and date column naming were corrected for clarity, and a destroy route for team meetings was added, ensuring a more efficient and user-friendly team management experience.
<center>[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]</center>

=== Backend and Controller Updates ===
The backend for mentor meeting management underwent significant restructuring to improve efficiency and maintainability. A dedicated destroy route for team meetings was implemented, along with a revised deletion process. The logic for determining mentored teams and displayed teams for mentors was refined, and the meetings table was refactored to utilize the Participants class, establishing a database relationship between mentored teams and meetings. The meetings-related logic was moved from the teams controller to a newly implemented meetings controller, which includes a filter function. An instructor table was added in paginated form, and meeting routes were standardized. The meetings controller was further enhanced with CSS styling and instance variable reorganization, culminating in the integration of @meetings into the Teams Controller model.

```

#POST /meetings
def create
@team = Team.find(params[:team_id])
@meeting = @team.meetings.new(meeting_params)
if @meeting.save
# TODO: Re-implement email notification for meeting creation
render json: { status: 'success', message: 'Meeting date added' }, status: :created
else
render json: { status: 'error', message: 'Unable to add meeting date', errors: @meeting.errors.full_messages }, status: :unprocessable_entity
end
end
'''

'''

#DELETE /meetings/:id
def destroy
puts "Team ID: #{params[:team_id]}"
puts "Meeting ID: #{params[:id]}"
puts "Meeting: #{@meeting.inspect}"
if @meeting.destroy
render json: { message: 'Meeting deleted successfully' }, status: :ok
else
render json: { error: 'Failed to delete meeting' }, status: :unprocessable_entity
end
end
'''

'''
resources :teams, only: %i[new create edit update] do
collection do
get :list
post :create_teams
post :inherit
get :delete
get :delete_all
get :bequeath_all
end
resources :meetings, only: %i[create destroy]
end
'''

=== Refactor Existing Codebase ===
This set of backend and frontend changes focuses on code cleanup, standardization, and compatibility improvements. Unnecessary whitespace was removed, and the database column "date" was renamed to "meeting_date" for clarity. The "get_dates" function was refactored to ensure compatibility with older Ruby versions. Table column names were converted to snake_case to adhere to Ruby naming conventions, and rendering partials were removed to resolve Turbo issues. Finally, an initial refactoring session was conducted with a Large Language Model (LLM) to further refine the code.

=== Testing and Validation ===

== Relevant Links ==
*Github Repository: https://github.com/jmwinte3/expertiza

== Team ==
===Mentor===

Ed Gehringer

=== Members ===

Jacob Winters
Alex Wakefield
John Buchanan

File:Mentor meetings email notification.png

2025-03-23T21:14:47Z

Jlbucha4: The shows the implementation of the mailer logic.

== Summary ==
The shows the implementation of the mailer logic.