X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0A3F9D1B473 for ; Tue, 16 Dec 2003 17:11:31 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 68653-07 for ; Tue, 16 Dec 2003 13:11:00 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id B0C8AD1B449 for ; Tue, 16 Dec 2003 13:10:59 -0400 (AST) Received: from [63.195.55.98] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 4085148; Tue, 16 Dec 2003 09:11:36 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: francisco@natserv.net Subject: Re: Requirements feedback for jobs.postgresql.org. Date: Tue, 16 Dec 2003 08:53:10 -0800 User-Agent: KMail/1.4.3 Cc: pgsql-www@postgresql.org References: <1070400141.25244.8915.camel@camel> <200312120908.47640.josh@agliodbs.com> <20031215211038.Q1205@zoraida.natserv.net> In-Reply-To: <20031215211038.Q1205@zoraida.natserv.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200312160853.10380.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/99 X-Sequence-Number: 3159 Francisco, > Wouldn't it be better to have the resumes on the service and to just have > prospective employees be able to have multiple resumes? This way when > there is an application they can tell the system which resume to point to > for that particular application. But you've missed two important points I addressed in my earlier e-mails: 1) We (my team) does not want to code that functionality. It would expand = the=20 scope of the project by at least 75% and we're just not interested. If you= =20 want to add that to what we contribute, you are welcome to do that later. 2) Storing resumes, employee profiles, etc., will have significantly greate= r=20 storage and security requirements than the storage of job listings, and the= se=20 issues will have to be addressed. Using our spec, they can be=20 ignored/postponed. >If you EVER send attachments to > prospective employers what will happen if someone fakes an email as coming > from you and sends a trojan or a virus?=20 Mmmm... yeah, we'd better put in a filter to limit the MIME encoding and=20 extensions of resume attachements to DOC, PDF, WPD, TXT & SXW. > I have never seen categories in the sense you are talking about. My > experience is with Hotjobs, Monster and a few others. They have categories > like IT, programmer, etc..=20 Precisely. And just becuase you don't use them doesn't mean that others d= o=20 not. > > Database Administrator (DBA), Software Development, Performance Tuning, > > PostgreSQL Support, General System Administrator, Training, and Other. >=20 > Not a bad list, but the system should be flexible so the administrators > can add. Maybe. I can see adding a couple new categories after the system is launch= ed=20 and we get feedback from the users. Otherwise, I think the categories=20 should be rather inflexible; otherwise we risk ending up with 80 categories= ,=20 50% of which have only one job in them. > So people are going to attach or cut/paste their resumes? > Sounds cumbersome. Well, if you don't like it, you're welcome to ready your PHP skills. After= =20 you draft a spec to deal with the security issues raised by online storage = of=20 resumes .... --=20 -Josh Berkus Aglio Database Solutions San Francisco