by
Faculties' publication bibliography is valuable information for many. Students are interested in which
faculty members are active in which field. Faculty members and university officials would like to
maintain the up-to-date bibliography information. For this reason, it is necessary
to develop an efficient and safe Faculty Publication Archiving and Retrieval System.
Students who take CS 387 Database Design
course at least offered by Dr. Cha are required to design
and implement a database application system as a
project requirement.
Those students can use this document as a template to write a final project report.
| DBMS | Oracle 8.0.5 |
| OS | Linux |
| GUI tool | Perl |
| HOSTNAME | matrix.csis.pace.edu |

There are seven entities and two relations.
Paper entity contains bibliography information about the paper.
The paper is divided into four entities because many attributes depend on publication types such as
journal, book chapters, conference proceedings, or technical reports, e.g.,
volume attribute is null for all other types of publication except for journal whereas conference name
attribute only occurs in the conference proceeding publication. Hence, it is necessary to divide the paper
into four different entities while the parent "Paper" entity contains all attributes that are
applicable for all types of publication
The mapping cardinality of the relationship called "writes" is "many to many"
because one faculty writes multiple papers and one paper can be coauthored by many authors. Hence,
the relationship,"writes", has an attribute called "a_order", to indicate the
order of the authors appearing on the paper.
The mapping cardinality of the relationship called "has_key" is "many to many"
because a keyword, "database" may appear in multiple papers and
one paper can have many keywords.
| Entity Authors | ||
| Attribute | type | Description |
|---|---|---|
| a_name | varchar2(30) | primary key, author's full name |
| affiliation | varchar2(40) | author's affiliation like CSIS Pace university |
| a_email | varchar2(40) | author's email address |
| a_url | varchar2(70) | author's homepage URL |
| a_title | varchar2(20) | author's title like Dr. |
| a_rank | varchar2(20) | author's rank like Associate Professor |
| Entity Paper | ||
| Attribute | type | Description |
|---|---|---|
| p_id | number(4) | primary key, unique identification number |
| title | varchar2(100) | Title of the paper |
| year | number(4) | published year like 1002 |
| month | number(2) | published month like 01 |
| page | varchar2(10) | pages like 1198-1230 |
| Publisher | varchar2(50) | Name of the publisher like 'IEEE Computer Society |
| urlloc | varchar2(100) | URL where the paper abstract or electronic copy can be found |
| status | varchar2(10) | current status like 'complete', 'in print', 'in review', etc |
| ptype | varchar2(50) | values are 'Academic',' Professional', or 'Dissertation' |
| Entity Journal | ||
| Attribute | type | Description |
|---|---|---|
| p_id | number(4) | primary key, unique identification number inherited from Paper |
| volume | number(3) | volume number |
| issue | number(2) | issue number |
| volume | varchar2(50) | The name of the Journal like 'IEEE Transaction on PAMI' |
| Entity Bchap (book chapters) | ||
| Attribute | type | Description |
|---|---|---|
| p_id | number(4) | primary key, unique identification number inherited from Paper |
| btitle | varchar2(70) | The name of the book |
| editors | varchar2(50) | list of editor full names |
| Entity Conf (Conference Proceedings) | ||
| Attribute | type | Description |
|---|---|---|
| p_id | number(4) | primary key, unique identification number inherited from Paper |
| place | varchar2(30) | The city or country where the conference was held. |
| cname | varchar2(50) | name of the conference like 'Computer Vision and Pattern Recognition' |
| refereed | varchar2(1) | T/F whether the paper was refereed |
| theurl | varchar2(100) | URL link to the conference homepage |
| ptype | varchar2(10) | type of presentation like 'oral', 'poster' or 'abstract' |
| Entity Tech_rep (technical reports) | ||
| Attribute | type | Description |
|---|---|---|
| p_id | number(4) | primary key, unique identification number inherited from Paper |
| institute | varchar2(30) | name of the institute which publishes |
| Entity Dictionary (no physical table) | ||
| Attribute | type | Description |
|---|---|---|
| keyword | word | primary key, input to server's dictionary program |
| meaning | text | the output of the dictionary result |
| Relation has_key (m-m) | ||
| Attribute | type | Description |
|---|---|---|
| keyword | word | foreign key to Dictionary |
| p_id | number(4) | foreign key to Paper |
| Relation writes (m-m) | ||
| Attribute | type | Description |
|---|---|---|
| p_id | number(4) | foreign key to Paper |
| a_name | varchar2(30) | foreign key to Authors |
| a_order | number(2) | order number where the author name appears in the paper |
Note that the system is partially implemented and the database contains neither all faculties nor all publications.