(1) The coder will develop a PHP interface that directly replaces the Who's Who directory shown at [url removed, login to view] , This is an online listing, like a phone book, which contains a person's name, E-mail address, homepage, hometown, birthdate, region, and biography. (2) The coder will develop four main HTML panels: selection of data, display of data, modification login, and modification edit. (3) SELECTION OF DATA. The selection screen will show a list of all regions, followed by a listing of all individuals, sorted by last name then first name. Clicking on an individual will show an Individual Display (one person), while clicking on a region will show a Region Display (all persons in that region). (4) DISPLAY OF DATA. This page displays all data for an selected individual, with the exception of the authentication password and exact birthdate. However the system will calculate the individual's age based on the birthdate and embed the age (in years) into the text. The display page will either display data for a specific individual, for individuals in a region, or display all individuals. Listings will always be sorted by last name and then by first name. They will appear similar in structure to the listings shown at: [url removed, login to view] (5) MODIFICATION LOGIN SCREEN. Before having access to a modification screen, the user must authenticate by providing their E-mail address and password. A "Forgot Password" option will be provided which E-mails the password to the E-mail address on file. (6) MODIFICATION EDIT SCREEN. The modification screen must fill in the HTML objects with the existing data for that user, before the user begins editing. The regions must be provided in a Combo control and are limited to Canada, International, Great Plains, Midwest, Northeast, Southeast, and West.
(1) Deliverables: Source code, instructions for installation and configuration, and recommended permissions settings for all files. (2) All configuration variables will be set at the top of the PHP script so that changes can be made if necessary. (3) All data files will be stored either in a simple MYSQL database or in a plaintext flatfile in a hidden directory (this will be a system directory outside of the /www hierarchy). If MYSQL is used, the Coder will provide full specifications to create the database. (4) The coder will recommend the appropriate permission settings for all files at a level that makes the project functional but preserves security. (5) The coder will develop the system so that another data field may be easily coded into the project if needed. About four reserved (unused) fields may be added to the flatfile or database for this purpose. (6) The coder will strive for simplicity and a small footprint. (7) The coder is expected to contact me (Buyer) if anything is unclear or ambiguous. I will be glad to answer questions and help provide additional specifications for the project. (8) The coder will comment the code where appropriate. (9) At the bottom of each page, the coder may provide a small credit for themselves and link to their homepage on this project to advertise their services. The coder may also publish and sell this system to third parties as they see fit, providing that all references to our name and website are removed. (10) The coder is not expected to transfer existing data, however he/she may use as many samples of the existing data as needed to develop the script. The coder may deliver this data with the script, and it will be used; we will convert the rest.
PHP 4.3.2. See [url removed, login to view] for server-specific configuration information.