If you can, please help.
If you will advise me to buy an ATS system, save your energy on typing. That wouldn’t be the answer to my question. I am considering buying an ATS if this becomes too complicated…
Thanks!
If you want them searchable, I’d suggest a Text field rather than a Blob. You can use a Blob field, if you insist, for the raw file that the applicant submitted; but it would be better to store the file in the filesystem and just keep a path in the database.
It’s probably also worthwhile to add other fields, such as the applicant’s name; the date they submitted their resume; the position(s) they competed for, and so on.
I would create multiple tables, this process is called “normalization”.
TABLE_RESUME
—————–
r_id
submitter
date
time
TABLE_USER
——————–
r_id
name
address
phone
more personal data…
skill_id
work_id
TABLE_SKILL
—————–
r_id
skill_id
skill
TABLE_WORK
—————–
r_id
work_id
jobname
location
startdate
enddate
startwage
endwage
This is the correct way to do database programming. It allows all the data to be searched/changed and added with ease.
Here’s a good solution: store the resumes in a text field like nvarchar(2000), and use Full-Text search for searching them. Full text search is very powerful and flexible, but can be difficult to configure. This will also remove the formatting for the resumes, so what you do is, keep the resumes on disk somewhere and keep a path to them in the database. That way, when you return matches from your full-text search, you can open the original resume document to view it from the document source.