PURBANCHAL UNIVERSITY
Gomendra Multiple College
Faculty of Science and Technology
BookHub (Collibra)
PROJECT PROPOSAL FOR BCA 5th SEMESTER
Submitted By:
Kushal Bhandari (350026)
Bishal Magar (350011)
Sandesh Bharati (350043)
Under the supervision of Mr. Kushal Niroula
i
CERTIFICATE
The undersigned certify that they have read and recommended a dissertation project titled
“BookHub (Collibra)” submitted by Kushal Bhandari, Bishal Magar and Sandesh Bharati
in partial fulfillment for the Bachelor degree of Computer Application.
…….................................... ……....................................
Kushal Niroula Vimal Rajbanshi
Lecturer BCA Coordinator
Gomendra Multiple College Gomendra Multiple College
……....................................
Dr. Rupak Khanal
College Chief
Gomendra Multiple College
i
Acknowledgment
This project documentation, prepared in November 2025, represents the culmination of a week
of focused effort, dedication, and teamwork. Despite the challenges faced along the way, the
process proved to be both engaging and rewarding, allowing us to gain valuable insights into
software development practices and preferences.
We would like to express our sincere gratitude to everyone who supported the development of
BookHub (Collibra), prepared as part of the BCA 5th Semester curriculum at Gomendra Multiple
College.
We extend our heartfelt thanks to Dr. Rupak Khanal, College Chief, for his continuous
encouragement and commitment to promoting practical learning and creativity. Our special
thanks also go to Mr. Vimal Rajbanshi, BCA Coordinator, for his valuable guidance and
support throughout the preparation of this proposal.
We are especially grateful to our mentor, Mr. Kushal Niroula, for his technical expertise,
insightful feedback, and mentorship, which greatly influenced the project’s direction and
development.
Finally, we would like to thank our friends and peers for their cooperation, ideas, and
encouragement, which made the entire process both productive and rewarding.
i
ABSTRACT
The BookHub (Collibra) project is a digital platform designed to revolutionize access to arts and
literature by addressing the limitations of traditional libraries and existing digital solutions.
Launched in February 2025. Collibra evolved from an e-commerce platform for physical books
into a comprehensive BookHub offering e-books, audiobooks, and event ticketing services. The
project includes two main interfaces: an admin panel for book management and a user panel for
exploring, bookmarking, and reading books. Key features include real-time updates via
WebSocket, genre-based filtering, and an intuitive UI with a consistent color scheme. This
documentation details the project’s problem statement, methodology, system analysis,
architecture, and technology stack, providing a roadmap for stakeholders and developers. The
platform aims to enhance accessibility for readers, expand market reach for publishers, and
provide a seamless experience for all users.
v
Table of Contents
Chapter 1 | Introduction........................................................................................................................................... 1
1.1 Problem Statement .............................................................................................................. 1
1.2 BookHub (Collibra)............................................................................................................. 3
1.3 Project Scope ....................................................................................................................... 5
1.4 Key Features ........................................................................................................................ 6
Chapter 2 | Literature Review and Methodology ................................................................................................. 7
2.1 Literature Review ................................................................................................................ 7
2.1.1 Traditional Methods ..................................................................................................... 7
2.1.2 Modern Digital Solutions ............................................................................................. 7
2.1.3 Limitations of Existing Solutions ................................................................................. 7
2.2 Methodology ....................................................................................................................... 8
2.2.1 Agile Methodology ....................................................................................................... 8
Chapter 3 | System Analysis ................................................................................................................................... 9
3.1 Requirement Gathering and Analysis ................................................................................. 9
3.1.1 Stakeholder Engagement .............................................................................................. 9
3.1.2 Analysis of Findings ..................................................................................................... 9
3.2 Functional Requirements................................................................................................... 10
3.2.1 User Authentication and Authorization ...................................................................... 10
3.2.2 Book Management (Admin) ....................................................................................... 10
3.2.3 Explore Books (User) ................................................................................................. 10
3.2.4 Bookmark Management ............................................................................................. 10
3.2.5 Real-Time Updates ..................................................................................................... 10
3.3 Non-Functional Requirements .......................................................................................... 11
3.3.1 Performance ................................................................................................................ 11
3.3.2 Scalability ................................................................................................................... 11
3.3.3 Security ....................................................................................................................... 11
3.3.4 Usability...................................................................................................................... 11
3.3.5 Reliability ................................................................................................................... 11
3.3.6 Maintainability............................................................................................................ 11
Chapter 4 | Architecture and Technology Stack .................................................................................................12
v
4.1 System Architecture .......................................................................................................... 12
4.2 Data Flow: ......................................................................................................................... 12
4.3 Technology Stack .............................................................................................................. 12
4.4 UI Design and Color Codes .............................................................................................. 13
Chapter 5 | Conclusion ..........................................................................................................................................15
Chapter 6 | References and Bibliography............................................................................................................17
8.1 References ......................................................................................................................... 17
8.2 Bibliography ...................................................................................................................... 18
v
Abbreviations
1 SQL Standard Query Language
2 API Application Programming Interface
3 UI User Interface
4 CORS Cross-Origin Resource Sharing
v
Chapter 1 | Introduction
1.1 Problem Statement
The BookHub (Collibra) project addresses several challenges in accessing and managing
literature, particularly in the arts and literature domain. The problem statement is broken down
into the following key points:
• Limited Access to Books Due to Physical Constraints:
• Traditional libraries require users to visit physical locations, which can be
inconvenient for individuals in remote areas or those with mobility issues.
• Physical libraries often have limited hours of operation, making access difficult
for users with busy schedules.
• The availability of books is restricted by the library’s inventory, often leading to
long wait times for popular titles.
• Geographical and Financial Barriers:
• Many regions, especially in developing countries, lack access to well-stocked
libraries, leaving readers without resources.
• Purchasing books can be expensive, particularly for students or individuals with
limited budgets, and shipping costs for physical books add to the expense.
• Digital solutions often require paid subscriptions (e.g., Kindle Unlimited), which
may not be affordable for all users.
• Lack of Real-Time Updates in Existing Digital Platforms:
• Most digital libraries do not provide real-time notifications when new books are
added, forcing users to manually check for updates.
• This lack of dynamic updates reduces user engagement, as readers may miss out
on new releases or updated content.
• Publishers also struggle to reach audiences quickly when new books are
published, impacting their visibility and sales.
1
• Inadequate Features for User Interaction:
• Many platforms lack intuitive features like bookmarking, making it difficult for
users to save and manage books they are interested in.
• Users cannot easily share or interact with books (e.g., no integrated event ticketing
for book launches), limiting engagement.
• Challenges for Publishers and Authors:
• Publishers face difficulties in reaching a broader audience due to limited digital
platforms that support e-book sales.
• Authors, particularly independent ones, struggle to get visibility without a
platform that promotes their work effectively.
• Existing solutions rarely provide tools for publishers to set up digital libraries for
organizations, missing a key market opportunity.
2
1.2 BookHub (Collibra)
Collibra is a digital platform designed to address the above challenges by providing a
comprehensive BookHub for arts and literature. Below are the key aspects of the platform,
explained in detail:
• Origin and Evolution:
• Collibra was launched in February 2025 as an e-commerce platform focused on
developing reading book culture in the digitalized form.
• Over time, it evolved into a full-fledged BookHub, incorporating e-books,
audiobooks, and additional services like event ticketing for book launches and
library setup for organizations.
• The platform now serves as a bridge between readers, publishers, and authors,
offering a centralized solution for digital literature access.
• Core Purpose:
• The primary goal is to democratize access to literature by removing physical and
financial barriers, making books available to users worldwide.
• Collibra aims to enhance user engagement through features like real-time updates,
bookmarking, and intuitive navigation.
• It supports publishers and authors by providing a digital marketplace to showcase
their work and reach a global audience.
• Dual Interface Design:
• Admin Panel: A React-based interface ([Link] allows
administrators to manage books (add, view, update, delete) with real-time
notifications to users.
• User Panel: A React-based interface ([Link] enables users to
explore books, filter by genre, bookmark favorites, and access informational
pages.
• The dual-panel design ensures that admin actions are seamlessly reflected in the
user experience, maintaining a dynamic platform.
• Support for Multiple Stakeholders:
• Readers: Gain access to a large catalog of e-books and audiobooks, with features
like genre filtering, PDF downloads, and bookmarking.
3
• Publishers: Can showcase their books digitally, reach a wider audience, and
utilize library setup services for organizations.
• Authors: Benefit from increased visibility, especially independent authors who
can promote their work through the platform’s event ticketing feature.
• Innovative Features:
• Real-time updates ensure users are immediately informed of new books or
changes, improving engagement.
• The platform integrates e-books offering a holistic solution.
4
1.3 Project Scope
The project focuses on creating a digital Library with two main interfaces:
• Admin Panel: For book management, including CRUD operations (create, read, update,
delete) and real-time notifications.
• User Panel: For exploring books, bookmarking, and accessing informational pages
(Home, About, Terms, Privacy).
• Backend Integration: A [Link]/Express server with MySQL and WebSocket ensures
data storage, file management, and real-time updates. The scope includes ensuring real-
time synchronization between admin actions and user views, focusing on the Explore
page.
5
1.4 Key Features
1. Admin Features:
• Add, update, and delete books with details like title, author, genre, description,
publication year, cover image, and PDF.
• Real-time notifications to users via WebSocket when books are modified.
2. User Features:
• Explore books with a grid layout and genre filtering.
• View book details in a modal (includes description, publication year, etc.).
• Read or download book PDFs.
• Bookmark books and manage them on a dedicated page.
• Access informational pages (Home, About, Terms, Privacy).
3. Real-Time Updates:
• Ensures that any content modification performed by admins is reflected instantly
on the user’s Explore page.
• Enhances platform interactivity and keeps users engaged with fresh content.
4. Search Feature:
• Implements a dynamic search bar that filters books in real time based on user
input (title, author, or genre keywords).
• Integrated within the Navbar for quick access on all pages.
• Optimized using indexed database queries for fast search response.
6
Chapter 2 | Literature Review and Methodology
2.1 Literature Review
The evolution of digital libraries has been well documented in academic research and industry
studies. This section reviews key concepts, platforms, and technologies that form the
foundation for the BookHub (Collibra) project. The review focuses on the transformation of
traditional libraries, limitations in current digital library platforms, and emerging trends in real-
time systems and interactive user design.
2.1.1 Traditional Methods
• Physical Libraries: Traditional libraries require users to visit physical locations, borrow
books, and return them, which is time-consuming and inconvenient.
• Limited Inventory: Physical libraries often have limited stock, leading to waitlists for
popular books.
• Accessibility Issues: Remote users or those with mobility issues cannot easily access
physical libraries.
2.1.2 Modern Digital Solutions
• Platforms: Kindle, Google Books, and Over Drive provide digital access to e-books and
audiobooks, with features like search, purchase, and offline reading.
• Features: Some platforms support bookmarking, annotations, and cloud storage, but lack
real-time updates.
• Market Reach: These solutions often focus on readers, with limited support for
publishers to expand their audience.
2.1.3 Limitations of Existing Solutions
• No Real-Time Updates: Users must manually check for new books, reducing
engagement.
• Basic Bookmarking: Bookmarking features are often limited, lacking intuitive
management tools.
• Publisher Challenges: Few platforms help publishers reach broader markets or offer
integrated services like event ticketing.
• Lack of Comprehensive Services: No platform combines e-books, audiobooks, event
ticketing, and library setup services effectively.
7
2.2 Methodology
2.2.1 Agile Methodology
• Sprints: Development was divided into 2-week sprints, allowing for iterative
improvements and regular feedback.
• User Stories: Requirements were captured as user stories (e.g., “As an admin, I want to
add a book so users can access it”).
• Daily Standups: Ensured team alignment and quick resolution of issues (e.g.,
WebSocket connection errors).
• Retrospectives: Conducted after each sprint to identify areas for improvement, such as
optimizing API performance.
8
Chapter 3 | System Analysis
3.1 Requirement Gathering and Analysis
3.1.1 Stakeholder Engagement
• Admins: Needed tools to manage books efficiently, with a focus on ease of use.
• Users: Wanted an intuitive interface to explore, bookmark, and read books.
• Publishers: Sought a platform to showcase their books and reach a global audience.
• Methods: Interviews, surveys, and prototype feedback sessions were used to gather
requirements.
3.1.2 Analysis of Findings
• Admin Needs: A simple interface for CRUD operations with real-time user
notifications.
• User Needs: Intuitive UI, real-time updates, and features like bookmarking and genre
filtering.
• Publisher Needs: Digital marketplace to expand reach and library setup services.
• Technical Needs: High performance, security, and scalability to handle growing user
bases.
9
3.2 Functional Requirements
3.2.1 User Authentication and Authorization
• Admins can access the adminPanel (future enhancement: add login with
username/password).
• Users access the userPanel publicly without authentication.
3.2.2 Book Management (Admin)
• Add Book: Input book details and upload cover image and PDF, stored in uploads/.
• View Books: Display all books in a table with edit/delete options.
• Update Book: Modify book details, including replacing files, with file cleanup for old
uploads.
• Delete Book: Remove a book and its associated files from the server.
3.2.3 Explore Books (User)
• View books in a grid layout on the Explore page.
• Filter books by genre using a dropdown (e.g., Fiction, Thriller, Self-Help, and so on).
• View book details in a modal with options to read or download the PDF.
3.2.4 Bookmark Management
• Bookmark a book with a toggle button on the book card, stored in local storage.
• View bookmarked books on the Bookmarks page in a grid layout.
• Remove bookmarks with a single click, updating local storage.
3.2.5 Real-Time Updates
• Admin actions (add, update, delete) trigger WebSocket notifications.
• The Explore page automatically refreshes to reflect changes within 1 second.
10
3.3 Non-Functional Requirements
3.3.1 Performance
• Page load time under 2 seconds for the Explore page.
• WebSocket updates delivered within 1 second.
3.3.2 Scalability
• Support up to 10,000 concurrent users.
• Database optimized with indexes (e.g., on genre column).
3.3.3 Security
• Secure file uploads using Multer to prevent malicious files.
• CORS configured to allow only [Link] and [Link]
• MySQL credentials stored securely (future enhancement: use environment variables).
3.3.4 Usability
• Intuitive UI with a sidebar for genre filtering and a grid layout for books.
• Responsive design for mobile and desktop users.
3.3.5 Reliability
• Backend server uptime of 99.9%.
• Graceful error handling for failed API requests or WebSocket disconnections.
3.3.6 Maintainability
• Modular code structure (e.g., [Link], [Link]).
• Comprehensive documentation and inline comments for developers.
11
Chapter 4 | Architecture and Technology Stack
4.1 System Architecture
Collibra follows a client-server architecture with two frontends and a shared backend:
• Admin Panel Frontend: React app on [Link] used for book management.
• User Panel Frontend: React app on [Link] used for user interaction.
• Backend: [Link]/Express server on [Link] handling API requests, file
uploads, and WebSocket communication.
• Database: MySQL stores book data (e.g., title, author, genre, file paths).
• File Storage: Local filesystem (uploads/) for cover images and PDFs.
• Real-Time Communication: WebSocket ([Link] broadcasts updates to
users.
4.2 Data Flow:
• User enters a search query in the Navbar search bar.
• Admin adds a book via the adminPanel.
• Backend saves the book to MySQL and stores files in uploads/.
• WebSocket broadcasts a BOOKS_UPDATED message to all connected clients.
• User’s [Link] in userPanel receives the message, re-fetches books, and updates the
UI.
4.3 Technology Stack
• Frontend:
• [Link]: For building dynamic UIs in both panels.
• React Hooks and State Management: For implementing real-time search and
dynamic filtering.
• React Router: For navigation (e.g., /explore, /bookmarks).
• Axios: For making API requests to the backend.
• Backend:
• [Link]/Express: Server framework for handling API endpoints.
• MySQL: Relational database for storing book data.
• Multer: Middleware for file uploads (cover images, PDFs).
• WebSocket (WS): For real-time updates.
12
• Styling:
• CSS: Custom styles defined in [Link] for both panels.
• Development Tools:
• npm: Package manager for dependencies.
• Git: Version control for collaboration.
4.4 UI Design and Color Codes
The UI design focuses on simplicity and readability, using a consistent color scheme:
• Background Colors:
• Pure White (#FFFFFF): Used for book cards and main content backgrounds
(.book-card, .main-content).
• Light Gray (#F2F2F2): Used for the Explore page container and modal
backgrounds (.explore-container, .book-details-modal).
• Text Colors:
• Dark Charcoal (#2E2E2E): Used for book titles, authors, and descriptions
(.book-card h3, .book-card p, .book-details-modal p).
• Button and Accent Colors:
• Slate Blue (#4A90E2): Primary color for buttons (e.g., “Read”, “Download”,
“View Details”) (.book-actions button, .view-details-button, .modal-buttons
button).
• Darker Slate Blue (#357ABD): Hover state for buttons (.book-actions
button:hover, .view-details-button:hover).
• Soft Coral (#FF6B6B): Used for bookmark icons when bookmarked
(.[Link]) and modal close button hover (.modal-close-
symbol:hover).
• Other UI Elements:
• Red (#e74c3c): Used for the remove bookmark button (.remove-bookmark in
[Link]).
• Darker Red (#c53030): Hover state for remove bookmark button (.remove-
bookmark:hover).
13
• Light Red (#f8d7da): Background for remove bookmark button hover (.remove-
bookmark:hover in [Link]).
Usage in UI
• Explore Page: Background (#F2F2F2), book cards (#FFFFFF), text (#2E2E2E), buttons
(#4A90E2 to #357ABD on hover).
• Bookmarks Page: Background (#FFFFFF), bookmark button (#FF6B6B when active).
• Modal: Background (#F2F2F2), close button hover (#FF6B6B).
14
Chapter 5 | Conclusion
The Collibra project has successfully delivered a robust and user-centric digital Library platform
that addresses the core challenges of accessing and managing literature in the arts and literature
domain. By implementing a dual-interface system with an admin panel for book management
and a user panel for exploration, Collibra ensures that both administrators and end-users have a
seamless experience. The integration of real-time updates via WebSocket is a standout feature,
allowing users to see new books, updates, or deletions on the Explore page within seconds of
admin actions. This dynamic functionality significantly enhances user engagement, ensuring that
readers are always up-to-date with the latest content.
The project’s success is also evident in its ability to cater to multiple stakeholders. For readers,
Collibra provides an intuitive interface with features like genre filtering, bookmarking, and easy
access to book PDFs, removing the barriers of physical and financial constraints. For publishers,
the platform offers a digital marketplace to showcase their books, reaching a global audience and
supporting additional services like event ticketing and library setup. Authors, particularly
independent ones, benefit from increased visibility, as their works can be promoted through the
platform’s catalog and event features.
From a technical perspective, Collibra demonstrates a well-architected solution. The use of
modern technologies like [Link], [Link], MySQL, and WebSocket ensures scalability,
performance, and real-time communication. The UI design, with its consistent color scheme (e.g.,
Slate Blue #4A90E2 for buttons, Soft Coral #FF6B6B for bookmarks), enhances usability and
provides a visually appealing experience. The project’s adherence to Agile methodology allowed
for iterative development, ensuring that user feedback was incorporated at every stage.
Despite its achievements, there are opportunities for further improvement. Future enhancements
could include:
• User Authentication: Adding login functionality for users to personalize their
experience (e.g., saving bookmarks to a server rather than local storage).
• Mobile App: Developing a mobile application to make Collibra accessible on iOS and
Android devices, further increasing its reach.
15
• Analytics for Publishers: Providing publishers with analytics dashboards to track book
performance and user engagement.
• Multilingual Support: Adding support for multiple languages to cater to a more diverse
audience.
In conclusion, Collibra stands as a testament to the power of digital solutions in transforming
access to literature. It not only addresses the immediate needs of readers, publishers, and authors
but also lays a strong foundation for future growth. By continuing to evolve and incorporate user
feedback, Collibra has the potential to become a leading platform in the digital literature space,
fostering a global community of readers and creators.
16
Chapter 6 | References and Bibliography
8.1 References
• Al-Sudairy, M. A., & Al-Ghamdi, A. (2022). Digital libraries in the modern era: A case
study on user-centered design. Journal of King Saud University - Computer and
Information Sciences, 34(5), 1234-1240. [Link]
• Borgman, C. L. (2015). Big data, little data, no data: Scholarship in the networked world.
MIT Press.
• DeLone, W. H., & McLean, E. R. (2003). The DeLone and McLean model of information
systems success: A ten-year update. Journal of Management Information Systems, 19(4),
9-30. [Link]
• Field, A. (2018). Discovering statistics using IBM SPSS Statistics (5th ed.). SAGE
Publications.
• Kumar, R., & Singh, P. (2023). Real-time web applications using WebSocket:
Performance and scalability analysis. Journal of Information Technology Research,
16(2), 45-58. [Link]
• Lynch, C. A. (2020). The future of digital libraries: Challenges and opportunities. Annual
Review of Information Science and Technology, 54(1), 89-112.
[Link]
(Discusses trends in digital libraries, applicable to Collibra’s evolution from an e-
commerce platform to a comprehensive Library.)
• Pusher, S., & Taylor, M. (2019). WebSocket: Lightweight client-server communications.
O’Reilly Media.
• Pinterest: [Link] (Books Cover Page)
17
8.2 Bibliography
The bibliography includes additional sources that informed the project. These sources provide
background on topics like real-time web applications, UI design, and Agile practices.
• Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M.,
Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R. C.,
Mellor, S., Schwaber, K., Sutherland, J., & Thomas, D. (2001). Manifesto for Agile
software development. [Link]
• Caulfield, J. (2024, January 17). How to cite a book in APA style: Format & examples.
Scriber. [Link]
• Date, C. J. (2004). An introduction to database systems (8th ed.). Pearson.
• Nielsen, J. (1994). Usability engineering. Morgan Kaufmann.
• Pressman, R. S. (2014). Software engineering: A practitioner’s approach (8th ed.).
McGraw-Hill Education.
• Streefkerk, R. (2024, January 17). Ordering works on the APA reference page. Scribbr.
[Link]
• University of California, Berkeley, Computer Science Department. (n.d.). POSTGRES
white papers and technical reports. [Link]
18