How sriraghavi22/careercatalyst works
Entities (Collections)
From your folder “backend copy/models” you have four core entities:
• Individual
• Institution
• Organization
• Job
Attributes for Each Entity
(Use your actual Mongoose schema definitions to fill in exact fields—these are example placeholders.)
• Individual
– _id (ObjectId, PK)
– fullName: String
– email: String
– passwordHash: String
– resumeUrl: String
– createdAt, updatedAt
• Institution
– _id (ObjectId, PK)
– name: String
– address: String
– contactEmail: String
– createdAt, updatedAt
• Organization
– _id (ObjectId, PK)
– name: String
– description: String
– contactEmail: String
– createdAt, updatedAt
• Job
– _id (ObjectId, PK)
– title: String
– description: String
– requirements: [String]
– postedDate: Date
– institutionId: ObjectId (FK → Institution)
– createdByOrgId: ObjectId (FK → Organization)
– createdAt, updatedAt
Relationships and Cardinalities
• Institution 1–N Job
– One Institution can post many Jobs.
• Organization 1–N Job
– One Organization can create many Jobs.
• Institution 1–N Individual (optional)
• Many-to-Many (Individual ↔ Job) via “matches”
– Your resume_job_matcher.py implies you store match results:
• matchCollection
– individualId: ObjectId (FK → Individual)
– jobId: ObjectId (FK → Job)
– matchScore: Number
Final Steps
• Inspect each *.js model file to capture any extra fields or indexes.
• Timestamps or embedded sub-documents if present (e.g., resume parsed data).
• Collections logically: group “User” collections on one side, “Job” collections on the other.
• Review and refine with the team to ensure it matches the actual database.