Expertiza_Wiki - User contributions [en]

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

2025-04-16T22:38:14Z

Jmwinte3:

__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.

==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-16T22:28:42Z

Jmwinte3:

__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.

==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.

===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.

===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] - To add the field for selecting a mentor when adding a topic manually.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb] - To display mentor information for an individual topic.

==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-16T22:28:12Z

Jmwinte3:

__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.

==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.

===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.

===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] - To add the field for selecting a mentor when adding a topic manually.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/sign_up_sheet/_topic.html.erb views/sign_up_sheet/_topic.html.erb] - To display mentor information for an individual topic.

==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-16T22:24:22Z

Jmwinte3: Undo revision 163986 by Jmwinte3 (talk)

__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.

==Implementation==
====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing 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. Its 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. For ECE 517 these projects would be the last two 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 which was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team 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 of any team they are on.

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are assigned, there needs to be a minor change to the way that topics are imported into expertiza. There should be an optional field that when included associates a mentor with a topic. This will requiring a modification to both the way that topics without associated mentors are imported and the option to import topics with mentors. There should still be a way to edit the mentor manually as well once the topic is imported with or without a mentor

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

[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding an individual topic and assigning a mentor to it.]]

[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely to support importing mentor-related data.]]

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

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

[[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.]]

When project topics are imported (from the Topics tab of the assignment “Import topics” at the bottom of the page) there must be an optional field for mentor
At the bottom of this page for example http://152.7.178.121:8080/assignments/1028/edit

just as is done now when the team reaches half strength.

this is happening within the mentor_management model here:
#https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43

====Database====
We will be implementing the same database as 'teams_users' for our project, specifically using duty_id for assignments of mentors.

==Files That May Be Modified==
Models:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam]
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic]

Controller:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb]

Views:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit.html.erb views/assignments/edit/_topics.html.erb]
#[https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb#L2 views/import_file/start]
#[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]
#[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]
#[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]
#[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]
#[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]
==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, not directly with teams. Each of these cases will have multiple tests to ensure the proper functionality when there is both a failure and a success. The topics include:

Storing Mentors with Topics:
Ensuring that topics can hold information about their assigned mentors.

Assigning Mentors During Topic Sign-up:
Confirming that when a team chooses a topic, the topic's mentor is automatically assigned to that team.

Assigning Mentors when Teams Reach Half Strength: Ensuring that the existing logic for intelligent assignments still applies.
Displaying Mentor Information: Validating that team views accurately show mentor information for mentored assignments and correctly hide it for non-mentored ones.

Importing Topics with Mentors: Checking that topics imported from files correctly capture and store mentor assignments.
Include mentors checkbox updates table: Confirm the table columns are properly updated to include the mentors in the topic

===Test Coverage===
Once we have created our tests and made the modifications to the expertiza repository that we have described we will include screenshots of what percentage of the tests fail and show that all functions will hopefully have some coverage in the tests

==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-16T22:23:00Z

Jmwinte3:

__TOC__

==Background==
In Project E2504, functionality was implemented allowing mentors to record meetings with the teams they mentor. This system worked effectively for projects where mentors were automatically assigned based on team formation (e.g., when a team reached half capacity). To enhance the mentor management capabilities, this project aims to integrate mentor assignments with the assignment topics system.

==Project Overview==
The primary goal is to extend the mentor management system to collaborate with assignment topics. Currently, when an assignment requiring topic selection is created, topics are often imported from a spreadsheet. This project will enhance this process by:

* Allowing pre-selected mentors (specified in the import spreadsheet) to be associated with specific topics in the assignment table.
* Automatically assigning the topic's designated mentor to a team as soon as that team selects the topic.

This will provide more granular mentor assignment capabilities, particularly suited for assignments where different teams work on different topics, each potentially requiring a specific mentor.

==Implementation==

===Checkbox to Alter Assignment Creation or Import===
During the topic import process (or potentially during manual assignment creation), a new checkbox option will be added.

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

* **Functionality:** This checkbox will toggle whether mentor information should be included during the topic import.
* **UI Update:** Selecting the checkbox will dynamically update the topic table view (e.g., reloading it via AJAX or similar) to display an additional column for mentor usernames.
* **Data Storage:** When saved, the associated mentor's username (or ID) will be stored as an additional attribute within the `sign_up_topic` data structure for each relevant topic.

