Proposed Drop Jobs Sprint

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
alexweber's picture

I've tagged a couple simple issues with low learning curves as candidates for an upcoming sprint.

As anyone that's been following this project knows, it's basically been just myself developing this and I can definitely use all the help I can get!

Even if you don't know how to code or aren't experienced, there's plenty that can be done in order to help!

I'd like to organize a sprint within the next week or so to help kill some lingering bugs and stabilize a release, if anyone's interested in contributing let me know!

Comments

Hi

kaizerking's picture

for any functional specs I can help you, on what should be there and what should not be there, coding ? Sorry I am dumb as rock in that.

I can write excellent documentation that's for sure, I am ready for that, as soon as we have good stable version i will start documentation.

PS: it is really hard for a single person to do this as a IT professional i would say this is not late to think about 'hresume' format as i said in drop jobs issue que
this will make a best recruitment package if you consider implementing the format.
at this stage it is easy as not much has been done to get an idea on what it is and who is using it please visit http://drupal.org/project/microformats where the author already worked on hcard and some other microformats he it seems not much difficult, this format is being used by linkedin.and some of the well known sites
Let me know your ideas on that

hresume format

alexweber's picture

This looks interesting, once the resume profile structure is complete and stable (almost there I think) we can look towards making it available in this format!

Regarding the documentation, that would be great! :)

one more point: We should

kaizerking's picture

one more point:
We should have total three roles
1. Employer
2. Employer_recruiter
3. Recruiter_employer
4. Candidate
1.Employer:
a) has subscriptions
b) holds number of accounts named "employer_recruiters" based on
subscription these accounts will be managed by employer
2. Employer_recruiter:
1.can post jobs
2.Search resumes
3.Has a profile

3.Recruiter_employer(freelancer):
a) has subscriptions based on
1.Industry sector
2.Number of employers he can work for (separate field collection field for adding each employer- remember ?issue tagged auto populate employer name?) this will come handy
3.Period
4.have profile (just to create user name and password by employer)
4.Candidate:
1. Has subscriptions(one subscription type will be free if any one wants to allow free registrations)
2. Has profile
What do you think about this?

I think this starts

alexweber's picture

I think this starts complicating things a bit!!!

On the one hand, I'm already anticipating situations you described such as:

  • A headhunting company has multiple accounts for users but needs a centralized place to manage everything.

  • Freelance recruiters that don't necessarily work for a specific company but for various organizations.

This is up for debate at the moment...

yes in a way it is complicate

kaizerking's picture

Yep, I know it is bit complicated ,but ultimately this is what should make drop jobs stand out from job portals crowd isn't it?
Not exactly head hunting companies I know even big manufacturing and chemicals, engineering companies names I cannot mention here are/will be interested in this kind of facilities,
I know big companies having accounts in monster like portals,
why i have been advocating in "hresume" formatting is example use case: if a candidate is selected from the portal, simply they can upload the same resume to their employee data base.
this is even very complicated isnt it? :)
but small step only needed to complete along journey, if agreed you can keep in TODO
after the dev is updated in repository with your latest commits, i'll try creating these features and pass them on to you NOT hresume part, the additional roles part :)

Agreed in parts! :) Please

alexweber's picture

Agreed in parts! :)

Please file an issue for hresume and anything else you would like to see.
It's easier if you open 1 issue for each feature request, to help keep things organized and help during development.

Thanks!!

site safety, security, prevention of over usage

kaizerking's picture

Some issues to be thought of:
Employer recruiters (as explained above) miss use their login credential for their own private use or lend login credentials to their friends, this will cause
1.illegal load on server and
2.This a loss to the employer
Any ideas ?

I think is very specific and

alexweber's picture

I think is very specific and something along the premium service or do it yourself lines. Definitely out of the project's initial scope! Sorry!

Create Dropjobs features as separate project

kaizerking's picture

Problem is each time you do a small commit i have to download full package

if you keep it separate and do commits against that I only need to download that and hit update

only update the main project if you do some major changes like adding new contrib modules other than drop job features.
what do you think.
I dont know how this development environment works , but will it up date the main project if you do changes in the drop job features project, if you have separately?

Topics

makhluk's picture

It is excellent for the user.

