Group, Groupmember, groupTutorial, progress, solution, heartbeat

[Lav-Sen]

Summary

This PR introduces Group functionality for Blockly, enabling teachers to create and manage groups and allowing students to join them using an access code.

It also adds support for:

• assigning tutorials to groups
• tracking student progress
• publishing Blockly solutions
• tracking user activity (heartbeat / online status)

The implementation includes new API endpoints and corresponding database schemas.

---

Features

Groups

• Create and manage groups
• Retrieve group details
• Update group name
• Archive or delete groups

Group Members

• Join groups via an access code
• Leave groups
• Teachers can view and remove members

Group Tutorials

• Assign tutorials to groups
• Remove tutorial assignments
• Retrieve tutorials available to students
• Manage tutorial release status

Progress Tracking

• Track student progress in tutorials
• Store currentPage, totalPages, and completion state
• Track lastSeen activity for online status

Solutions

• Students can publish their Blockly solutions
• All group members can view published solutions
• Solutions can be withdrawn

Heartbeat / Online Status

• Track user activity via lastSeen
• Online status is derived from recent activity

---

Added API Endpoints

Groups

• POST /api/groups – Create a group (teacher)
• GET /api/groups – Retrieve teacher's groups
• GET /api/groups/dashboard – Retrieve teacher's groups
• GET /api/groups/:groupId – Get group details (member)
• PATCH /api/groups/:groupId – Update group name (teacher)
• PATCH /api/groups/:groupId/archive – Archive group (teacher)
• DELETE /api/groups/:groupId – Delete group (teacher)

Join / Leave Groups

• POST /api/groups/join – Join a group via access code (student)
• DELETE /api/groups/:groupId/leave – Leave a group (student)

Group Members

• GET /api/groups/:groupId/members – Retrieve all members (teacher)
• DELETE /api/groups/:groupId/members/:userId – Remove member (teacher)

Tutorials

• GET /api/groups/:groupId/tutorials – Retrieve released tutorials (students)
• GET /api/groups/:groupId/tutorials/manage – Retrieve tutorials with release status (teacher)
• POST /api/groups/:groupId/tutorials – Assign tutorial to group (teacher)
• DELETE /api/groups/:groupId/tutorials/:tutorialId – Remove tutorial assignment (teacher)

Solutions

• GET /api/groups/:groupId/solutions – Retrieve all published solutions
• POST /api/groups/:groupId/solutions – Publish a solution
• DELETE /api/groups/:groupId/solutions/:solutionId – Withdraw a solution

Progress

• PUT /api/groups/:pseudoUserId/progress – Retrieve all published solutions

Status

• GET /api/groups/:pseudoUserId/heartbeat – Retrieve all published solutions

---

Database Schema

groups

• _id
• name
• accessCode (unique)
• teacherId
• archived
• createdAt
• updatedAt

groupMembers

• _id
• groupId
• userId
• role (teacher | student)
• joinedAt

groupTutorials

• _id
• groupId
• tutorialId
• assignedAt
• assignedBy

progress

• _id
• userId
• groupId
• tutorialId
• currentPage
• totalPages
• lastSeen
• updatedAt

pseudoUsers

• _id
• name
• nickname
• groupId
• sessionToken
• onlineStatus
• lastSeen
• createdAt

solutions

• _id
• userId
• groupId
• tutorialId
• blocklyXml
• publishedAt

---

Notes

• Authentication and authorization are enforced based on teacher and student roles.
• Online status is derived from the lastSeen timestamp.
• Solutions store the Blockly workspace as blocklyXml.

[Thiemann96]

From code review all in all looks solid! Please see the attached comments for improvements.

In Summary

• keep track of code consistency across your implementation
• if you write excessive docs, please make sure they are correct. otherwise just remove them (though a little bit of documentation what a function does is nice but you dont need to document every exception to the rule ;) )
• remove logs from development

[Thiemann96]

shouldnt this be checked if it returns true and if it returns true respond with a success response?

[Thiemann96]

reply to my commet above:

like you do here