What this module is for
Manage books, book copies, categories, shelves, authors, circulation, reservations, fines, reports, and settings.
Prerequisites
- Library permissions assigned
- Library setup completed
- Books and copies created before circulation
Main screens
Step-by-step workflows
Set up library catalog
- Configure categories, shelves, authors, and related setup values.
- Create book records.
- Add physical copies for each book.
- Use copy status to understand availability.
Issue and return books
- Open Circulation.
- Select borrower and copy.
- Issue the copy through the normal form.
- Return the copy when received.
- Review overdue and fine records where applicable.
Operational detail
Permission checkpoints
- Library setup, catalog, copies, circulation, reservations, fines, reports, and settings are permission checked.
- Issue and return actions change copy availability and borrower history, so they must be performed through the circulation workflow.
- Fine visibility depends on library permission and school policy.
Field guidance
Store the title, category, author, publisher, subject, ISBN or code, and status for catalog search.
Each physical copy should have a unique copy/accession code and availability status.
Select a valid student or staff borrower according to the library circulation rules.
Use the actual issue date because due date, overdue status, and reports depend on it.
Return copies through the return action so availability, overdue, and fine states are recalculated correctly.
Use reservations to manage demand for unavailable books without creating a false issue record.
Validation and system feedback
- Only available copies should be issued.
- A borrower must be valid for the authenticated school and permitted borrower type.
- Return actions must match an open issue record.
- Overdue and fine records should be reviewed through library reports or fine screens.
Common mistakes to avoid
- Creating one book record but no physical copies.
- Editing copy status manually instead of issuing or returning through circulation.
- Issuing the same copy twice while it is already out.
- Using reservation as a substitute for return or renewal.
Recommended next steps
Screenshot plan
Final public screenshots will use synthetic QA data only. Sensitive values such as names, phone numbers, emails, admission numbers, document numbers, credentials, cookies, tokens, and internal IDs must be removed or redacted.
Important safety notes
Use normal Schoolixa workflows
Public docs explain user workflows only. They do not expose internal IDs, direct database operations, credentials, provider prompts, or private system configuration. Permission visibility in the interface does not replace server-side permission checks.