Hi,

I am designing a system for my company to get employee resumes via the Web,
rather than paper. All resumes now go into a mySQL DB, which can be
searched by HR (at least that's the theory :) 

Here are the scripts I will be writing.

User pages
----
Listings
Descriptions
Application form

Admin pages
-----------
Add listing
Edit listing
Delete listing
Search for matches

---

Now, job description consists of:

job code
department
desig
location
desc
qualification
contact
posted on
salary range (?)

Application form consists of:

personal information:
        job code and name
        first name
        last name
        age 
        sex 
        addr 1
        addr 2
        city
        state
        zip
        country
        email
        web site
        primary phone
                country code
                city code
                local area
                type - home/work/cell
        sec. phone
                SAA
        willing to relocate??

employment history (last 3 jobs)
        start
        end
        employer
        job title
        field of work
        responsibilities
        is current employer?

skills
        skill name
        years of experience

references
        contact person
        phone
        email

additional info
        free-form field

salary
        current monetary range
        current non-monetary benefits
        expected

type of employment
        trainee
        freelance
        full-time

would you like your resume to be shared with other departments?

My questions:

For job listings - how do I design the tables? Can I dump all job listings
into a single table, and all applications/resumes into another one? Or
should they be normalized?

If normalized - how much? For example, in a listing, I have job code,
department, location, salary range, etc. - should I have separate tables
for each of these? Like

jcode   dept    loc
1       213     2
2       77      3

where dept and loc are FKs to other tables? Or is this taking it too far? 

Same for application form. All this information that I am getting - should
I put into a single table, or split across separate tables? I do plan to
search by differenet criteria later.

What about items in drop-downs? For example, if I have a drop-down for
salary ranges or countries - should this information come from a table, or
should I hard-code into the form itself? How do I make the decision as to
which is appropriate?

Any assistance much appreciated. TIA,

Vikram
--
Give a homeless man a bundle of firewood, and he'll be warm for one day.
Douse him with a gallon of gasoline and set him on fire, and he'll be warm
for the rest of his life!

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to