Splitting this from #953668: Create new aggregator category "Drupal Jobs Announcements".
We should add a cck field for "job type" - I don't want to make it too specific, so I think it could be a multi-select with:
* Site builder
* Designer
* Developer
For location, this is a little trickier since the module-space in Drupal is not so well defined right now. Location is the most obvious. Geo seems like a solid new choice, but is not so reliable the last time I used it. Something else?
I think letting someone select a country/city is a decent way to go.
Or we could give them a map and let them choose the lat/lon that makes it super easy to store lat/lon and do distance calculations.
I'm relatively disenchanted with doing geocoding based on city/country, especially for international locations.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 954674-improve-job-type-D6.patch | 2.24 KB | acouch |
Comments
Comment #1
gregglesFor the listing, it would be of course great to then expose that information as filters on the listing view.
Comment #2
gábor hojtsyIn fact, the drupal.org redesign mocks have some interesting content relating to jobs :) Such as offering you jobs close to you. Or that you can specify your interest areas in your profile and view jobs (also events) matching those :) I'd suggest consulting the mocks there as they had some critical thinking going into them.
Comment #3
gregglesHere's the jobs section Gabor mentions: https://infrastructure.drupal.org/drupal.org-style-guide/prototype/jobs....
Comment #4
acouch commentedI think country / city would specific enough for the location element.
I like the design. It lacks the location element discussed above which I think is important. A Solr type search would also be useful.
I might expand the job list to include 'Manager / Sales' or something that includes job types that often require a Drupal background but aren't technical.
Comment #5
alex ua commentedI definitely like the idea of adding in address specific info into the job postings, and I think we could probably tie into (or pull from) some locale system to get local city/town names.
+1 from me on this idea, but -1 on only having Site builder, Designer, & Developer listed, as I think there's space for other job types (business, accounting, project management, content writing/copy editing, etc.).
One thing that could (potentially) make this even better is a "company profile" for the posting company so that people could see all the postings from said company. Heck, I'd even pay to have a profile linked to our job postings. ;-)
Comment #6
gregglesThe Redesign of the page has slots for Developer, Designer, Writer. I'm not sure what the process is for deviating from The Redesign, but my initial thought is we should start with those and tweak based on real world information (e.g. I doubt we'll get many requests for writers, but we should try it and see).
Company Profile is an interesting idea and something that I believe is specified as part of The Redesign: Marketplace.
Comment #7
acouch commentedIf we are constrained by the design for now at least adding an 'other' category would allow initially for posting jobs that don't fall into "Developer, Designer, Writer".
How do we actually make this happen? I'm willing to put in some work if we can move forward.
Comment #8
alex ua commentedTo follow up on @greggles in comment #6, I've created another issue to talk about the business listings (which I think we should link to the job postings, if only to give contributing shops a way to share job openings with the community): #967772: Additional features for the Marketplace
Comment #9
alex ua commentedI'm curious: is there a compelling reason to keep Jobs @ g.d.o? If not, anyone mind if I move this issue to the webmasters queue?
Comment #10
gregglesUntil there's a commitment to a new home and reasonably sure sense that it will happen I'd rather keep this issue here.
@acouch, if you're still interested, I've got g.d.o DB dumps that are reasonably sanitized of private data. So, you should get read access to the groups bzr (file an infra issue and then ping basic` or nnewton about it in #drupal-infrastructure) and then I'll get you a copy of the DB.
Comment #11
acouch commentedI did a search on the gdo database (select count(*) from node where type = 'job' and title like '%designer%';) and got the following results for different terms:
developer: 3645
designer: 299
manager: 169
director: 51
sales: 13
editor: 13
writer: 12
It seems like "Developer, Designer, Manager, Other" would best reflect what people have been posting.
Comment #12
acouch commentedAttached is a patch to add an cck formatter that makes returns an abbreviation. This is necessary for 'Employment Type' and 'Telecommute' listed above. I'll export an updated view when I get a chance. I realize that to have the numbers applied to the tabs for "Developer" "Designer" we'll need to update the database to apply the new designations to current jobs. Will try and write something for that when I get a chance.
Comment #13
gregglesI think it's OK if the historic job posts don't use the same designer/developer/etc. designation.
You can either post the exported view here or mail it to me - I'll test this all out on scratch and then make it live.
Thanks!
Comment #14
gregglesFrom a post about how to improve the jobs area - http://groups.drupal.org/node/161264#comment-541634
I don't like all of these, and some would be too complex in the UI, but many are great. We can add some and see how it goes.
Comment #15
JuliaKM commentedWhat about adding some or all of the following CCK fields?
I didn't include Payment Options because it seemed like a very specific requirement that might not make a lot of sense for the majority of positions. For example, if someone was hiring a full-time designer with benefits, it would be odd to ask them to explain how they will pay that person.
Sponsor
- CCK Text - Radio widget
- Options: Individual, Company
- Required field
Position Type
- CCK Text - Check boxes
- Options: Module Development, Theming, Project Management, Support/Maintenance, Editorial, Other
- Required Field
Location
- Location using location module? Not sure what the options are here
- Required field
Setting
- CCK Text - Select widget
- Options: Home Office, Partial In-office, On location
- Optional field
Expiration Date
- CCK Date Widget Text field with Pop-up calendar. An advantage of adding this field is that we could have expired jobs disappear from the page.
- Required field
Eligibility
- CCK Text - Check box widget
- Options: Local candidates only, English proficiency required, (Other options)
- Optional field
Salary
- CCK Text - Text field with help text prompting the user to enter a currency as well
- Optional field
Comment #16
Sahin commented"Job" content type is a pain in the g.d.o for a long time. Many jobs which are posted mistakenly or expired or became irrelevant or just spam, cannot be deleted/disabled even by their authors nor excluded from the view.
This was discussed in the following issues (which are now closed and redirected here):
* create open/closed toggles for job posts
* Enable "mark my own job as closed"
After examining those issues together with #14 & #15, I think it is possible to formulate a solution like this:
- "expired date", as JuliaKM defined, and
- "status", select widget with "open", "closed" and "spam" values.
Comment #17
sreynen commentedThis is postponed pending #994230: Move job postings out of g.d.o
Comment #18
avpadernoSince jobs post have been removed from g.d.o, this issue is outdated. Any change should be done in jobs.drupal.org.