It's important to note that this new feature is designed for topic-specific mentoring and '''will not affect''' the existing mechanism for projects where all teams work on the same project. In those cases, mentors will still be assigned based on team capacity (e.g., reaching half strength), managed separately. This feature specifically enables mentor association with distinct project topics, such as those used in the later Expertiza-based projects for courses like ECE 517.

===Automatic Assignment of Mentors===
Once the topics are set up with their associated mentors:

1. A team is created for the assignment.
2. The team selects a topic from the available list.
3. Upon successful topic selection, the system will automatically assign the mentor linked to that specific topic to the team.

[[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 topic selection.]]

This automatic assignment will be implemented by adding the designated mentor as a participant to the team roster and ensuring their `can_mentor` participant flag is set to true. Leveraging the logic from previous mentor management implementations, this flag ensures the participant is correctly identified and treated as a mentor for any team they are associated with.

*(Note: The existing logic for assigning mentors when teams reach half-strength, relevant for non-topic-specific assignments, resides in the `mentor_management` model, specifically around [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43 this section]).*

===Importing Topics===
To facilitate assigning mentors during setup, the topic import process needs modification.

[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely including the new checkbox option.]]

* **Optional Mentor Field:** The spreadsheet format used for importing topics will need to accommodate an optional column for mentor usernames.
* **Import Logic Update:** The import controller (`import_file_controller.rb`) will be updated to:
* Recognize the optional mentor column if present.
* Parse the mentor username.
* Associate the specified mentor with the corresponding topic during the import process, but only if the "Include Mentors" checkbox is selected.
* Gracefully handle imports where the mentor column is absent or the checkbox is unchecked (maintaining current functionality).

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

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

* **Manual Editing:** Even after import (with or without mentors), there should remain a way to manually edit topic details, including adding, changing, or removing the assigned mentor through the standard assignment/topic editing interface.

[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of manually adding or editing an individual topic and assigning a mentor to it.]]

*(Example page context for import: The import functionality is typically found at the bottom of the assignment edit page, e.g., `http://<your_expertiza_instance_address>/assignments/<assignment_id>/edit` under the "Topics" tab)*.

===Database===
No new database tables are anticipated. The association between teams and their assigned mentors will likely utilize the existing `teams_users` table structure, potentially leveraging the `duty_id` field or similar participant roles to signify the mentor relationship, consistent with current practices. The association between a topic and its potential mentor will be stored as an attribute of the `SignUpTopic` model/table.

==Files That May Be Modified==

* '''Models:'''
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam] (`signed_up_team.rb`) - Potentially modified to handle actions upon topic selection.
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic] (`sign_up_topic.rb`) - Will be modified to add the mentor attribute.
* '''Controllers:'''
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb] - Will be modified to handle the new import format and checkbox logic.
* Controllers related to topic selection/team formation might need adjustments for automatic mentor assignment.
* '''Views:''' (Related to assignments, topics, and import)
* [https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit.html.erb views/assignments/edit/_topics.html.erb] - Likely needs changes for displaying mentor column and manual editing.
* [https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb#L2 views/import_file/start.html.erb] - To add the new checkbox for mentor import.
* Sign up sheet partials may need updates to display or handle mentor info:
* [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]
* [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]
* [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]
* [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]
* [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]

==Testing==

===Test Plan===
The test plan focuses on verifying the correct handling of mentor assignments specifically linked to topics. Tests should cover both success and failure scenarios for each area:

* '''Storing Mentors with Topics:'''
* Ensure that topic data structures can correctly store and retrieve assigned mentor information (e.g., after manual assignment or import).
* Verify that topics without assigned mentors are handled correctly.
* '''Assigning Mentors During Topic Sign-up:'''
* Confirm that when a team selects a topic with an assigned mentor, that mentor is automatically added to the team roster with the correct role/permissions.
* Test scenarios where a topic has no mentor assigned – ensure no mentor is automatically added.
* '''Coexistence with Existing Mentor Assignment Logic:'''
* Ensure that the existing logic for assigning mentors based on team capacity (half-strength rule for non-topic assignments) remains unaffected and functional for relevant assignment types.
* '''Displaying Mentor Information:'''
* Validate that team views (e.g., team roster page) accurately display the assigned mentor's information when applicable (topic-based or capacity-based).
* Confirm that mentor information is appropriately hidden or not displayed for assignments/teams where no mentor is assigned.
* '''Importing Topics with Mentors:'''
* Check that topics imported using the new format (with the optional mentor column and checkbox selected) correctly capture and store mentor associations.
* Test imports where the mentor column is missing or the checkbox is unselected – ensure topics are imported without mentors as expected.
* Verify error handling for invalid mentor usernames in the import file.
* '''Import Checkbox UI Behavior:'''
* Confirm that toggling the "Include mentors" checkbox correctly updates the topic table display (adds/removes mentor column) on the import/setup page.

===Test Coverage===
After implementing the features and writing corresponding tests (e.g., RSpec unit/feature tests), we will run the test suite and report the coverage metrics. Screenshots documenting the test results (pass/fail counts) and coverage percentage will be provided, aiming for comprehensive coverage of the modified and new functions.

==Relevant Links==
* Project Repository: https://github.com/jmwinte3/expertiza
* Previous Project (E2504) Wiki: https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Spring_2025_-_E2504._Mentor-meeting_management
* Detailed 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-16T22:21:19Z

Jmwinte3:

__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.

==Implementation==
====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing 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. Its 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. For ECE 517 these projects would be the last two 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 which was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team 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 of any team they are on.

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are assigned, there needs to be a minor change to the way that topics are imported into expertiza. There should be an optional field that when included associates a mentor with a topic. This will requiring a modification to both the way that topics without associated mentors are imported and the option to import topics with mentors. There should still be a way to edit the mentor manually as well once the topic is imported with or without a mentor

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

[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|Interface view demonstrating the process of adding an individual topic and assigning a mentor to it.]]

[[File:Import_menu_changes.png|600px|thumb|Right|Screenshot highlighting modifications to the import menu, likely to support importing mentor-related data.]]

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

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

[[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.]]

When project topics are imported (from the Topics tab of the assignment “Import topics” at the bottom of the page) there must be an optional field for mentor
At the bottom of this page for example http://152.7.178.121:8080/assignments/1028/edit

just as is done now when the team reaches half strength.

this is happening within the mentor_management model here:
#https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43

====Database====
We will be implementing the same database as 'teams_users' for our project, specifically using duty_id for assignments of mentors.

==Files That May Be Modified==
Models:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam]
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic]

Controller:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb]

Views:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit.html.erb views/assignments/edit/_topics.html.erb]
#[https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb#L2 views/import_file/start]
#[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]
#[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]
#[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]
#[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]
#[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]
==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, not directly with teams. Each of these cases will have multiple tests to ensure the proper functionality when there is both a failure and a success. The topics include:

Storing Mentors with Topics:
Ensuring that topics can hold information about their assigned mentors.

Assigning Mentors During Topic Sign-up:
Confirming that when a team chooses a topic, the topic's mentor is automatically assigned to that team.

Assigning Mentors when Teams Reach Half Strength: Ensuring that the existing logic for intelligent assignments still applies.
Displaying Mentor Information: Validating that team views accurately show mentor information for mentored assignments and correctly hide it for non-mentored ones.

Importing Topics with Mentors: Checking that topics imported from files correctly capture and store mentor assignments.
Include mentors checkbox updates table: Confirm the table columns are properly updated to include the mentors in the topic

===Test Coverage===
Once we have created our tests and made the modifications to the expertiza repository that we have described we will include screenshots of what percentage of the tests fail and show that all functions will hopefully have some coverage in the tests

==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-16T22:19:52Z

Jmwinte3:

__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.

==Implementation==
====Checkbox to alter the Assignment Creation or Import====
Implementation will include adding a checkbox option when importing 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. Its 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. For ECE 517 these projects would be the last two 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 which was assigned to the topic will automatically be assigned to the team. This will be done by adding the mentor to the team 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 of any team they are on.

====Importing Topics====
In order for assignments/topics to have mentors assigned to them before teams are assigned, there needs to be a minor change to the way that topics are imported into expertiza. There should be an optional field that when included associates a mentor with a topic. This will requiring a modification to both the way that topics without associated mentors are imported and the option to import topics with mentors. There should still be a way to edit the mentor manually as well once the topic is imported with or without a mentor

[[File:mentor_checkbox_mockup.png|600px|thumb|Right|This shows where the checkbox will be added as an option to the existing form]]

[[File:Adding_individual_topic_with_mentor.png|600px|thumb|Right|This shows where the checkbox will be added as an option to the existing form]]

[[File:Import_menu_changes.png|600px|thumb|Right|This shows where the checkbox will be added as an option to the existing form]]

[[File:Imported_column_change.png|600px|thumb|Right|This shows where the checkbox will be added as an option to the existing form]]

[[File:Successfully_imported_topics_with_mentors.png|600px|thumb|Right|This shows where the checkbox will be added as an option to the existing form]]

[[File:Mentor_shows_up_within_teams.png|600px|thumb|Right|This shows where the checkbox will be added as an option to the existing form]]

When project topics are imported (from the Topics tab of the assignment “Import topics” at the bottom of the page) there must be an optional field for mentor
At the bottom of this page for example http://152.7.178.121:8080/assignments/1028/edit

just as is done now when the team reaches half strength.

this is happening within the mentor_management model here:
#https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43

====Database====
We will be implementing the same database as 'teams_users' for our project, specifically using duty_id for assignments of mentors.

==Files That May Be Modified==
Models:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb SignedUpTeam]
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb SignUpTopic]

Controller:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/controllers/import_file_controller.rb import_file_controller.rb]

Views:
#[https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit.html.erb views/assignments/edit/_topics.html.erb]
#[https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb#L2 views/import_file/start]
#[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]
#[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]
#[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]
#[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]
#[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]
==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, not directly with teams. Each of these cases will have multiple tests to ensure the proper functionality when there is both a failure and a success. The topics include:

Storing Mentors with Topics:
Ensuring that topics can hold information about their assigned mentors.

Assigning Mentors During Topic Sign-up:
Confirming that when a team chooses a topic, the topic's mentor is automatically assigned to that team.

Assigning Mentors when Teams Reach Half Strength: Ensuring that the existing logic for intelligent assignments still applies.
Displaying Mentor Information: Validating that team views accurately show mentor information for mentored assignments and correctly hide it for non-mentored ones.

Importing Topics with Mentors: Checking that topics imported from files correctly capture and store mentor assignments.
Include mentors checkbox updates table: Confirm the table columns are properly updated to include the mentors in the topic

===Test Coverage===
Once we have created our tests and made the modifications to the expertiza repository that we have described we will include screenshots of what percentage of the tests fail and show that all functions will hopefully have some coverage in the tests

==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

File:Mentor shows up within teams.png

2025-04-16T22:18:02Z

Jmwinte3:

File:Successfully imported topics with mentors.png

2025-04-16T22:17:26Z

Jmwinte3:

File:Imported column change.png

2025-04-16T22:16:58Z

Jmwinte3:

File:Import menu changes.png

2025-04-16T22:16:34Z

Jmwinte3:

File:Example import topic.png

2025-04-16T22:14:27Z

Jmwinte3:

File:Adding individual topic with mentor.png

2025-04-16T22:13:54Z

Jmwinte3:

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

2025-04-15T16:10:26Z

Jmwinte3:

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

2025-04-15T14:13:46Z

Jmwinte3:

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

2025-04-14T20:13:49Z

Jmwinte3:

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

2025-04-14T20:13:00Z

Jmwinte3:

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

2025-04-14T20:11:17Z

Jmwinte3:

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

2025-04-14T20:08:37Z

Jmwinte3:

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

2025-04-07T22:50:16Z

Jmwinte3: /* Test Plan */

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

2025-04-07T22:42:18Z

Jmwinte3:

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

2025-04-07T22:41:23Z

Jmwinte3:

File:Mentor checkbox mockup.png

2025-04-07T22:40:45Z

Jmwinte3:

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

2025-04-07T22:36:31Z

Jmwinte3: /* Files That May Be Modified */

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

2025-04-07T22:36:05Z

Jmwinte3:

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

2025-04-07T22:31:12Z

Jmwinte3: /* Test Coverage */

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

2025-04-07T22:29:59Z

Jmwinte3: /* Test Plan */

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

2025-04-03T19:15:24Z

Jmwinte3:

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

2025-04-03T19:14:53Z

Jmwinte3:

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

2025-04-03T19:10:54Z

Jmwinte3:

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

2025-04-03T19:10:31Z

Jmwinte3:

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

2025-04-03T19:09:31Z

Jmwinte3:

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

2025-04-03T19:09:22Z

Jmwinte3:

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

2025-04-03T19:09:12Z

Jmwinte3:

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

2025-04-03T19:09:02Z

Jmwinte3:

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

2025-04-01T22:49:42Z

Jmwinte3: /* Test Plan */

__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==

When project topics are imported (from the Topics tab of the assignment (“Import topics” at the bottom of the page) there must be an optional field for mentor
At the bottom of this page http://152.7.178.121:8080/assignments/1028/edit

just as is done now when the team reaches half strength.
Where does this happen?
https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43

TODO: Add Implementation

==Files That May Be Modified==
Models:
#SignedUpTeam: https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb
#SignUpTopic: https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb

Views:
#views/assignments/edit: https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit.html.erb
#views/import_file/start: https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb#L2

TODO: Add Files Modified

==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, not directly with teams. This includes:

Storing Mentors with Topics: Ensuring that topics can hold information about their assigned mentors.
Assigning Mentors During Topic Sign-up: Confirming that when a team chooses a topic, the topic's mentor is automatically assigned to that team.
Assigning Mentors when Teams Reach Half Strength: Ensuring that the existing logic for intelligent assignments still applies.
Displaying Mentor Information: Validating that team views accurately show mentor information for mentored assignments and correctly hide it for non-mentored ones.
Importing Topics with Mentors: Checking that topics imported from files correctly capture and store mentor assignments.

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-01T22:46:59Z

Jmwinte3: /* Implementation */

__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==

When project topics are imported (from the Topics tab of the assignment (“Import topics” at the bottom of the page) there must be an optional field for mentor
At the bottom of this page http://152.7.178.121:8080/assignments/1028/edit

just as is done now when the team reaches half strength.
Where does this happen?
https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/models/mentor_management.rb#L43

TODO: Add Implementation

==Files That May Be Modified==
Models:
#SignedUpTeam: https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/signed_up_team.rb
#SignUpTopic: https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/models/sign_up_topic.rb

Views:
#views/assignments/edit: https://github.com/jmwinte3/expertiza/blob/mentor_meetings/app/views/assignments/edit.html.erb
#views/import_file/start: https://github.com/jmwinte3/expertiza/blob/e566f88436d4c833111086631d0f30c76a5970a2/app/views/import_file/start.html.erb#L2

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-01T22:38:58Z

Jmwinte3: /* File That May Be Modified */

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

2025-04-01T22:38:50Z

Jmwinte3: /* File Modified */

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

2025-04-01T22:38:24Z

Jmwinte3:

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

2025-04-01T22:37:43Z

Jmwinte3:

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

2025-04-01T22:35:59Z

Jmwinte3:

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

2025-04-01T21:42:09Z

Jmwinte3: /* Implementation */

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

2025-03-23T21:02:13Z

Jmwinte3:

__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 ===

=== 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:01:34Z

Jmwinte3:

__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 ===

=== 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-23T20:58:11Z

Jmwinte3:

__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 ===

=== 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.

```ruby
# 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-23T20:57:42Z

Jmwinte3:

__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|Caption here]]</center>

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===

=== 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.

```ruby
# 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-23T20:57:22Z

Jmwinte3:

__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 ===

=== 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|300px|Caption here]]</center>

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===

=== 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|300px|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.

```ruby
# 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-23T20:55:23Z

Jmwinte3:

__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 ===

=== 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.
[[File:MentorMeetingViewMockup.png|thumb|1000px|Caption here]]

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===

=== 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.
[[File:Screenshot_2025-03-23_164914.png|thumb|1000px|Screenshot of the Mentor Meeting Management System within the teams table]]

=== 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-23T20:54:51Z

Jmwinte3:

__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 ===

=== 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.
[[File:MentorMeetingViewMockup.png|thumb|600px|Caption here]]

=== Backend and Controller Updates ===

=== Refactor Existing Codebase ===

=== Testing and Validation ===

== Implementation ==
=== Email Notifications ===

=== 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.
[[File:Screenshot_2025-03-23_164914.png|thumb|300px|Screenshot of the Mentor Meeting Management System within the teams table]]

=== 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