Notification System for Faculty Members

[ChaitanyaGudimalla]

Estimated effort: 15 hours Description: As a faculty member, I want to be notified of new questions or discussions posted by students within the Q&A board, so that I can promptly respond and provide assistance when needed.

Justification: A notification system for faculty members ensures timely responses to student inquiries, enhancing the learning experience. It facilitates effective communication between faculty and students, fostering a supportive and responsive academic environment.

Acceptance Criteria:

1. Faculty members should receive notifications for new questions or discussions posted by students in the Q&A board.
2. Notification alerts should be delivered via email and/or within the NodeBB platform interface.
3. Faculty members should have the option to customize their notification preferences, such as frequency (immediate, daily digest) and notification channels (email, platform notifications).
4. Notification alerts should include relevant details about the new question or discussion, such as the title, content, and author.
5. Notifications should be clear, concise, and actionable, enabling faculty members to quickly understand the nature of the inquiry and decide on a response.
6. Faculty members should have the ability to mark notifications as read or unread, allowing them to manage their notification inbox effectively.
7. The notification system should be scalable to accommodate a growing number of faculty members and student interactions.

Dependencies:

1. Integration with the existing user authentication and permission management system of the NodeBB project.
2. Access to the necessary APIs or services for sending email notifications.
3. Coordination with the frontend team to ensure that notification alerts are displayed correctly within the NodeBB platform interface.
4. Testing and validation of the notification system across different environments and user scenarios.
5. Review and approval from project stakeholders before deployment to the production environment.

[Aishwaryasri15]

Initially, we might have created the notification system for faculty members as a single feature issue on GitHub without recognizing the potential for breaking it down into smaller sub-tasks. However, as we became occupied with other feature implementations, we realized that the notification system could be a significant task requiring time and resources. Consequently, we decided to plan its implementation as a stretch goal. In the later stages, once we have more bandwidth available, we intend to revisit the issue and create sub-tasks to break down the implementation into manageable steps. This approach allows us to prioritize higher-priority features initially while still ensuring that we can address the notification system effectively as part of our project roadmap.