> Hmm. Two ways for taking care of CVs sprint to mind.
> One of them is the utter epitome of laziness - have a URLOFCV field.
> The other way is a bit more involved and would mean having
> skills & experience/work tables.
>Well, I had come up with two solutions - separate fields for each field in the
CV, aswell as a cut and paste BLOB or TEXT field for a complete CV. A CV URL
field is a good idea too. Better to include all options rather than one of them
though, don't you think? Like I said, it should be aimed primarily at the
jobhunter rather than the employers/agencies.
When I think about it, using your suggestion - or the copy and paste option -
would be the easy route for the jobhunter, but the first option would be the
most updatable - they would only have to modify the necessary fields, rather
than a) having to search through and modify the copy-and-paste item, or b)
having to modify a HTML page and upload it.
There's a chance it could build into a nice CV repository for people - if
someone enquires about them, they could just point to their record on linux.ie.
The fact alone that it's on linux.ie could only be a good thing for them: it
hints - wrongly of course - that they're a part of the Linux community, and
therefore a "real" Linux user; it offers a level of protection, with the
permission levels (there should be another 'none' level btw, so people can turn
their CV's off); and with a little mod_rewrite URL trickery, we can give people
a "real" URL to point people to: http://linux.ie/jobs/cv/$user.
I can handle setting up the DB's though, that's no problem. It's a list of
fields for the separated items I need - I'll look into the links that have been
posted, but if anyone has a little spare time I'd appreciate it if they'd
compile a list. It doesn't need to be perfect, I'll probably tinker with it
anyway. And of course any other suggestions for fields that wouldn't normally be
there, well and good. For instance, a URL's TEXT field is a must.
> having an Expires date entry may be a good thing to keep the
> database from filling up with cruft if someone forgets to remove
> their entry after finding their 'ideal job'.
>Well, this can be handled in a "responsible manner". There'll be several fields
in the DB to handle this - added, (last) modified, (last) accessed and (last)
reminded. A daily cron job can look for records that haven't been modified,
accessed or reminded about for, say a month, and send out an email notice asking
people if they still want their record in the DB, or if they'd like to make any
changes. Responses can be piped directly back into the app, via links in the
email, or manually for our ascii-only email readers. Even the manual option can
be piped directly back in using sendmail aliases. Tricky, but possible. That
should keep the workload on the administrator to a minimum.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!