Explain this Database like a presentation, please make it as detailed as possibl

Question

Explain this Database like a presentation, please make it as detailed as possible and for at least 6 minutes:

This is background of the database:

A Case for Demonstrating Conceptual and Logical Database Design
(General and Not Catered to the Oracle XE DBMS)

The Library Department of a public undergraduate university wants to keep track of its
users, holdings, and users' checking out of different kinds of holdings.
There are exactly three kinds of users. They all have one user identity number, one name,
one address, one phone number, and a user type. If user type is "STU," then this user is a
student. The class (integer) needs to be recorded. The class value can only be 1, 2, 3, or 4.
If user type is "STA," then this user is a staff member. The rank description needs to be
recorded. If user type is "COM," then this user is a community user. The expiration date
of his/her membership needs to be recorded.
There are exactly three kinds of library holdings. Each has one call number for
identification, one title, and one section code. The first kind is books for regular
circulation with a section code "CIR." There can be zero to three author names for each
one. There can also be a subtitle which is optional. The second kind is books in the
Reference section with a section code "REF." The publisher of such a book needs to be
recorded. It can also have one optional subtitle as well. The third kind is periodicals. For
each title, it has section code "PER" and a call number. The current volume and current
number need to be recorded and they are not a part of the call number of a periodical title.
Each holding must belong to one and only one section at any time.
Any library user can check out any number of books for circulation for two weeks at a
time. For each loan, the due date has to be recorded. A library user can check out up to
three books in the Reference section for four hours. Both a due date and a due time need
to be recorded. Lastly, a library user can check out up to five different issues of all
periodicals for four hours. For each one, the volume, the number of that particular issue,
a due date, and a due time need to be recorded.

Page 2 of 6
The Static Conceptual Schema for the Library Case

The PERIODICAL participation of CHECKS-OUT-P is 0:n because each PERIODICAL entity
instance is for a periodical title, not an individual issue of a periodical.

Page 3 of 6

The Attributes in the EER Diagram:
(In the Conceptual Schema, the inherited attributes in a subclass do not have to be
repeated. It is understood that BOOK-CIR also has H-CALL-NO and it is an inherited key
attribute.)
Attribute Attribute
Entity Attribute Domain Cardinality
-------------------------------------------------------------------------------------------------------------
HOLDING H-CALL-NO STRING 1:1
H-TITLE STRING 1:1
H-SECTION STRING 1:1
“CIR,” “REF,” and “PER”
BOOK-CIR B-SUBTITLE STRING 0:1
B-AUTHOR STRING 0:3

REFERENCE R-SUBTITLE STRING 1:1
R-PUBLISHER STRING 1:1
PERIODICAL CUR-VOL INTEGER 1:1
CUR-NO INTEGER 1:1
USER U-ID STRING 1:1
U-NAME STRING 1:1
U-ADDR STRING 1:1
U-PH-NO STRING 1:1
Format: “(xxx)xxx-xxxx”
U-TYPE STRING 1:1
“STU,” “STA, “COM”
Candidate Key 1 of USER: U-ID
Candidate Key 2 of USER: U-NAME, U-ADDR
STUDENT CLASS INTEGER: 1:1
1, 2, 3, and 4

STAFF RANK STRING 1:1
COMMUNITY- MEM-EXP-DATE DATE 1:1
USER

Attribute Attribute
Relationship Attribute Domain Cardinality
---------------------------------------------------------------------------------------------------------------
CHECKS-OUT-C C-DUE-DATE DATE 1:1

CHECKS-OUT-P P-VOL INTEGER 1:1
P-NO INTEGER 1:1
P-DUE-DATE DATE 1:1
P-DUE-TIME TIME 1:1

CHECKS-OUT-R R-DUE-DATE DATE 1:1
R-DUE-TIME TIME 1:1

Page 4 of 6

