Integrated Donor, Student, Committee, Volunteer, Staff and User Management Portal
Conceirge Donor Portal Management is a web-based management application used to centralize information related to donors, orphan/semi-orphan students, donations, payments, committee members, volunteers, staff and organizational activities.
The functional design describes the Conceirge Portal as a Hostel Management and Donor Management application. It was created to support an organization managing orphan, semi-orphan and poor boys, including requirements such as accommodation, food, clothing and educational fee support, while maintaining student, donor, committee, volunteer, staff, donation and payment-history information online.
Maintain detailed orphan, semi-orphan and poor-student records and supporting information.
Register donors, search donors and maintain donor profiles and history.
Record monetary payments and grocery/material donations with history and reports.
Control registration, login, OTP, passwords, roles and access to the portal.
Maintain organization, school, address and supporting master information.
Provide payment, donor and date-range search/reporting capabilities.
The application follows a layered Spring-based architecture. The functional design also contains a Spring MVC request-processing diagram showing request handling through the Dispatcher Servlet, handler mapping/adapter, controller, service/business logic, repository/data access and database before returning a response.
| Technology | Purpose |
|---|---|
| Java 11 | Core backend programming language. |
| Spring Boot 2.7 | Application development, dependency injection, web/API and backend configuration. |
| Spring MVC | Request handling and controller-based web flow. |
| JPA/Hibernate | ORM/database persistence layer where applicable. |
| MySQL | Relational database for persistent application data. |
| Maven | Build and dependency management. |
| Linux VPS | Application hosting/deployment environment. |
The functional design identifies the major Conceirge Portal modules as Student, Donor, Login, Communication, Organization, Committee, Staff, Report and Reference Module.
Student profile, education, health, parent, certificates, achievements and related records.
Donor profile, payments, grocery donations, feedback and donor searches.
Registration, login, OTP, password and role/security management.
Email and SMS history and communication-related records.
Organization, school and address information.
Committee member information and organizational participation.
Volunteer information and support activities.
Staff information and operational support.
Donor/payment searches, date-range information and consolidated views.
Reusable/master information used across portal functionality.
The Student module is designed to create and maintain detailed records for orphan, semi-orphan and poor students. The documented student information includes personal details, CWC ID, contact details, student type, disability information and organization association.
| Area | Information Managed |
|---|---|
| Basic Profile | Student ID, admission number, first name, last name, surname, status and date of birth. |
| Contact | Mobile number and email ID. |
| Identification | CWC ID and government certificate information. |
| Student Type | Orphan, semi-orphan and poor. |
| Disability | Disability status/details as represented by the application. |
| Organization | Organization association and audit information. |
The Donor module is a major functional area of the portal. It manages donor registration, donor profile information, donor searches, special/permanent donor information, feedback and donor-related history.
| Field Area | Examples |
|---|---|
| Identity | Donor ID, first name, last name, surname. |
| Contact | Email, primary and secondary contact numbers. |
| Additional Information | Nationality, PAN number and organization. |
| Address | Present and permanent address references. |
| Audit | Audit user and modified timestamp. |
The payment module records monetary donations and maintains payment history. The documented payment structure includes donor payment ID, donor ID, amount, mode of payment, cheque number/date, bank name, receipt number, occasion, occasion details, audit information and received-by information.
The attached screen provides a dedicated Date Range Payment History option. This supports retrieval of payment records for a selected period, which can be useful for monthly, quarterly, annual or financial-period reporting.
| Search | Purpose |
|---|---|
| Total Donor Payments | Retrieve donor payment totals. |
| Payments With PAN | Search payment records associated with PAN information. |
| Payments Without PAN | Identify payment records without PAN information. |
| Consolidated Payments | Provide an aggregated view of donor payment information. |
| Cheque Payments | Search cheque-based transactions. |
| Fund Type | Search donations according to configured fund type. |
The portal supports non-monetary donations through the Accept Grocery Items functionality shown in the attached screen. The system also provides Grocery Items History to review previously recorded grocery donations.
The documented grocery structure contains a grocery ID, donor ID, item quantity, item description and related audit/location information.
Committee is identified as a major portal module. It can be used to maintain committee-member information and support organizational administration.
Volunteer information is part of the broader organizational scope. Volunteers can support student activities, donation activities, events and other organizational operations.
Staff is also identified as a managed group in the portal. Staff members can support day-to-day student, donor and administrative operations.
The User Administration module provides login, registration, password-change and forgot-password functionality. The functional design specifies registered-user login using username, password and OTP, administrator approval for registered users, change-password functionality and forgot-password recovery using registered mobile OTP.
The documented email history structure stores email ID, subject, message, recipient, CC, BCC, sent date and audit information.
The documented SMS history structure stores SMS ID, message, mobile number, sent date, transaction ID and audit information.
These structures provide a record of communication generated through the portal.
The functional design contains separate structures for student, donor, user administration and generic/master data.
| Table | Purpose |
|---|---|
| student_details | Core student profile. |
| student_achievement_details | Student achievements. |
| student_behaviour_details | Behaviour and attitude information. |
| student_certificate_upload_details | Student certificates. |
| student_govt_certificate_details | Government identification details. |
| student_health_details | Health information. |
| student_previous_qualification_details | Previous qualifications. |
| student_profile_images | Student images. |
| student_qualification_details | School/class/qualification details. |
| student_reference_details | Reference information. |
| student_vacation_details | Vacation/guardian information. |
| student_parent_details | Parent/guardian information. |
| student_parent_address_details | Parent/student address references. |
| student_parent_birth_death_details | Parent birth/death information. |
| student_parent_divorce_details | Parent divorce information. |
| Table | Purpose |
|---|---|
| donor_details | Donor master/profile information. |
| donor_payment_details | Monetary donation/payment records. |
| donor_feedback_details | Donor feedback and comments. |
| donor_profile_images | Donor profile images. |
| donor_groceries_details | Grocery/material donations. |
| donor_generate_groceries_id | Grocery ID generation. |
| generate_groceries_details_id | Grocery detail ID generation. |
CRUD represents Create, Read, Update and Delete operations. In this project, these operations are implemented through the relevant application layers for maintainable business entities.
| Operation | Example |
|---|---|
| Create | Add donor, register student, create payment record. |
| Read | Search donor, view student, view payment history. |
| Update | Edit donor/student information and update records. |
| Delete / Deactivate | Where supported by business rules, remove or deactivate records rather than exposing unrestricted deletion. |
The application is deployed on a Linux VPS server. A typical Spring Boot deployment flow is:
The generated application JAR is then deployed to the Linux VPS and started using the configured Java runtime and server settings.
Conceirge Donor Portal Management: Developed and maintained a Spring Boot-based web application for managing donors, donations, orphan/semi-orphan student records, user access, committee, volunteers, staff and financial reports using Java 11, Spring Boot 2.7, MySQL and Linux VPS deployment.
Java 11 | Spring Boot 2.7 | Spring MVC | REST APIs | JPA/Hibernate | MySQL | Maven | Linux VPS | User Management | Donor Management | Student Management | Payment Management | Reporting
The attached document is ConceirgePortal Functional Design – Version 0.1. It documents the portal history, business purpose, architecture diagrams, modules and detailed database tables/fields. The document states that the portal was implemented to manage students, donors, committee, volunteers, staff, donor reports and payment history online.
This HTML presents the project information in a structured format and incorporates the three supplied application screenshots.