[Feature Request] Resume Upload

[stevenmqnguyen]

Overview

We want to allow users to upload their resumes from their profiles. The existing implementation from portal v1 will provide some logic along with some updates and provide a user interface. The client will request a signed url through graphql, which will produce a signed URL through resolver / service and return to client.

Tasks

• Create get / put signed URL within graphql service
• Create resolver for producing Signed url
• Update filenames to be <userId>.pdf
• Add button to user's profile to upload file
• Add option to view uploaded file
• Add option to delete uploaded file
• Display use & privacy info
• Document

Supplemental Information

• Portal v1 resume upload implementation
• Tailwind headless ui
• Signed URLs
• Example implementation of Signed URL
• @google-cloud/storage

[NickBurnett]

Is <userId> the user's auth stub?

[stevenmqnguyen]

Is <userId> the user's auth stub?

Take a look at this NextAuth model doc. The userId is the primary key / document id. Any better implementation suggestions are welcome. Admins will need to be able to sort the resumes by role, name file with the users name, and zip & download all or by various roles / unions of roles.

[NickBurnett]

Take a look at this NextAuth model doc. The userId is the primary key / document id. Any better implementation suggestions are welcome. Admins will need to be able to sort the resumes by role, name file with the users name, and zip & download all or by various roles / unions of roles.

Primary Key works well I think. I think at the very least it would be beneficial to keep UUIDs consistent across user data.