[FEATURE] Enhance Reporting and Analytics Capabilities

[sanchitc05]

Fixes #95

📊 Add Analytics Endpoints with Role-Based Access Control

Overview

This PR introduces new analytics endpoints to LibraryMan-API, providing valuable insights into library operations. The feature is specifically designed for administrators and librarians to track and analyze library usage patterns.

🚀 New Features

• Added role-based access control for analytics endpoints
• Restricted access to ADMIN and LIBRARIAN roles only
• Enhanced security configuration in WebConfiguration.java

🔒 Security Updates

.requestMatchers("/api/analytics/**").hasAnyRole("ADMIN", "LIBRARIAN")

🎯 Why This Matters

• Better Insights: Administrators and librarians can now make data-driven decisions
• Enhanced Security: Role-based access ensures data privacy
• Operational Efficiency: Easy access to important metrics for authorized personnel

🧪 Testing Checklist Please verify the following scenarios:

• [x] Analytics endpoints are accessible with ADMIN role
• [x] Analytics endpoints are accessible with LIBRARIAN role
• [x] Analytics endpoints are NOT accessible with USER role
• [x] Existing endpoints continue to work as expected
• [x] JWT authentication works correctly with new endpoints

📝 Example Usage

# Access analytics endpoint (requires ADMIN or LIBRARIAN token)
GET /api/analytics/books
Authorization: Bearer <your-jwt-token>

🔍 Review Focus Areas

1. Security configuration in WebConfiguration.java
2. Role-based access implementation
3. Integration with existing JWT authentication
4. Error handling for unauthorized access

📚 Documentation Updates

• Updated API documentation to include new analytics endpoints
• Added role requirements in security documentation
• Included usage examples for new endpoints

🤝 Testing Instructions

1. Clone the branch
2. Run the application
3. Test with different user roles:

# Login as ADMIN
POST /api/login
{
  "username": "admin",
  "password": "admin_password"
}

# Try accessing analytics
GET /api/analytics/books

🔄 Dependencies

• No new dependencies added
• Utilizes existing Spring Security configuration

⚠️ Important Notes

• This feature requires proper role configuration in the user database
• Existing ADMIN and LIBRARIAN accounts will automatically have access
• Remember to update environment variables if necessary

🌟 Future Enhancements

• Add more detailed analytics endpoints
• Implement data visualization endpoints
• Add customizable reporting periods
• Include export functionality for analytics data

🐛 Known Issues

• None at this time

📋 Checklist

• [x] Code follows project style guidelines
• [x] Added necessary documentation
• [x] Updated API documentation
• [x] Added/updated tests
• [x] All tests passing
• [x] No new warnings
• [x] Security review completed

💡 Questions or suggestions? Feel free to comment below!

🙏 Thank you for reviewing this PR. Your feedback is valuable and appreciated!

[Guhapriya01]

It looks like the findByMember_memberId method was removed from the Borrowing Repository. Could you please re-add it?

[sanchitc05]

Oh yeah sure @Guhapriya01

[sanchitc05]

@Guhapriya01 please review the changes and feel free to merge pr if everything looks good.

[sanchitc05]

@Guhapriya01 I have added Page<Borrowings> findByMember_memberId(int memberId, Pageable pageable); please feel free to merge it with required labels.