Jobs
Update--------------------------------------------------------------
Well .. im beginning to think that perhaps this module should instead be a feature
http://drupal.org/project/features
It seems to me that my original inspiration for this module about depending on cck etc fits better with features. This would allow things to be more modularized. Perhaps we can have a set of several different jobs types ... mainly one for the basic needs of a small company webiste which was my original intent for this module.
Im going to take a shot at creating this into a feature. I'll post back asap.
----------------------------------------------------------------------
This project is intended to be an Integrated Jobs Management App. The opposite of the job_posting module which has no dependencies; & subsequently is less configurable. Also this will be simpler than the jobsearch module in that we dont require resumes tracking & recruiters bits, this module intends to start simpler and allow that addition/or/integration if required. I figure rather than attempting to re-invent the wheel, we can use Views & more importantly CCK to open up many features easily. This allows the platform to be more use-case centric without a lot of bloat.
For starters I am creating one default CCK type (Job Post) which includes a customizable application with resume upload & built in actions which send notifications emails etc. There will also be a couple configurable supplied views. Of course it will be open to other cck fields like location, date, gmap, etc etc..
I am creating the module for a couple of my current projects and will have a dev release for 6.x out ASAIC.
This project will depend on--- CCK & some field-types, Views, Token, Actions, Trigger
Sure cck/views is pretty straight forward stuff .. and could be done manually by most anyone. But I think as a module its easier to get started with the basics and (through good docs) move right into customizing a jobs management platform for most site uses.
This is my first actual module & even though mostly dependent, it might still take me a bit! Shouldn't be too terribly long since most of the hard stuff is already written & available!
-----------------------------------------------------
A Thought on content-types: I was thinking it would be nice to need only one content_type that can be altered into various job_types and have unique application elements and notifications choices, this would require slightly more complicated code but would eliminate the need to create multiple content_types for varied job-types. I am starting simple though and will come to this aspect more detailed than taxonomy categorization once the bulk of things are operational.
-----------------------------------------------------
Please post Suggestions and such in the issues cue.
