Adithya Popularity By Timeline Chart Backend

[adithya-6101]

Description

This backend PR implements the Popularity Timeline chart for Job Posting Page Analytics.
It introduces a new popularityTimeline model and APIs to fetch monthly hits and applications for job postings, with filters for date range and job role.

Related PRS (if any):

This backend PR is related to the frontend PR Adithya Popularity By Timeline Chart Frontend.
To test this backend PR, checkout the corresponding frontend PR.

Main changes explained:

• Added popularityTimeline.js model to store:
  • Month (e.g., "January 2024")
  • Hits count
  • Applications count
  • Role (for filtering)
  • Timestamp (for sorting & filtering)
• Added new routes in popularityTimelineRoutes.js:
  • GET /popularity?range=12months — fetch last 12 months data
  • GET /popularity?roles=[role1,role2] — filter by roles
  • GET /popularity?start=YYYY-MM&end=YYYY-MM — fetch custom date ranges
• Aggregates data by month and role for frontend consumption.
• Implements efficient database indexing for faster queries.

How to test:

1. Checkout the branch adithya_impl_popularity_timeline_backend.
2. Run npm install to install dependencies.
3. Run the backend locally with npm run dev.
4. Test the API endpoints using Postman:
   • GET http://localhost:4500/api/popularity?range=12months
   • GET http://localhost:4500/api/popularity?roles=["Backend Developer", "Full Stack Developer"]
   • GET http://localhost:4500/api/popularity?start=2024-03&end=2025-09
5. Verify that the response includes hits and applications.
6. Optionally, test with the frontend to confirm chart updates correctly with filters.

Screenshots or videos of changes:

Note:

• This PR focuses only on backend logic and API endpoints.
• Frontend visualization and chart rendering are handled in the related frontend PR.

[akshith312]

Tested the PR locally. All the end points return the desired results with different parameters.

[harshavarma29]

I have tested the PR for the below listed scenarios, it is working fine. However, I have request changes in the related Frontend PR.

1. Range fitler:
   

2. Role filter:
   

3. Custom range filter:
   

[one-community]

Thank you all, merging!