Open
Conversation
…R-126-Admin-Outreach
…) and indexes for outreach targeting.
…as and register in getModelService.
…nce for dynamic audiences.
…nOutreachService for send flow and analytics.
…dmin/outreach and /me.
…/backgroundColorHex so color picker stays in sync.
|
|
||
| ### Solution | ||
|
|
||
| The Admin Outreach System allows administrators to precisely target students based on attributes such as major, year, enrollment status, and program. |
Collaborator
There was a problem hiding this comment.
these are good attribute based targets
Comment on lines
+69
to
+122
| Admin Outreach System | ||
|
|
||
| Overview: | ||
| Problem | ||
| Administrators often struggle with communicating with the right students effectively. Currently, they rely on mass emailing, which results in cluttered inboxes, students ignoring important announcements, and messages not reaching the right people. For example, an admin might just want to contact the class of 2027 computer science students only. | ||
| Solution | ||
| The Admin Outreach System allows administrators to precisely target students based on attributes, major, year, enrollment status, program, etc. | ||
|
|
||
| Goals: | ||
| Have targeted communication to specific student groups | ||
| Reduce inbox clutter | ||
| Improve students engagement | ||
|
|
||
| General Features | ||
| Student Targeting: | ||
| Administrators select recipients using filters such as: | ||
| Major / department | ||
| Graduation year | ||
| Program type (undergraduate, graduate, etc.) | ||
| Enrollment status | ||
| Dynamic | ||
| As the student attribute changes, updates automatically | ||
|
|
||
| Philosophy Behind the System | ||
| Prioritizes relevant messages instead of mass emailing | ||
| Asking what type of student should receive the message | ||
| All targeting and messages should be done with clear UI controls | ||
|
|
||
|
|
||
|
|
||
| Inspiration from Existing Software | ||
| Submitty, Blackboard: Structured announcements for defined groups | ||
|
|
||
|
|
||
|
|
||
|
|
||
| Breakdown Into Actionable Tasks | ||
| Planning: | ||
| students attributes | ||
| Admin roles and permissions | ||
| Figure out how to get data | ||
| Backend | ||
| Database schema | ||
| Frontend | ||
| Admin UI | ||
| Student email feed | ||
| Delivery | ||
| Integrating email and notification | ||
|
|
||
|
|
||
|
|
||
| Bugs found while creatin events: | ||
| Changin time and location after making an event | ||
| For qr code when coping and pasting the hex color the little color box doesnt reflect the right color |
|
|
||
| ### Planning | ||
|
|
||
| - Define student attributes |
Collaborator
There was a problem hiding this comment.
what kind of attributes? it's important for backend set up for schemas
|
|
||
| ### Frontend | ||
|
|
||
| - Build the admin UI |
Collaborator
There was a problem hiding this comment.
what would that include? create messages? different filters, like major or year?
…R-126-Admin-Outreach
…R-126-Admin-Outreach
Collaborator
nicolelin322
left a comment
nicolelin322
left a comment
There was a problem hiding this comment.
overall, I would like to see more parameters declarations and in all backend route just to make it more readable.
Comment on lines
+47
to
+49
| const page = Math.max(1, parseInt(req.query.page) || 1); | ||
| const limit = Math.min(50, Math.max(1, parseInt(req.query.limit) || 20)); | ||
| const skip = (page - 1) * limit; |
Collaborator
There was a problem hiding this comment.
declare all in one line for readability please (example const {page, limit, skip}
Collaborator
There was a problem hiding this comment.
also, do we really need all 3 pagination parameters (would just two suffice)
| */ | ||
| router.get('/audiences/:id', async (req, res) => { | ||
| try { | ||
| const { OutreachAudience } = getModels(req, 'OutreachAudience'); |
Collaborator
There was a problem hiding this comment.
please clearly declare parameters
Collaborator
There was a problem hiding this comment.
try not to reference directly
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.