Job notification subscription feature

[dsychin]

• User should be able to specify filter parameters

  • keywords
  • location
  • salary

• Notify daily?

• Notification medium

  • web push
  • email
  • app push (our own standalone app or something like pushover?)

• [x] Create database schema

• [ ] Create system architecture

• [x] Create sequence diagram

• [ ] Implement

[dsychin]

Database

• notif_subscription

  • id
  • user_id
  • medium (1=email, 2=webpush)
  • filters (json) - can include salary ranges, location, etc in the future
  • keywords
  • provider
  • frequency (1=daily, 2=weekly, 3=monthly) - use daily only to start with?

• notif_subscriber

  • id
  • notif_subscription_id
  • mediium
  • target (json) - push endpoint, email, etc

• notif_queue

  • id
  • notif_subscription_id
  • job_id
  • medium
  • status (0=new, 1=sent)

• notif_log

  • id
  • user_id
  • sent_time
  • status (1=success, 2=failed)
  • notes

• need to keep track of push subscription IDs

General flow

1. User sets filters and subscribes to new job notifications
2. New batch program checks db for newly added jobs and add to notif_queue if job matches filters
3. Another batch that runs daily checks subscriptions and log for jobs that are due to run. Gets the list of jobs to notify about and include in notification.

User should be able to view the notif_queue in the web app so that they can see the list of jobs that they were notified for?

[dsychin]

sequenceDiagram
    Participant User
    Participant Jobbuzz
    Participant FCM

    User->>Jobbuzz: Subscribe to push/email notification
    Jobbuzz-->>User: OK
    loop Every hour
    Jobbuzz->>DB: Check for new jobs since last processed
    DB -->> Jobbuzz: Found new matching user's filters
    Jobbuzz->>SMTP: Send emails if subscribed
    SMTP-->>Jobbuzz: OK
    Jobbuzz->>FCM: Send webpush if subscribed
    FCM-->>Jobbuzz: OK
    Jobbuzz-->>DB: Log results
    DB-->>Jobbuzz: OK
    end