www.bankall.org

Finally! I had to scroll

Anonymous's picture

Finally! I had to scroll through hundreds of job post just to see this thread!

Let me know how I can help. I am new to this and would like to help any way I can as I will be implementing a stable version for our live site.

drop_jobs-7.x-1.0-alpha8 facing issues

kishorhase's picture

Hi
I have install drop_jobs-7.x-1.0-alpha8 of 10 Sep 2012. I am facing some errors... Let me know how I will get latest revision of code..

When I do the activity (Searching Jobs, Searching Resume, Update Resume, Update Job) I found the error on the screen like this

Notice: Undefined index: field_candidate_exp_field in content_taxonomy_autocomplete_validate_deny_new_terms() (line 106 of /opt/lampp/htdocs/drop_jobs/profiles/drop_jobs/modules/contrib/content_taxonomy/content_taxonomy_autocomplete.module).
Warning: Invalid argument supplied for foreach() in content_taxonomy_autocomplete_validate_deny_new_terms() (line 106 of /opt/lampp/htdocs/drop_jobs/profiles/drop_jobs/modules/contrib/content_taxonomy/content_taxonomy_autocomplete.module).
Notice: Undefined index: field_candidate_pref_occupation in content_taxonomy_autocomplete_validate_deny_new_terms() (line 106 of /opt/lampp/htdocs/drop_jobs/profiles/drop_jobs/modules/contrib/content_taxonomy/content_taxonomy_autocomplete.module).
Warning: Invalid argument supplied for foreach() in content_taxonomy_autocomplete_validate_deny_new_terms() (line 106 of /opt/lampp/htdocs/drop_jobs/profiles/drop_jobs/modules/contrib/content_taxonomy/content_taxonomy_autocomplete.module).
Language: this field cannot hold more than 1 values.
Notice: Undefined index: field_candidate_skills_skill in content_taxonomy_autocomplete_validate_deny_new_terms() (line 106 of /opt/lampp/htdocs/drop_jobs/profiles/drop_jobs/modules/contrib/content_taxonomy/content_taxonomy_autocomplete.module).
Warning: Invalid argument supplied for foreach() in content_taxonomy_autocomplete_validate_deny_new_terms() (line 106 of /opt/lampp/htdocs/drop_jobs/profiles/drop_jobs/modules/contrib/content_taxonomy/content_taxonomy_autocomplete.module).

Please guide us..

Thanks

installed drop jobs distro, seeing some cool stuff

mkahn's picture

and hitting some errors..

Doesnt look like i'll be able to show this to a prospective company as a prototype for work, but it looks like a good project,and i'll be happy to help in the ways i can. No a genius coder, but i've gotten some functionally interesting drupal sites to work in the past.

Is there a known issues repository for the project? I dont want to report things that are known.

Not much recent input from Alexweber here. Is this still happenin?

Ive seen a couple of errors along these lines.

Notice: Undefined index: use text format filtered_html in user_role_grant_permissions() (line 3056 of /usr/www/users/frk/D7/D/modules/user/user.module).
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'module' cannot be null: INSERT INTO {role_permission} (rid, permission, module) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 1 [:db_insert_placeholder_1] => use text format filtered_html [:db_insert_placeholder_2] => ) in user_role_grant_permissions() (line 3058 of /usr/www/users/frk/D7/D/modules/user/user.module).

Mk ~ Drupal apprentice

How do I install it !?!

skrotos's picture

I got drupal 7, got the drop_jobs profile, ran build.sh it gave 3 errors that it can't unzip some solr stuff and that it can't get other stuff from somewhere.

Got a complete distribution , same issue.

How can i install it ?

I have been using drupal for the last 3 days so i am noob. PLS HELP

PLOX

Jobs v Recruiter

gibry21's picture

I know this may be a slightly biased group to ask this question to but I was hoping for an honest answer.

From what I can see Recruiter seems to be a much more polished, used and supported distribuition, however there seems to be some interesting features in Jobs that I like, in particular the ability to match potential jobs hunters via their resume to available jobs.

Is this correct?

Can anyone show me examples of Jobs?

Honest opinions, for a quick out the box solution with minimal development required other than theming....is Jobs better than Recruiter?

Thanks

Ryan