In the first part of this article, you built the architecturenecessary to accept and store resumes online. In this concluding part, findout how to make use of the stored data to find suitable candidates for aparticular job, and also read about the functions available to maintain andupdate the job listings.
And that just about concludes this case study. Throughout this development effort, I have made widespread use of database normalization techniques, PHP's built-in functions, HTTP headers, and mySQL database queries. If you are new to PHP, I hope that the effort has been instructive, and that it has helped you gain a greater understanding of these powerful open-source tools.
If you'd like to learn more about some of the issues described throughout the course of this article, here are a few links:
I believe that a tool such as the one described over the preceding pages offers tremendous benefits to any organization in its recruitment efforts. By obtaining and storing information in electronic format, it reduces paperwork; by imposing a structure on user information, it makes it easier and quicker to locate information; and by using a database, it ensures that data does not get corrupted.
It should be noted also that this is an initial release of the application, and I expect it to evolve further, with new features being added and old features being upgraded. It's always a good idea to review both design and code as the application evolves - I plan to do this a little further down the road, and to make changes to both the database schema and the scripts themselves. This process should take place in conjunction with the development plan for new features, so that the addition of new features does not add to overhead and cause performance degradation.
Until then, though, I'm going to kick back with a cool drink and a good book.
This article copyright Melonfire 2001. All rights reserved.
