iVOTE: PUPSRC Online Election System 🗳️ 📊

About

• iVOTE is an under-development online voting web application for Polytechnic University of the Philippines Santa Rosa Campus Student Academic Organizations.
• This project is for partial fulfillment of the subject COMP 20133: Applications Development and Emerging Technologies.

Table of Contents

1. Tech Stack
2. Features
3. Installation
   • Prerequisites
   • Steps
4. Role Access
5. For Collaborators
6. Acknowledgments
7. Contributors
8. UI Snippets
9. Recommendation

Tech Stack

Tech stack and frameworks used to build iVOTE web-application

• 
• 
• 
• 
• 
• 
• 

Features

Features Offered:

1. Electronic Ballot Form
2. Live Counting of Results
3. Election configuration
   • Add Ballot Form Input Field
   • Vote Scheduling
   • Dynamic Voting Guidelines
   • Candidates Sequence on Ballot Form
4. Archive of Election Results
5. Exportable Reports (pdf, xlsx, csv, and docx)
6. Candidates Information Management
7. Voters Account Mangagement
8. Password Recovery
9. Login Attempts Lockout

Other Features:

1. Mobile Responsive
2. Full Screen Toggle of Live Results
3. Anonymous Toggle of Live Results
4. Email Notification about Account Approval or Rejection

Installation

Prerequisites

• You must have installed PHP and Git on your machine.
• To access the phpMyAdmin, you need XAMPP installed also.

Steps:

1. Clone this repository by running this git command.

git clone https://github.com/BSIT-3-1-APPDEV/PUPSRC-AutomatedElectionSystem

or if you need to checkout a specific branch only

git clone --single-branch --branch main https://github.com/BSIT-3-1-APPDEV/PUPSRC-AutomatedElectionSystem

Note: Change the branch name as you see fit. In this case, the name of the checked out branch is main.

2. Download the necessary files on your root folder to create the databases of 9 orgs. These are the only files needed.

• create-db.php
• env.php
• create-org-tbl.sql

Access them here.

3. Run the PHP script on your terminal

php create-db.php

or thru directory listing

localhost/path_to_file/create-db.php

4. Open the website locally on your machine. The URL may look something like this:

http://localhost/PUPSRC-AutomatedElectionSystem/src/landing-page.php

Role Access

Account Type	Features
Student-Voter	Account registration, password recovery, and vote casting.
Admin	Validation of voter account, and access to live counting of results
Head Admin	Similar to admin, with only the additional privilege of adding new admin accounts

For Collaborators

1. Clone this repository and checkout the development branch on your computer

 git clone --single-branch --branch development https://github.com/BSIT-3-1-APPDEV/PUPSRC-AutomatedElectionSystem

2. Create a local branch on your computer

git checkout -b your_branch

3. Commit your changes

  git add .
  git commit -m "type: issue-key-your_commit_message"

4. If finished, push/publish your local branch to this repository

git push origin your_branch

5. Open a pull request from your published branch to merge it into the development branch
6. Await the review and approval of at least one collaborator on your pull request
7. After approval, ensure that you pull the latest changes from the development branch on your computer.

git pull origin development

Important Note: Keep in mind the issue key of your Team's Project in Jira and proper conventional commit message.

Acknowledgments

The project team would like to thank the student academic organizations of PUPSRC below for their unwavering and continuous support and guidance for the success of this endeavor:

• Student Council Organization
• Association of Competent and Aspiring Psychologists
• Association of Electronics and Communications Engineering
• Eligible League of Information Technology Enthusiasts
• Guild of Imporous and Valuable Educators
• Junior Executives of Human Resource Association
• Junior Marketing Association of the Philippines
• Junior Philippine Institute of Accountants
• Philippine Institute of Industrial Engineers

Contributors

Made with contrib.rocks.

UI Snippets

• To follow

Recommendation

You can read more about:

Conventional Commits
Semantic Versioning

Back to Top