The Static Part of the Logical Schema (Output of Logical Database Design):
(This is a general logical schema, not specific to Oracle XE)
HOLDING(H-call-no, H-title, H-section)
BOOK-CIR(H-call-no, B-subtitle)
BOOK-AUTHOR(H-call-no, Author)
REFERENCE (H-call-no, R-subtitle, R-publisher)
PERIODICAL(H-call-no, Cur-vol, Cur-no)
[H-call-no of BOOK-CIR, BOOK-AUTHOR, REFERENCE, and PERIODICAL are also
foreign keys that reference the primary key, H-call-no, of HOLDING.]
USER(U-ID, U-name, U-addr, U-ph-no, U-type)
STUDENT(U-ID, Class) [U-ID is a foreign key that references U-ID of USER.]
STAFF(U-ID, Rank) [U-ID is a foreign key that references U-ID of USER.]
COMMUNITY-USER(U-ID, Mem-exp-date)
[U-ID of STUDENT, STAFF, COMMUNITY-USER are foreign keys that reference the
primary key, U-ID, of USER.]
CHECKS-OUT-CIR(U-ID, H-call-no, C-due-date)
CHECKS-OUT-PERIODICAL(U-ID, H-call-no, P-vol, P-no, P-due-date, P-due-time)
CHECKS-OUT-REFERENCE(U-ID, H-call-no, R-due-date, R-due-time)

[U-ID of CHECKS-OUT-CIR, CHECKS-OUT-PERIODICAL, and CHECKS-OUT-
REFERENCE are foreign key attributes that reference the primary key, U-ID, of USER.]

[H-call-no of CHECKS-OUT-CIR, CHECKS-OUT-PERIODICAL, and CHECKS-OUT-
REFERENCE are foreign key attributes that reference the primary key, H-call-no, of

HOLDING.]

Page 5 of 6

Attribute NULL
Relation Attribute Domain Allowed
----------------------------------------------------------------------------------------------------------
USER U-ID STRING no
U-name STRING no
U-addr STRING no
U-ph-no STRING no
Format: “(xxx)xxx-xxxx”
U-type STRING no
“STA”, “STU” and “COM”
STUDENT U-ID STRING no
Class INTEGER: no
1, 2, 3, and 4

STAFF U-ID STRING no
Rank STRING no
COMMUNITY- U-ID STRING no
USER Mem-exp-date DATE no

HOLDING H-call-no STRING no
H-title STRING no
H-section STRING no
“CIR”, “REF” and “PER”
BOOK-CIR H-call-no STRING no
B-subtitle STRING yes
BOOK-AUTHOR H-call-no STRING no

Author STRING no (if there is no author for a book,
no entries needed in this table)

REFERENCE H-call-no STRING no
R-subtitle STRING no
R-publisher STRING no
PERIODICAL H-call-no STRING no
Cur-vol INTEGER no
Cur-no INTEGER no

Page 6 of 6

Attribute NULL
Relation Attribute Domain Allowed
-------------------------------------------------------------------------------------------------------------
CHECKS-OUT-C U-ID STRING no
H-call-no STRING no
C-due-date DATE no

CHECKS-OUT-P U-ID STRING no
H-call-no STRING no
P-vol INTEGER no
P-no INTEGER no
P-due-date DATE no
P-due-time TIME no

CHECKS-OUT-R U-ID STRING no
H-call-no STRING no
R-due-date DATE no
R-due-time TIME no

dinteser(PK Has + phone nadring 1r(PK) usmgsr IF) d USER TYPE Has + (PK) Student Has Has Has HOLDING SECTIONd 1n :n dintagar (PK)

Explanation / Answer

Library Management System is a software used to manages the catalog of a library. This helps to keep the records of whole transactions of the books available in the library.

AmpleTrails provides Library Management System which is very easy to use and fulfills all the requirement of a librarian. There are many features which helps librarian to keep records of available books as well as issued books. This software is available in both mode i.e. web-based or local host based. We provide best Library Management System of this planet.

Here is a list of some features of Library Management System which AmpleTrails offer:

Related Questions

Navigate

• Browse (All)
• Browse E
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.