Thread: jobs.postgresql.org - SPEC
Hi, As a start on jobs.postgresql.org we need to build a spec. list for the site. I can start off a few idea's and other's can add their input. The site can be simple or elaborate. Here's some simple points to begin with: There just idea's - nothing set in concrete. Ideally the site is build how you and others would like to see. Please add your thoughts to the following list and/or rule out those options which are overkill or not neccesary. a) Multi language ( I'll need some advice on the best method for this ) b) Opt in email alert list for job postings c) RSS file for interested people to use in their site(s) d) Drill down Country to State level ( no city ) e) Member profile for Employers to search for Employees ( username/password ) f) Company profile for Employees to search for Employers ( username/password ) g) Super User approval for all new listings ( both employer and employee ) f) Time limit of Job postings ( to help keep list relevant ). h) Time limit extension for Employers to log in and extend job posting. i) Flash ?? Thanks Best Regards Rudi.
On Tuesday 01 Jul 2003 8:23 am, Rudi Starcevic wrote: > Hi, > > As a start on jobs.postgresql.org we need to build a spec. list for the > site. > I can start off a few idea's and other's can add their input. > > The site can be simple or elaborate. > > Here's some simple points to begin with: > There just idea's - nothing set in concrete. Can I make a suggestion based on the fact that I was IT manager for a recruitment firm for three years and still do consultancy work in recruitment. There's one and only one factor that really matters - how many jobs have you got listed?* The functionality of the site itself is icing on the cake - what drives usage is an active turnover of vacancies. What possible number of jobs are there? Quick search: theregister.co.uk - 2 jobs jobsearch.co.uk - 3 jobs gojobsite.co.uk - 3 jobs computerweekly.co.uk - 0 jobs Now, it looked like at least one of those was a duplicate. Most were developer jobs (Perl/PHP that happened to mention PG amongst the usual long list of desired skills). So - we get the two sysadmin jobs out of the above posted every month (say). That means that once I pick UK from the search options, there's no point in any more search functionality, I can read all vacancies on one page. In fact, if that's the level of activity we could get by with a couple of screens of PHP script. Rudi - before you start building search systems, I'd strongly recommend getting answers to two questions: 1. How many vacancies per month per country? 2. How do we get those vacancies onto jobs.postgresql.org? Not trying to rain on your parade here, but I'd hate to see you spend a lot of effort on a site that attracted no vacancies. PS - your options list looked good, except for the "Flash?". * In a conventional situation, how many candidates too, but anyone who knows what they're doing will be subscribed to one or more mailing lists, so almost all potential candidates should know about the service. -- Richard Huxton
Too true. Good points. Perhaps a very simple app. is ample. It could be a simple as 2 pages. One to email a job listing to me and one to display all listings. I'll update the listing page manually as listings trickle in and follow up on listings to see if they've been filled. Maybe a third page for job seekers to list their Postgresql skills for Employers to contact ? Cheers Rudi. > On Tuesday 01 Jul 2003 8:23 am, Rudi Starcevic wrote: > > Hi, > > > > As a start on jobs.postgresql.org we need to build a spec. list for the > > site. > > I can start off a few idea's and other's can add their input. > > > > The site can be simple or elaborate. > > > > Here's some simple points to begin with: > > There just idea's - nothing set in concrete. > > Can I make a suggestion based on the fact that I was IT manager for > a recruitment firm for three years and still do consultancy work in recruitment. > > There's one and only one factor that really matters - how many jobs > have you got listed?* > > The functionality of the site itself is icing on the cake - what > drives usage is an active turnover of vacancies. What possible > number of jobs are there? > > Quick search: > theregister.co.uk - 2 jobs > jobsearch.co.uk - 3 jobs > gojobsite.co.uk - 3 jobs > computerweekly.co.uk - 0 jobs > > Now, it looked like at least one of those was a duplicate. Most were > developer jobs (Perl/PHP that happened to mention PG amongst the > usual long list of desired skills). > > So - we get the two sysadmin jobs out of the above posted every > month (say). That means that once I pick UK from the search options, > there's no point in any more search functionality, I can read all > vacancies on one page. In fact, if that's the level of activity we > could get by with a couple of screens of PHP script. > > Rudi - before you start building search systems, I'd strongly > recommend getting answers to two questions: > 1. How many vacancies per month per country? > 2. How do we get those vacancies onto jobs.postgresql.org? > > Not trying to rain on your parade here, but I'd hate to see you > spend a lot of effort on a site that attracted no vacancies. > > PS - your options list looked good, except for the "Flash?". > > * In a conventional situation, how many candidates too, but anyone > who knows what they're doing will be subscribed to one or more > mailing lists, so almost all potential candidates should know about > the service. > > -- > Richard Huxton
> Too true. > Good points. > > Perhaps a very simple app. is ample. > > It could be a simple as 2 pages. > One to email a job listing to me and one to display all > listings. > > I'll update the listing page manually as listings trickle in and > follow up on listings to see if they've been filled. > > Maybe a third page for job seekers to list their Postgresql skills > for Employers to contact ? Sounds like an excellent start. What about combining that with a "search aggregator" so people can volunteer job sites in their country that offer some PG jobs? Hmm - need to be quite flexible in the fields you could submit, and we'd have to think about terms of usage. - Richard Huxton
On Tue, Jul 01, 2003 at 17:23:54 +1000, Rudi Starcevic <rudi@oasis.net.au> wrote: > f) Time limit of Job postings ( to help keep list relevant ). > h) Time limit extension for Employers to log in and extend job posting. You might ask the employers for a time limit when they first submit the posting. You can have f) be a maximum time limit.