PRODUCT CONTEXT:

The Library module provides visibility into a student’s reading activity within the school’s physical library. It displays books issued to the student, their expected return dates, overdue indications, and return confirmations. The module helps parents and students stay informed about reading habits and ensures timely returns to support responsible academic behavior.

FEATURE DESCRIPTION:

The Library module automatically receives book issuance and return updates from the school’s library management system (Skolaro). It displays this information in a structured, easy-to-understand format within the LMS on both web and mobile platforms. Parents and students receive notifications when a book is issued, returned, or overdue.

PLATFORMS SUPPORTED:

• Web
• Mobile

PERSONAS INVOLVED:

• Parent
• Student

BUSINESS RULES:

• Skolaro (3rd-party) triggers issue/return events to LMS via API.
• LMS stores and displays these events in the Library tab under Student Profile.
• LMS computes overdue status automatically when expected return date has passed without a return event.
• Data is displayed in tabular (web) or card (mobile) format with clear status indicators.

PERMISSIONS LOGIC:

• Student_Library_View — Allows students to see the Library module.
• Parent_Library_View — Allows parents to see the Library module for their child.

NOTIFICATIONS:

• In-app notifications for Parents and Students:
– When a book is issued
– When a book is returned
– When a book becomes overdue

1. Introduction

The Library feature provides a transparent and structured view of a student’s reading activity through the school library. It exists to:

Why the Feature Exists

• Promote awareness of students’ reading habits.
• Improve communication between school and home regarding library engagements.
• Encourage timely return of borrowed books.

What Problem It Solves

• Parents currently have limited visibility into library interactions.
• Students often forget return dates due to lack of reminders or centralized tracking.
• Schools face overdue returns, causing operational delays.

Who Benefits

• Parents — visibility into reading choices and responsibility habits.
• Students — a clear view of borrowed books and reminders.
• School stakeholders — reduced overdue management load.

How It Improves the System

• Creates a unified academic profile by integrating library activity.
• Reduces missed due dates through clear notifications.
• Fosters positive reading behavior.

2. Role-Based Access Overview

RBAC Table

Role	Web Access	Mobile Access	Create	Edit	Delete	View
Parent	Yes	Yes	No	No	No	Yes (Parent_Library_View)
Student	Yes	Yes	No	No	No	Yes (Student_Library_View)

LMS displays Library information only to Student & Parent personas.

RBAC Logic

• Access is purely view-only.
• Permissions must be explicitly granted at user-role level.
• Notifications are received regardless of permissions, but opening them will respect RBAC.

3. Super Admin Guide

3.1 Responsibilities

• Oversee configuration of incoming APIs.
• Ensure RBAC mapping is correct.
• Monitor ingestion logs.

3.2 Administration

• Verify Skolaro → LMS API is active.

3.3 Configuration

• Maintain API credentials in secure configuration layer.

3.4 Permissions

• Ensure Parent_Library_View and Student_Library_View are assigned correctly.

3.5 Reporting
• Access ingestion reports and logs if required.

3.6 Use Cases

• Troubleshooting when ingestion fails.
• Supporting school admins reporting missing transactions.

4. HO Admin Guide

HO admins do not access the Library feature.

5. School Admin Guide

School admins do not access the Library feature.

6. Teacher Guide

Teachers do not access the Library feature.

7. Parent Guide (Web & Mobile)

7.1 Access

• Parent navigates: Student Profile → Library.
• Requires Parent_Library_View permission.

7.2 Default View & Navigation

• Two tabs:
– History
– Library Analytics (basic placeholder)

7.3 What Parents Can Do

• View books issued.
• View expected return date.
• View returned books.
• View overdue indicator.
• Receive notifications.

7.4 Notifications

Parents receive:
• Book Issued
• Book Returned
• Book Overdue

7.5 Use Cases

• Tracking child’s reading activity.
• Ensuring timely book returns.

8. Student Guide (Web & Mobile)

8.1 Access

• Student navigates: Profile → Library.
• Requires Student_Library_View.

8.2 Default View & Navigation

Same UI as parent view.

8.3 What Students Can Do

• View their issued books and upcoming return dates.
• Understand which books are overdue.

8.4 Notifications

Students receive the same 3 notifications as parents.

8.5 Use Cases

• Managing personal responsibility for borrowed books.

9. How-To Guide

How to View Library Books (Parents & Students)

1. Log in to the LMS.
   
2. Open the Student Profile.
   
3. Select the Library tab.
   
4. View the History list of books.
   
5. Check the Return By date and status.
   

How Overdue Works (System Logic)

1. LMS checks expected return date.
   
2. If today > expected return date AND returned event not received → status becomes Overdue.
   
3. Overdue reminder notifications are triggered automatically.
   

How Notifications Work

1. Book Issued → Skolaro sends event → LMS triggers notification.
   
2. Book Returned → LMS updates status → notification sent.
   
3. Overdue → LMS computes & sends reminders.
   

10. Feature Logic & Display Rules

System Behavior

• LMS stores each Skolaro event.
• Status can be:
– Issued
– Returned
– Overdue

Display Hierarchy

• Web: Table format
• Mobile: Card format

Sorting Rules

• Latest issued books appear at the top.

Data Grouping

• Grouped by student profile.

Visibility Rules

• Only visible to Student & Parent personas with permissions.

11. Notifications Overview

Notification Types

1. Book Issued
   
2. Book Returned
   
3. Overdue Reminder
   

Triggers

• Triggered automatically during ingestion or overdue processing.

Audience

• Parent
• Student

Redirection Behavior

Each notification opens Library → History.

12. Governance & Compliance Rules

Business Rules

• LMS is only the visibility layer; Skolaro remains the operational system.
• No data editing is allowed in LMS.

Permission Rules

• Parent & Student only receive view access.

Restrictions

• No manual entries permitted.
• No editing or deleting entries.

System Validations

• Validate payload completeness.
• Validate enrollment mapping.
• Log and handle malformed data.

13. Frequently Asked Questions

Q1. Why don’t I see any book records?
The student has not taken any library books OR Skolaro has not sent an event.

Q2. Why can’t I edit or delete an entry?
Library operations occur only in Skolaro, not in the LMS.

Q3. Why did I receive an overdue reminder?
The expected return date has passed, and no return event was received.

Q4. What if a book was returned but still shows overdue?
The school may not have updated Skolaro yet.

Q5. Who can view the Library module?
Only Parents and Students with the appropriate RBAC permissions.

14. Conclusion

The Library module brings clarity and accountability to students’ reading activity by integrating Skolaro’s library data directly into the LMS. Parents and students benefit from transparent book history, timely reminders, and improved awareness of reading habits. By centralizing this information, the LMS strengthens academic communication and enhances the overall school–home ecosystem.