This ER diagram presents a library management system featuring entities such as "Book," "Member," "Loan," "Author," and "Genre," where books are uniquely identified with attributes like Title, AuthorID (referencing Author), and GenreID (referencing Genre), members are identified by Name and Address, loans include details such as LoanDate and ReturnDate, and authors are identified by Name and Biography, while genres have attributes like Name and Description. Connections between these entities illustrate how members borrow books, books relate to authors and genres, and book loans are managed within the system.

erd-library-management.png

Edit this diagram in Gleek

Library management system diagram code in Gleek

Book

    UniqueIdentifier BookID PK "Unique identifier"

    String Title "Book title"

    UniqueIdentifier AuthorID FK "Reference to Author entity"

    UniqueIdentifier GenreID FK "Reference to Genre entity"

Member

    UniqueIdentifier MemberID PK "Unique identifier"

    String Name "Member name"

    String Address "Member address"

    String Phone "Member phone number"

Loan

    UniqueIdentifier LoanID PK "Unique identifier"

    UniqueIdentifier BookID FK "Reference to Book entity"

    UniqueIdentifier MemberID FK "Reference to Member entity"

    Date LoanDate "Date of loan"

    Date ReturnDate "Date of return"

Author

    UniqueIdentifier AuthorID PK "Unique identifier"

    String Name "Author name"

    String Biography "Author biography"

Genre

    UniqueIdentifier GenreID PK "Unique identifier"

    String Name "Genre name"

    String Description "Genre description"

Member {1}-borrows-{1..n} Book

Book {1}-has-{1..n} Author

Book {1}-has-{1..n} Genre

Book {1}-borrowed-{1..n} Loan

About ER diagrams

We often make an entity-relationship (ER) diagram, ERD, or entity-relationship model, in the early stages of designing a database. An ERD is perfect for quickly sketching out the elements needed in the system. The ERD explains how the elements interact. ER diagrams can be shared with colleagues. Their simplicity makes them ideal even for non-technical stakeholders.

Similar ER diagram examples

Online store entity-relationship diagram

Employee management system entity-relationship diagram

Banking system entity-relationship diagram

Travel management system Er diagram

College management system ER diagram

Library management system ER diagram with Chen notation

E-commerce website ER diagram

Hospital management system entity-relationship diagram