BCStudentSoftwareDevTeam / BCStudentSoftwareDevTeam/lsf
CELTS Labor import not updating new positions
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
It appears that the feature that imports CELTS labor positions from LSF is not working. For example, user `ramireza2` had a 2024-2025 position with CELTS.
If I run `updateCeltsLaborFromLsf()` in production, I can see the data returned by the production LSF instance:
```
'B00794020': [
{'jobType': 'Primary', 'laborEnd': '2025-05-04', 'laborStart': '2024-08-20', 'positionTitle': 'Hispanic Outreach Team Member', 'termCode': 202400, 'termName': 'AY 2024-2025', 'wls': '3'},
{'jobType': 'Primary', 'laborEnd': '2025-12-13', 'laborStart': '2025-08-19', 'positionTitle': 'Hispanic Outreach Associate', 'termCode': 202511, 'termName': 'Fall 2025', 'wls': '4'}],
```
However, the User Profile stays the same, and the new position is not saved.
In order to test this in development, you need to run both LSF and CELTS, and add the ip address of the lsf instance into your celts config. The script `app/scripts/import_labor_from_lsf.py` will pull the CELTS labor students into CELTS.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.