Thank you so much for the modules, they are wonderfully versatile, but they seem to rely heavily on other modules to work, so some more explanation would really help everybody out, especially on what other modules are needed and how to make them work with your job and resume modules.

If you laid out some recipes, it would help speed up the process for us who are new and help save you having to repeatedly answer questions related to the same thing.

I’m on D 5.7 with Job Search 5.2

Below are basic samples of what I found common in paid to view job sites, which I’d say many web masters and their employers are looking for.

Posting Resumes and Viewing Jobs as a Job Seeker:
Jobs that have a teaser and when the read more link is clicked unauthenticated users are taken to a link and signup with resume form and can pay to view/apply for
A) 1 job for a price
B) See jobs and can apply for jobs of choice for a day or week price
C) See jobs and can apply for jobs of choice for a monthly or yearly price
D) Job seekers can apply with their resume for free, but actual recruiter’s contact info is hidden.

Notes:
B) and C) can also sign up to have jobs in their category location, keywords emailed to them as soon as the jobs are published.
Not so basic: Teasers to go into a general newsletter which can be emailed and forwarded.

Posting Jobs and Viewing Resumes as a Recruiter:
Jobs can be posted
i) For free and Recruiter’s contact to be viewed by paid to view Job Seekers B) & C)
ii) For a price per job or per month and the teasers and read more links into a newsletter, which can be forwarded by email.

Viewing Resumes:
Done by Categories and Keywords:
Examples: skills, years experience, male or female, body type (for models and actors), location, type of equipment, driver’s license etc.
Resumes in chosen categories and keywords are sent to employers account or optional to their email in the form of teaser and link to read more.

Just suggesting.

Thanks

d

Comments

xamount’s picture

All these features are nice-to-have but may not be needed for every single career website. I guess it depends on how you want your site to function. The jobsearch module provides a very good base to start to build upon.

I have created a document page in trying to reduce the number of "how do I..." questions. Please see here:

http://drupal.org/node/341762

You can add to is as necessary.

Viewing Resumes:
Done by Categories and Keywords:
Examples: skills, years experience, male or female, body type (for models and actors), location, type of equipment, driver’s license etc.

This can be done using the Views module. Just create your View and expose the fields from your resume node type that you want to search by.

Because the jobsearch module does NOT create its own content type and leaves it up to the user to assign their own content type using the CCk module, it allows for full flexibilty using the Views module. So anything you can do using a view, can be done with the jobsearch module. Some people are having a hard time understanding this which is why I created the handbook page (link above) to help users.

xamount’s picture

Status: Active » Fixed

If anyone wants to write a site recipe, please add it to the jobsearch handbook page. I am closing this issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.