Right now it's just kinda there but doesn't really add any value or implement any of the actual functionality and workflow that's expected of it.

Organizations should be an optional module which, when enabled, allows organizations to manage teams of recruiters that work for them (in a nutshell).

Comments

kaizerking’s picture

kaizerking commented

Yes, That's exactly the way it should be.
By default, recruiter, applicant roles are minimum with their profile2 profiles and also the content type organization should be available,
1. recruiters will reference organization node either select or add in their job posting.
2. Candidates will reference organization node select or add in their work experience.
if an organization feature is enabled then the organization profile is created.
1. Created organization will reference organization node select or add in organization profile2 profile,as usual like in job or in resume experience. and the organization profile2 profile title is replaced with organization node title.
adavantages, no one can create duplicate organization entries
this way the data will be consistent across all the features. even if organization feature is disabled it wont effect other features
only issue will be to manage addresses for the organization
What do you think about this?

alexweber’s picture

alexweber commented

Not quite! You are trying to push stuff you asked for in another issue which I marked as closed (won't fix)...

I'll explain what I want to accomplish here later when I have more time.

iRex’s picture

iRex commented

Just thinking out loud....

Organization as a profile with the ability to create one or more sub-profiles (recruiter profiles)....

alexweber’s picture

alexweber commented

@iRex thanks for the idea, I'm considering that and also just keeping the node + author thing. Either way I do want organizations to be able to create and manage not only recruiters but also jobs and all activity from it's recruiters.