Bulk Resume Export

[Kyle Rubenok]

A problem that comes up every year is exporting the big pile of resumes to sponsors. As it stands, the resumes are named after the hackerID of the submitter (I think it's the hackerID, could be the accountID too).

This is good from a backend perspective to have them normally named in a strictly unique way, but it does make exporting difficult. Creating a route to bulk-export the attached resumes for a search query of hackers (the search could be as simple as all hackers in a given year) and while exporting the PDFs, do one of the following:

• rename the PDFs to something human readable. (Pro: easiest to consume. Con: name conflicts are not improbably and it could get ugly weird to append things like NameName2.pdf)
• Keep the PDFs named by some ID string, but also export a CSV of the rest of their application data where one of the columns is the file name of their PDF. (Pro: that CSV gives recruiters a way to reason over a big pile of resumes and apply further filters to which ones they want to review. Con: the CSV is critical to make any sense of the resumes)

I think I like the second option better.

[Pierre Theo Klein]

The application already has the name of the PDF. The name of the PDF is the timestamp followed by the hacker ID.