BPAMIS – Barangay Panducot Adjudication Manangement Information System

BPAMIS is a web-based case and complaints management system for barangays. It streamlines the handling of disputes and complaints, provides separate portals for residents and barangay officials, and includes hearing schedules, notifications, and a PHP-based chatbot assistant for case-related queries.

Features

• Resident portal

  • Online submission of complaints and blotter reports
  • View status and history of filed cases
  • Notifications for updates and hearings

• Barangay official portal (Captain, Lupon, Secretary, etc.)

  • Dashboard for active, pending, and closed cases
  • Assignment of mediators/lupon members
  • Scheduling and rescheduling of hearings
  • Case status updates and report generation
  • Feedback collection from residents

• External user portal

  • Limited-access view for external complainants
  • Notifications and case summaries

• Chatbot assistant

  • Case inquiry and basic guidance on KP (Katarungang Pambarangay) process
  • Knowledge-base–driven responses using local PHP scripts

• Notifications and reporting

  • In-app notifications per user role
  • Case reports and printable KP forms
  • Basic export to PDF for selected reports

Tech Stack

• Backend: PHP (procedural/custom MVC-style structure)
• Frontend: HTML, CSS, JavaScript (with Tailwind JS utilities in some views)
• Database: MySQL / MariaDB
• Dependencies:
  • PHPMailer for email sending
  • Composer (for PHP dependency management)

Project Structure

Key folders (not exhaustive):

• bpamis_website/ – Main public-facing pages (home, about, login, register, services, etc.)
• chatbot/ – Chatbot endpoints, knowledge base, and logging
• controllers/ – PHP scripts for login/registration, case handling, notifications, etc.
• ExternalMenu/ – Pages for external complainants and notifications
• OfficialMenu/ – Portals and tools for barangay captain, lupon, and other officials
• ResidentMenu/ – Resident dashboard and related pages
• SecMenu/ – Secretary-specific views and tools
• includes/ – Shared navigation bars, headers, and layout templates
• phpmailer/ – PHPMailer library
• uploads/ – Stored uploaded files (e.g., attachments, evidence)

Getting Started

Prerequisites

• PHP 7.4+
• MySQL / MariaDB
• A local server stack (e.g., XAMPP, WAMP, Laragon)
• Composer installed globally (for PHP dependencies)

Installation

1. Clone the repository

   git clone https://github.com/<your-username>/<your-repo>.git
   cd <your-repo>

2. Install PHP dependencies

   composer install

3. Create the database

   • Create a new MySQL database (e.g., bpamis_db).
   • Import the SQL schema (if provided) into this database via phpMyAdmin or the MySQL client.

4. Configure database connection

   • Open the configuration file (for example in the chatbot/ and/or controllers/ directory, such as config.php or similar).
   • Update the database host, name, username, and password to match your local environment.

5. Configure mail settings (optional but recommended)

   • In the PHPMailer configuration file(s), set your SMTP host, port, username, and password for email notifications.

6. Run the project

   • Place the project folder inside your local server’s web root (e.g., htdocs for XAMPP).
   • Start Apache and MySQL from your local server control panel.
   • Access the system in your browser, for example:
     • http://localhost/<your-repo>/bpamis_website/bpamis.php

Usage

• Register a new resident account or log in as an existing user.
• Submit complaints or blotter reports from the resident portal.
• Log in as a barangay official to assign cases, schedule hearings, and update statuses.
• Use the chatbot module to query case information and basic KP procedures.
• Generate and print reports or forms from the official menu.

Screenshots

Add screenshots or GIFs here to better showcase the system UI.

• Dashboard view
• Case management page
• Chatbot interface

Contributing

Contributions, suggestions, and bug reports are welcome:

1. Fork the repository
2. Create a new branch for your feature/fix
3. Commit your changes with clear messages
4. Open a pull request describing what you’ve changed

License

Specify your license here (e.g., MIT, GPL, or “All rights reserved”).