For a client we are looking for a programmer than can create a webbased system for us using php and MySQL. The system will be used by volunteers to subscribe as needed walk-on for courses of our client.
First I will explain our needs for the database part, then the front-end and then the back-end system.
The system must store 3 different sorts of data:
- Participant information.
About 10 fields of data like name and address. Also there need to be stored a username (e-mail address) and password used to log-in into the system. This info will be entered by the participant on our website.
- Course information.
About 10 fields with things like unike ID, name, small description, date, hours and how many participants/walk-on are needed. This information will be entered using the back-end system by our client
This must store which participant/walk-on subscribed for which course. After logging into the system by the potential applicant they can select and confirm on which course(s) they enter.
The front end will be a website with simple design (we will give details on colours end lay-out) that fits within a existing website. The front end that users see consists of the next pages:
A - Home-page with login system
On the home page there will be some general text about this project. Under it must come a table of all the available (not full) courses with minor information about them. Every course is a row in the table with on clickable link in it linking to a PDF with further information. The table with courses must be "smart" meaning that it greys out the courses that has already got the max number of applicants.
On this page there must only be one link like on which applicants can go to the page on which they can enter for a course. Actually they need to login to the system to get there so new users must fill-in all the 10 required fields (inclusing e-mailaddress as username and "strong" password) after which the go further. Users already been there before only have to enter there login information to go there,
B - Application system
After a user has logged in they come on a page look liking the first page on which is a table containing all the courses they can applicate for. By simply selecting the courses they want to enter and hitting the submit button they write themselves down for the courses. After doing that they egt a confirmation and come back on the same page which then contains 2 parts:
- The table with courses they selected themselves for (and the option to unselect them)
- The table with courses they didn't select themselves for (and the option to select them)
Like on the home page the table with courses must be "smart" meaning that in the table of courses they ones that are full are greyd out and can not be selected.
When a user enters a course by checking and submitting courses on this page there must 2 e-mails be send:
- One to the applicant as confirmation that they entered the course(s)
- One to our client so they can see someone is entering and have a e-mail backup
The back-end is the place that only our client can enter to manage the courses and applicants. This back-end system is only accessible by a administrator password and after login must have the following functionality:
- Overview of all registered participants with their details. Here they can see the participant details and edit, delete and create participants.
- Overview of all courses with their details. Here they can edit, delete and create courses including uploading the pdf.
- Overview of applicants by each course. Here they can delete or enter participants from their courses.
These are the specs. This is a very serious project for us in which we search for a programmer that is experienced with programming these systems and that can do the described job professionally.
The finished product must be a fully working secure system that can manage tens of courses and hundreds of applications. We are looking for a project time of max 10 days.
In the nearby future it is expected that when this system is successfully there will be interest for more functions and we will probably ask the programmer again for this when satisfied.