Adaptive learning: Add learner profile

[N0W0RK]

Warning

This PR includes a migration! Do not deploy on testservers

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) and too complex database calls.
• I strictly followed the principle of data economy for all database calls.
• I strictly followed the server coding and design guidelines.
• I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
• I documented the Java code using JavaDoc style.

Motivation and Context

Based on #9448

Description

Added LearnerProfile and CourseLearnerProfile. Each user has a LearnerProfile and each user in an active (current semester and not a test course) course with learning paths has automatically a course learner profile.
The CourseLearnerProfile is also created when a user enrolls in a course with learning paths or learning paths get enabled. The profiles are deleted if the user unenrolls or is deleted.

This PR does not add any UI!

Steps for Testing

🚨 🚨 Local setup to verify database entries 🚨 🚨
Course with enabled learning paths and some students

1. Log in to Artemis
2. Check that the migration works and all existing users have a corresponding entry in the learner profile table
3. Check that the migration works and all existing users in the course with learning paths have a corresponding entry in the course learner profile table
4. Create a new user and check that they also get a new learner profile in the data base
5. Delete the course and check that the corresponding course learner profiles are deleted as well
6. Delete a user and check that the corresponding learner profile course learner profiles are deleted as well

Review Progress

Performance Review

• I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance even for very large courses with more than 2000 students.
• I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance even for very large courses with more than 2000 students.

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Performance Tests

• Test 1
• Test 2

Test Coverage

Server

Class/File	Line Coverage	Confirmation (assert/expect)
LearnerProfileApi.java	85%	✅
CourseLearnerProfile.java	28%	✅
LearnerProfile.java	40%	✅
LearnerProfileRepository.java	100%	✅
LearningPathService.java	90%	✅
CourseLearnerProfileService.java	100%	✅
LearnerProfileService.java	100%	✅
User.java	90%	✅
UserRepository.java	87%	✅
CourseService.java	93%	✅
UserScheduleService.java	91%	✅
UserCreationService.java	91%	✅
UserService.java	89%	✅
CourseResource.java	89%	✅

LearnerProfile.java and CourseLearnerProfile.java currently only represent Datastructures without any logic. Coverage will be higher after subsequent PRs introduce logic and more tests.

Summary by CodeRabbit

Based on the comprehensive summary of changes, here are the updated release notes:

• New Features

  • Added learner profile functionality for users.
  • Introduced course-specific learner profiles.
  • Enhanced user management with profile creation and deletion.
  • Implemented methods for managing learner profiles via a new API.

• Improvements

  • Integrated learner profiles with course enrollment.
  • Added support for tracking learning paths and user learning goals.
  • Implemented lazy loading for learner profiles.

• Technical Enhancements

  • Created new repositories and services for managing learner profiles.
  • Updated user management processes to include profile creation.
  • Expanded test coverage for new profile-related functionality.

These changes introduce a more comprehensive user profile system, allowing for more personalized learning experiences and better tracking of user progress across courses.

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

src/test/java/de/tum/cit/aet/artemis/atlas/profile/LearnerProfileArchitectureTest.java (1)

28-33: Use more descriptive constant names.

The constant names could be more descriptive to better convey their purpose in the test scenarios.

-    private static final String TEST_PREFIX = "learningpathintegration";
-    private static final int NUMBER_OF_STUDENTS = 1;
-    private static final String STUDENT1_OF_COURSE = TEST_PREFIX + "student1";
+    private static final String LEARNING_PATH_TEST_PREFIX = "learningpathintegration";
+    private static final int INITIAL_STUDENT_COUNT = 1;
+    private static final String ENROLLED_STUDENT_USERNAME = LEARNING_PATH_TEST_PREFIX + "student1";

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 27fdfb5 and b6bcda4.

📒 Files selected for processing (1)

• src/test/java/de/tum/cit/aet/artemis/atlas/profile/LearnerProfileArchitectureTest.java (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/test/java/de/tum/cit/aet/artemis/atlas/profile/LearnerProfileArchitectureTest.java (1)

Pattern src/test/java/**/*.java: test_naming: descriptive; test_size: small_specific; fixed_data: true; junit5_features: true; assert_use: assertThat; assert_specificity: true; archunit_use: enforce_package_rules; db_query_count_tests: track_performance; util_service_factory_pattern: true; avoid_db_access: true; mock_strategy: static_mocks; context_restart_minimize: true

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: client-style
• GitHub Check: server-tests
• GitHub Check: client-tests-selected
• GitHub Check: server-style
• GitHub Check: client-tests
• GitHub Check: Analyse
• GitHub Check: Build and Push Docker Image
• GitHub Check: Build .war artifact

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (2)

src/test/java/de/tum/cit/aet/artemis/atlas/profile/LearnerProfileIntegrationTest.java (2)

14-19: Make test data prefix more specific to the test scenario.

Consider renaming TEST_PREFIX to something more specific like LAZY_LOADING_TEST_PREFIX to better reflect the test scenario.

---

20-29: Document test scenario and optimize user creation.

The setup creates users that aren't used in the current test cases. Consider:

1. Adding JavaDoc to document the test scenario.
2. Creating only the users needed for the current test.

 @BeforeEach
+/**
+ * Sets up the test scenario by creating:
+ * - One student (STUDENT1_OF_COURSE)
+ * - Two additional users not in the course
+ * Creates learner profiles for all users with the test prefix
+ */
 void setupTestScenario() {
     userUtilService.addUsers(TEST_PREFIX, NUMBER_OF_STUDENTS, 1, 1, 1);

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b6bcda4 and 461973f.

📒 Files selected for processing (1)

• src/test/java/de/tum/cit/aet/artemis/atlas/profile/LearnerProfileIntegrationTest.java (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/test/java/de/tum/cit/aet/artemis/atlas/profile/LearnerProfileIntegrationTest.java (1)

Pattern src/test/java/**/*.java: test_naming: descriptive; test_size: small_specific; fixed_data: true; junit5_features: true; assert_use: assertThat; assert_specificity: true; archunit_use: enforce_package_rules; db_query_count_tests: track_performance; util_service_factory_pattern: true; avoid_db_access: true; mock_strategy: static_mocks; context_restart_minimize: true

⏰ Context from checks skipped due to timeout of 90000ms (9)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: client-tests-selected
• GitHub Check: client-style
• GitHub Check: client-tests
• GitHub Check: server-style
• GitHub Check: server-tests
• GitHub Check: Build and Push Docker Image
• GitHub Check: Analyse
• GitHub Check: Build .war artifact

🔇 Additional comments (1)

src/test/java/de/tum/cit/aet/artemis/atlas/profile/LearnerProfileIntegrationTest.java (1)

1-12: LGTM! Class structure follows best practices.

The class is well-organized with proper package placement, necessary imports, and follows the integration test naming convention.