Resume upload, search, and export currently store resumes with hard-coded file paths and search for them by looking for active users with a resume, then pulling the resumes one by one from the file system. This system may benefit from using the Resume model directly to simplify logic.
This change should only be done when the Resume model is fully created and user resumes are migrated into the model.
Files which include logic for handling resumes include:
Other files may exist that could require updating, but these are the most important ones.
Additionally, the User model currently includes the attribute resume_date, which should be removed and replaced with the last_upload attribute of the Resume model in all places where it is used.
Any changes to these files must ensure that only active users who have paid dues can upload resumes, only resumes of active users that meet the requirements may be exported or searched, and the resume book will only display resumes for active users that meet the requirements.
Resume upload, search, and export currently store resumes with hard-coded file paths and search for them by looking for active users with a resume, then pulling the resumes one by one from the file system. This system may benefit from using the Resume model directly to simplify logic.
This change should only be done when the Resume model is fully created and user resumes are migrated into the model.
Files which include logic for handling resumes include:
Other files may exist that could require updating, but these are the most important ones.
Additionally, the User model currently includes the attribute resume_date, which should be removed and replaced with the last_upload attribute of the Resume model in all places where it is used.
Any changes to these files must ensure that only active users who have paid dues can upload resumes, only resumes of active users that meet the requirements may be exported or searched, and the resume book will only display resumes for active users that meet the requirements.