💻 LabSync — Lab Equipment Tracker

A simple, fast and secure way to report, manage and track computer-lab equipment problems.

LabSync is a lightweight web-based Lab Equipment Tracker designed for educational computer labs. Students can quickly report problems with a particular lab system, while authorized administrators can review, filter, update and delete complaints from a dedicated dashboard.

Built with HTML, CSS, JavaScript and Supabase, LabSync keeps the interface clean for students while giving lab administrators the tools they need to manage reported issues efficiently.

https://priyam-26.github.io/LabSync/

Here’s a look at LabSync in action — from submitting a complaint to managing it through the administrator dashboard.

The student-facing dashboard provides a clean and straightforward interface for reporting lab equipment issues.

 

A dedicated login interface keeps the administrative dashboard accessible only to authorized users.

The admin dashboard provides an overview of reported issues along with search, filtering, status management and complaint controls.

Students can report an equipment/software problem in just a few steps:

• Enter their name
• Enter their board roll number
• Select the lab room
• Enter the affected system number
• Describe the problem in a maximum of 100 words
• Submit the complaint directly to the database
• Receive an immediate confirmation after successful submission

Currently supported lab rooms:

• 🖥️ Lab 103
• 🖥️ Lab 115
• 🖥️ Lab 121

Students do not need to create an account to submit a complaint.

Authorized lab administrators get a dedicated dashboard where they can:

• 🔐 Sign in securely through Supabase Authentication
• 📊 View complaint statistics
• 🔎 Search complaints
• 🧪 Filter complaints by lab
• 🚦 Filter complaints by status
• ✅ Mark complaints as FIXED
• 🔄 Reopen complaints when required
• 🗑️ Delete complaints
• 💾 Save multiple changes together
• 🚪 Log out securely

The dashboard also keeps track of unsaved changes and asks for confirmation before potentially losing them.

LabSync-main/
│
├── 📄 index.html                 # Student complaint portal
├── 📄 admin.html                 # Admin login & dashboard
├── 🖼️ favicon.png               # Website favicon
│
├── 📁 css/
│   ├── style.css                 # Student portal styling
│   └── admin.css                 # Admin dashboard styling
│
├── 📁 js/
│   ├── config.js                 # Supabase configuration
│   ├── student.js                # Student portal logic
│   └── admin.js                  # Admin dashboard logic
│
└── 📁 supabase/
    └── database.sql              # Database schema, RLS & cleanup job

• HTML5 — page structure
• CSS3 — responsive styling and layout
• Vanilla JavaScript — application logic and interactions

LabSync is intentionally lightweight:

Student
   │
   ▼
Student Portal
(index.html + student.js)
   │
   │ Submit complaint
   ▼
Supabase
   │
   ├── PostgreSQL → complaints
   │
   └── RLS policies
          ▲
          │
Admin Dashboard
(admin.html + admin.js)
   │
   ├── Search
   ├── Filter
   ├── Update
   └── Delete

LabSync includes an automated database cleanup job.

When a complaint is marked:

FIXED

its fixed_at timestamp is recorded.

Fixed complaints older than 7 days are then automatically deleted by the scheduled PostgreSQL job.

This keeps the active complaint database small and focused on recent issues.

A typical complaint moves through the following flow:

📝 Student submits problem
          │
          ▼
      🔴 OPEN
          │
          ▼
🛠️ Admin works on the issue
          │
          ▼
     🟢 FIXED
          │
          ▼
🧹 Automatically removed
   after 7 days

LabSync focuses on a few simple principles:

• ⚡ Fast — minimal dependencies and no unnecessary build system
• 🧼 Clean — straightforward interface with focused workflows
• 📱 Responsive — designed to remain usable across screen sizes
• 🎯 Practical — built around an actual lab-management workflow
• 🔐 Secure — database-level access control with RLS
• 🛠️ Maintainable — separate HTML, CSS, JavaScript and SQL files

Imagine a student is working in Lab 115 and discovers that System 07 is unable to open VS Code.

Instead of manually informing a lab assistant:

Name: Priyam
Registration No.: 117xxxxxxx
Lab Room No.: 115
System No.: 07
Problem: VS Code is not opening on this computer.

The complaint is submitted → stored in Supabase → appears on the admin dashboard → the administrator fixes the system → marks it FIXED.

Simple. 🎯

LabSync currently focuses on complaint reporting and administrative tracking.

It does not currently include:

• Student accounts
• Email/SMS notifications
• File/image attachments
• Technician assignment
• Repair-cost tracking
• Detailed audit history
• Multi-institution support

These can be added later if the project grows.

Some natural next steps could be:

• 🔔 Real-time admin notifications
• 📧 Email notifications when a complaint is fixed
• 📎 Screenshot/image attachments
• 👨‍🔧 Technician assignment
• 📈 Complaint analytics and trends
• 🕒 Estimated resolution time
• 🧾 Full complaint history
• 📱 Installable PWA support
• 🌙 Dark mode
• 🏫 Support for additional labs and departments

Contributions and improvements are welcome.

A simple workflow:

git checkout -b feature/your-feature

Make your changes, test them locally, and submit a pull request.

When changing database behavior, remember to update:

supabase/database.sql

along with the relevant frontend code.

LabSync — Lab Equipment Tracker

Built to make reporting lab equipment problems faster, clearer and easier to manage. 🚀

Report it. Track it. Fix it. 💻

Priyam Prabhat
Computer Science Student | Web Development | Cybersecurity

If you find this project nice, you can give it a ⭐ on GitHub!