Skip to content

AndersonGroupPHInternal/Anderson-Recruits

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

58 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

HROnline

This is the Online Recruitment System or also known as Anderson.Recruits currently used by the Anderson Group BPO, Inc.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Prerequisites

You need XAMPP, FileZilla, Visual Studio Code (or any text editor but use VSC if possible because it has git pre-enabled).

Installing

1. You need to install Visual Studio Code or any text editor.
2. You will also be needing to install XAMPP for Apache and PHP, Filezilla for FTP, and GitKraken for easy version control but not necessary if you know how to use GitHub.
3. Clone and download this repository. Copy and paste it to your web server or if you are using XAMPP, it's in the /htdocs directory of wherever you installed XAMPP. Just search for the xampp directory and inside that directory you should see an /htdocs directory.
4. Get the database(.sql file) from your PM or the supervisor handling the Anderson.Recruits.
5. Get the index(.php file) from your PM or the supervisor handling the Anderson.Recruits.
6. Import the .sql file to localhost/phpmyadmin and configure the connection string of your codes to match the credentials of your MySQL database.
7. Test and run the website.

If the website successfully run, you should see the dialog box where you will choose a type of applicant you are applying for.

Notes

Some of the files need not be edited or removed. And if you are not sure of what you are doing, DO NOT edit or remove any file(s) from the file tree. This may result in unwanted errors or malfunction of the whole system.

This system was written, developed and created by many different software developers who were taught with a different strategy and writing codes in their academe, without following any framework or coding structure given by the company. So bare with how the system architecture looks like and how it was structured.

If you are reading this, your best approach in taking over this system is trial and error by using the console of the browser in debugging.

Branching

In adding features or when working something in the system, you must use branching to avoid unwanted errors and for everyone to have the same working version of the system. Therefore, we must follow a branching structure for the system.

*The master branch is the main branch that is working and in the production stage. *The release branch is the branch for development, this should be the copy of every developer and this is the branch that you must work on first before pushing and merging into the main branch. *The feature branch holds all the small features the system has. If you are working on adding a new feature in the system, you should create and check out a branch with 'feature/nameOfNewFeature' so everyone can work on the feature without worrying about the release or current working system.

Important Reminders

* ALWAYS test everything in the development stage before uploading changes into the live server. 
* In development stage, if you are testing or working in submission of application forms, put in mind that it will notify and submit an email on the email address of the HR, so remove the mailer function first or if you are working on the mailer, use data that will distinguish that it is for debugging/development purposes only (eg. firstname->'Test').
* ALWAYS check if there is anyone who is currently using the system before uploading changes in the system. 
* When writing codes, ALWAYS write comments. It will not just help you when going back or debugging the system when a bug occurs but also help the future developers who will take over the system.

Important Files From the File Tree

/HROnlline
|-api - This directory contains the api directory for the Anderson.Recruits.
    |-js - This directory contains the js file for the reports.
    |-reports - This directory contains all the api for the generation of reports.
|-config - This directory contains some of the PHP files for queries in the Anderson.Recruits.
|-constants - This contains the connection string/operations/functions for the api directory for Anderson.Recruits.
|-css - This directory contains the CSS files of the Anderson.Recruits.
|-fonts - This directory contains the fonts of the Anderson.Recruits.
|-custom_css - This directory contains the custom CSS files of the Anderson.Recruits.
|-custom_js - This directory contains the custom javascript files of the Anderson.Recruits.
|-img - This directory contains the image files of the Anderson.Recruits.
|-js - This directory contains the javascript files of the Anderson.Recruits.
|-quickapply - This directory for the quick-apply feature of the system.
    |-css - This directory contains the CSS files for the quick apply.
    |-img - This directory contains the image files for the quick apply.
    |-api - This directory contains the API of the quick-apply feature of the system.
    |-constants - This directory contains all the constants values for the quick-apply feature.
    |-index.php - This file is the ~/application/quickapply/ or index file of the Quick Apply feature of the Anderson.Recruits. If you want to add/remove/update any features in the system's ~/application/quickapply/ page, this is the file you need to edit.
|-account.php - This file is for updating the currently logged in account.
|-applicants.php - This file is for the Applicants List.
|-cms.php - This file is for the Content Management System, adding positions and application source lists.
|-connect.php - This is the connection string of the system to the MySQL database and Apache server.
|-createAccount.php - This file is for creating an account for the Anderson.Recruits.
|-google.php - This file is the main page/home/dashboard of the HR after logging in.
|-index.php - This file is the ~/application/ or index file of the Anderson.Recruits. If you want to add/remove/update any features in the system's ~/application/ page, this is the file you need to edit.
|-formvalidator.js - This file is the validator/checker of the field and values given by the applicant when filling up the application from the index.php.
|-printableResume.php - This file shows a printable resume in pdf when clicking the eye button in google.php for the HR.
|-query.php - This file runs the queries for the google.php.
|-quick_applicants_list.php - This file is for the Quick Apply Applicants List.
|-reports.php - This file is for the viewing the Reports.
|-sidenavehtml.php - This file is the side navigation bar shown in google.php
|-serverside.php - This file runs the queries for the index.php.
|-update_resume_form.php - This file updates the resume and is used by HR.
|-update_serverside.php - This file runs the queries for the update_resume_form.php
|-updateformvalidator.js - This file is the form validator for updating an applicant.
|-user_logs.php - This file is for the History Logs of the HR who logged in the system.
|-view_authorization_list.php - This file is for General List.
|-policy_viewer.php - This file is for the Privacy Policy List.

PS: Many files were not written and included in the "Important Files" section because during working or up to this date upon writing this README, I did not encounter changing or working any codes in the other files. Only the files in the "Important Files" section are the files that I had a chance to worked on.

Update this README if you want to add any other essential changes or notes.

About

Online recruitment system.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •