Hello Folks, My name is David, and I have been contracted by a friend to build for him a job matching web app.
I have learnt a lot from nairaland over the years, so I thought it will be nice to give back to it through explaining the process I will use to build this app. It should also be fun and educative, I can get ideas on things I might have overlooked or learn new things along the way. The goal is for relatively new web developers to learn and for me to also learn too.

I am using html5, jquerymobile and php for my development. I shall be posting the procedures I will be using. I wont be pasting the codes cos I browse with my phone, I will be explaining it, so that it can be understood by anyone that has an idea of the language.

Enough said, I really hope this will be fun.

Breaking down wot the application will be doing

An employer of labour signs up, and advertises for a job, indicating different qualifications for the job. He then clicks on a link to see d candidates dat qualifies for the job

On d job seeker front, he/she uploads his/her details and then can click on a link to see the jobs dat he/she qualifies for

There will also be the admin who will be controlling both sides

i will be keeping my head to this project

Sorry guys, I hav bin v.busy on anoda project wey its delivery time dey close, nd d client they on my neck.

osile2012:
[size=15pt] OK, tell us the roles the different languages u will combine will play in the development process. Thanks [/size]

Gud question, we'll use PHP nd MYSQL to connect to the database and interact with the server, most of the business logic will be done with PHP.
We'll use Jquery to manipulate the frontend, make the UI dynamic
We'll use Jquery mobile to give the application look a mobile app outlook. This is not like a regular website, its more of an app than website. And then the client has plans to upgrade it to a mobile app, so using Jquery mobile will make it easy to compile it with frameworks like phonegap nd mke it a html5 mobile app.
We'll use html5 so that jquerymobile can work with it well. Cos jquerymobile was designed to work with html5.


I have finished working out the database structure, I'll explain it in a bit, I gotta rush do some stuff now.

The database has lots of tables, nd can be grouped into 3
1) Employer information which consist of;
-Table of basic info of the employers/companies
-Table of locations of the companies

2)Job information which consists of;
-table of the basic info of a job advertised like title, company, description
-Table of d educational fields against the jobs dat requre them
-Table of qualifications against the jobs dat requre them
-Table of skills against jobs dat require them
- Table of locations where d jobs re available

3) Job seeker's information which consist of;
-Table of basic info of the job seeker
-table of job seekers yrs of experience against the field they acqured it in
-Table of job seekers qualifications
-Table of job seeker's skills

The other tabls include tables for Locations/states, skills, andqualifications.

It took careful brain storming to get this database table structure, cos if its wrong, the whole project will become really v.diffcult 2 complete nd may not be as dynamic as desired.

I hav bin busy, but am back to the project again for now.

There re some job qualifications dat might be compulsory like age, field, qualification etc. So I'll add columns to indicate 1 or 0 depending on weather d job qualfication is compulsory. These columns will hav names like age_compulsory, field_compulsory, etc nd will be in the job table.

Nxt agenda will be to create the main business logic that will be making the actual matching.

This logic will be in two parts;
1)The Logic for matching a job against all job seekers (dats from the employer's side/view of things)
2) The Logic matching a job seeker against all jobs (dats from the job seeker's side/view of things).

I'll delve into each of those logics nxt. Writing the pseudocodes for them.

Its been a looong time!!!
I actually left the project, the client wasn't showing enof seriousness. But now that I am less busy, I decided to go back to it, mainly for academic purposes and I might get anoda client for it.
I'll resume by giving a run down of my final database tables and a brief description of each

1st re tables relating to the Employees or more appropriately, job seekers. They re;
- Employees
This kinda the mini bio-data of the jobseekers
- employees_experience
This where the no of yrs of experience of the jobseeker in a particular field re stored
- employees-qualification
This is where the qualifications of a jobseeker is stored
- employees_skill
This s where the skills of the jobseeker is stored
- employee_location: the places where the jobseeker is located re stored here.

As u can see, all the info relating to the jobseeker that will help the app to perform its work re all stored in the above tables.

Next we go into the table for employers

There is only one table for the Employer/company
And it contains the mini bio-data of the company/employer

Next re tables relating to the job being advertised. They re;
-jobs:
This contains the title, employer_id, description, age for the job, and weda meeting the age barrier is compulsory.
- job-experences
This contains the no of yrs of experiences needed in a particular field for the job
-job_locations
This contains the locations where these job opening is
- job_skills
This contains the skills that this job requires

As u can see, the above table supply us with the relevant data concerning the job being advertised. This will help the app to match the job opening with relevant job seekers.

Next re tables that I refer to as resources

The last group of tables in the database I refer to them as the resources because they provide information for the other tables to use. They re;
-Fields
This table contain all the different fields available.
- Locations
This table contain the 36states and capital
- Qualifications
This contain the diff qualifications available
- Skills
This contains the different type of skills available

The Id of the above tables re used extensively in all the other tables to pull data.

That's the database. And I cannot over emphasize the importance of database in development. It can mess the whole tin down if not gotten right.

Next is a run down of the app itself.
I will do more of summarization than details, cos am not dat gud in typing. I can answer questions to throw more light

Wen u enter the app, there are 3tabs; Homepage, Employer and Job seeker.
All tabs re generated using jquery Mobile.

The pages re also loaded via jquerymobile, so most of the codes re on the same page.

Nothing is on the homepage for now except 'welcome to Job Match App'

Nexts we go to the Employer page

The Employer Page greets u with the Login. If its a new employer, he/she goes to the register page and register.
Existing employers logs in using its email and password.

Once logged in, the employer is presented with 4 tabs; myjobs, advertise a new job, profile and logout.

Myjobs is the doorway to the jobs the employer had advertised. And an opportunity to edit or update it.

Advertise a new job is the doorway to the form where the employer advertise a new job.

Profile shows the bio-data of the employer and a chance to edit or update.

Logout logs the employer out and takes him/her to the homepage

The Job seeker page greets u with a login form and a link to register.

Once logged in, there re 3 tabs that re loaded; jobs qualified, manage profile and logout

Job qualified leads u to all the jobs that u were successfully matched with. U can view the company profile of the company that owns the jobs.

Manage profile gives the job seeker opportunity to manage or edit his/her profile.

The Logout tab logs the jobseeker out nd takes him/her to the homepage.

So that's it, the app.
More adjustment may still be done in future depending on the client, but the basics has been done$

This wasn't. An easy project, I learnt a lot about jquery mobile which I didn't know before now and also jquery.

Questions are very welcomed.

I am of the opinion that if web developers in this country can come 2geda, form a group and keep on churning out apps and quality dynamic sites.
None of us is as good as all of us.