MySQL
  Home arrow MySQL arrow Page 2 - The Perfect Job (part 1)
Dev Shed Forums 
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Sun Developer Network 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Mobile Linux 
App Generation ROI 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
MYSQL

The Perfect Job (part 1)
By: icarus, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 4
    2001-06-28

    Table of Contents:
  • The Perfect Job (part 1)
  • An Ideal World
  • Entry Point
  • Going To The Database
  • The Five Rs
  • Lucky Thirteen
  • Building The Foundation
  • The Devil Is In The Details
  • Applying Yourself
  • Testing Times
  • Filing It All Away

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    The Perfect Job (part 1) - An Ideal World


    (Page 2 of 11 )

    Before getting into the nitty-gritty of syntax and structure, it is important to understand the problems I am addressing, so that the functional requirements of the solution become clear. Very briefly, here they are:

    1. Every placement call attracts a large number of resumes. Most of these resumes are printed documents, making it harder to search through them for potential candidates. Ideally, resumes should be made available electronically.

    2. Resumes are not in a standard format. Different applicants use different templates, styles, and colours, making it harder to read and sort through the volume of data. Ideally, every resume should be in a standard format, with standard fields and some structure imposed on the data within.

    3. With a large volume of responses, job applications may get misplaced or destroyed. Ideally, every resume, once entered into the system, should remain stored there with any data loss, so that it may be accessed at any time in the future.

    4. Searching through a large number of job applications for specific skills or capabilities is a time-consuming process. Ideally, the resume database should be easily searchable against pre-defined criteria.

    Having understood the problems, it becomes easier to decide on the requirements of the solution. An analysis of the problems above reveals that most of them would be resolved if I had a system which:

    1. categorized resumes by job;

    2. imposed a standard structure on the contents of a resume;

    3. processed resumes electronically;

    4. incorporated a search engine to easily produce a subset of the database matching specific criteria;

    5. archived applications over a period of time;

    6. allowed administrators to easily add and remove job listings from the Web site.

    This, therefore, constitutes the initial feature set for the application, and serves as the guideline for future development activity.

    This article copyright Melonfire 2001. All rights reserved.

    More MySQL Articles
    More By icarus, (c) Melonfire


     

       

    MYSQL ARTICLES

    - MySQL Server Tuning Tips and Tricks
    - MySQL Query Optimizations and Schema Design
    - MySQL Benchmarking Tools and Utilities
    - MySQL Benchmarking Concepts and Strategies
    - Take Some Load off MySQL with MemCached
    - MySQL Table Prefix Changer Tool in PHP
    - Using the SIGNAL Statement for Error Handling
    - Error Handling Examples
    - Error Handling
    - Completing a Search Engine with MySQL and PH...
    - Paginating Result Sets for a Search Engine B...
    - Building a Search Engine with MySQL and PHP 5
    - Using Boolean Operators for Full Text and Bo...
    - PHP, MySQL and the PEAR Database
    - Working with PHP and MySQL





    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 6 hosted by Hostway
    Stay green...Green IT