ID — Bahasa Indonesia

Muhamad Irga

Purwokerto, Central Java

Updated

RestMaos — School Library Management API

A Lumen school-library API: catalogue and DDC classification, copies, members, circulation, fines, visits, broadcasts, and reporting.

See the service: School & Learning Centre Applications

Screenshots

RestMaos library API deployed and responding
Main application view · Open image for full resolution
RestMaos endpoint collection open in Postman
Application view 2 · Open image for full resolution

Overview

What this system does.

RestMaos provides backend services for school-library management with over 200 endpoints. Its catalogue covers books, book titles, authors, publishers, categories, subjects, languages, media types (GMD), suppliers, and supporting metadata, including multiple-author and multiple-subject relationships for a single book. Classification is assisted by DDC data stored in the application.

Member, membership-type, student, class, department, subject, academic-year, school, and organisational-unit records provide reference data for circulation services. Workflows cover loans with details and histories, returns with book-status updates, and overdue fines and their payments. Visitors are recorded through a guest book and visit lists.

The API uses JWT authentication, pagination with page and size parameters on almost all list endpoints, and Excel imports that store problematic rows in a temporary table for correction. Book covers are processed and saved in application storage with image-format conversion. Additional modules cover notifications, broadcasts, reports, transaction histories, and library settings.

Feature inventory

Highlights

19 capabilities verified against the project source.

  • Book catalogue, book titles, and bibliographic metadata
  • Book copies with availability status
  • Book authors, publishers, categories, and subjects
  • Multiple-author and multiple-subject relationships for a single book
  • Language, media-type (GMD), and supplier reference data
  • DDC classification data to assist collection numbering
  • Member and membership-type management
  • Students, classes, departments, subjects, academic years, schools, and organisational units
  • Loan transactions with details
  • Book returns and loan-status updates
  • Loan histories by member and by book
  • Overdue-fine records and fine payments
  • Guest book and library visit lists
  • Library reports and transaction histories
  • Notifications and broadcast endpoints
  • Library settings and configuration
  • Book-cover management with image-format conversion
  • Excel imports with problematic rows held for correction
  • JWT authentication, user management, and pagination on list endpoints

Tech stack

Built with 7 technologies.

  • Lumen 8
  • PHP 8
  • MySQL
  • JWT Auth
  • Maatwebsite Excel
  • Flysystem
  • REST API

Common questions

What people usually ask.

How large is the API?

Over 200 endpoints covering catalogue, members, circulation, fines, visits, broadcasts, reports, and settings, with pagination on nearly every list endpoint and JWT authentication throughout.

Does it help with classification?

Yes. DDC data is stored in the application to assist collection numbering, alongside multiple-author and multiple-subject relationships for a single title.

What happens to a bad row in an Excel import?

It is held in a temporary table for correction rather than failing the whole import, so a librarian fixes the handful of problem rows instead of restarting.

Same field

Need something like this?

Send a short brief and I’ll come back with scope, approach, and an honest timeline.