Job Board > Requirements
>> Comment regarding Resume posting
It looks like the draft requirements for the job board include posting
resumes somewhere. I would prefer not to see them on the mailing list, but
it would be nice to offer this value added service for our job seeking
membership some other location within the AIfIA information network.
>> Comment regarding size/scalability
Does anyone have any idea as to the scale the system will have to handle?
Simple questions like "how many positions per month"? It could be that we do
need something which has lots of functionality to facilitate search + browse
+ subscribe + facetted + xml + rss + doohickeys ... or it could be that we
only need something simple.
How many job postings have there been to SIGIA-L in the last three months?
How many IA style jobs can you find at monster.com?
I find only 20 SIGIA-L postings since mid Nov 02, but many many more at
>> Comment regarding database structure
At the company I'm currently working for, we have a so called membership system (this is the backbone of our business). It is tightly connected to the back-end database of an integrated ERP system, through a customer table in the database. (actually it is totally integrated) When I build web solutions I have one single complaint: The ERP system has a world view that I do not really share. There is a Cust-table AND an Emp-table with the employees. I see all parties as part of the same "community" - just with different roles. I've seen a number of occasions where I would wish that ERP systems did not split the world into "us" and "them" at the database level. Come to think of it: This is where the "Intranet" "Extranet" split comes from - Not the firewall. When I build a solution with single sign on on a single url - I send customers to an extranet and employees to an intranet. I want to mix the two, but I can't - the system forbids!
What has this got to do with job boards? Roles! User permission systems. Be careful not to assume an "us" and "them" at a too low level - i.e. the database. You might regret this. ERP systems and business systems in general are carrying the signs of an obsolete understanding of business - which is slowing development of online community building at a business level. All the while open source based systems for non-profits are charging ahead.
>>Comment regarding email alerts
A very simple implementation would be an email alert whenever any new job is added. That is, no search criteria, simply an update email. Slightly more complex: a periodic email with a list of all jobs, just so they know they are still subscribed.
>>Comment regarding posting jobs
System should allow third parties to post jobs ... for example, I might see a job posted on a mailing list elsewhere, I then copy/paste the details to the job board. Having this functionality means having a job board administrator to remove duplicates.
>>Comment regarding retiring postings
One requirement which is missing is that job postings should expire, either when the job-poster (whether employer, agent, or third-party) actively retires the posting, or after a set period of time (eg. one month). Old jobs should remain available for research reasons, but be taken off the active list. Retired jobs should be able to be re-vivified.
Alternatively, every job could be clearly date-stamped, no active/retired dichotomy applied, and the reader can make up their own mind as to what is still active.
>>Comment regarding LIMITING postings received via region
Add email from Nick Finck