BCStudentSoftwareDevTeam / BCStudentSoftwareDevTeam/celts

Enhance CELTS Labor Position History in User Profile

Open
#1,805 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1
Forks
15
Avg merge
5d 39m
Merged PRs (30d)
8

Description

Description

In an individual User Profile, users can navigate through:

Student Search → Profile → CELTS Labor

The CELTS Labor section currently displays a list of the student's labor positions and associated terms, but the information shown is limited and does not clearly represent the student's labor history or career growth.

Update this section so that each labor position displays more complete information from the student's Labor Status Form (LSF) history.

The following information should be included:

Display the WLS associated with each labor position so that changes in responsibility or career growth can be seen over time.
If the student has a secondary labor position, display that position as well.
If multiple LSFs exist within the same academic year, display each position separately.
For example, a student may have two records for AY 2025–26 because they changed labor positions or moved to a different department during the year.
These should not appear as one vague or duplicate academic-year entry.
Add an indication when multiple positions exist within the same academic year so that the transition between positions is clear.
Order the labor history chronologically using the labor start date and labor end date, if those dates provide a reliable ordering.

The existing function updateCeltsLaborFromLsf should be useful when implementing this change. Its docstring and related logic likely identify the LSF fields used to populate CELTS Labor records and may already contain some of the information needed for this display.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with updateCeltsLaborFromLsf and its docstring, then trace where CELTS Labor records are rendered in the User Profile. Verify the LSF fields for WLS, secondary positions, dates, and same-year records; done means distinct, clearly marked entries appear in chronological order.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.