Database Design and Construction: Database Design - Definitions and Structure

By Hlava, Marjorie; Sawyer, Ed | Information Today, May 1992 | Go to article overview

Database Design and Construction: Database Design - Definitions and Structure


Hlava, Marjorie, Sawyer, Ed, Information Today


Last month, in part one of this series (April, Information Today, page 41), we described the major decision points that should be addressed before establishing a database. In this article, we will address more specific issues.

For the sake of clarity, it may be useful to begin by defining some database associated terms.

* Record--The basic unit of information, usually concerning one article, one person, or one transaction.

* File--A collection of records containing related information such as articles in a given subject area, resumes, or payroll records.

* Database--A structured collection of files. In the book Database Design for Information Retrieval (Wiley, 1987), Raya Fidel defines a database as "a single, central store of data with multiple usages."

* Field--The structure of a record is determined by the way data are broken down into specific elements such as a title or an author field. These may, in turn, be broken down into subfields such as last name, first name, and initial. In an address field the city and state could be subfields.

In larger organizations, or where multiple database exist, a Data Dictionary is usually built to define various data elements and their use. This allows for consistency across databases and throughout the organization.

* As mentioned in the previous article, the why and what type questions should be answered early on. Given satisfactory answers to such questions, the design process can now begin.

The structure of the database, the way the data elements are organized, is the initial design consideration. Only after fields, subfields, and the resultant records are laid out can input screens and output formats be created. It is often useful, however, to consider output or reporting requirements early in the design process to be sure that all of the data elements needed are actually included in the database and organized in a useful manner. At the same time the scope of the database must be addressed. Will it consist of only the currently available materials? Will an active acquisition program be mounted in order to continue acquiring similar data? What about the backlog? Is there a considerable number of retrospective documents? Will they all be input, or only a certain number acquired during a twelve month period?

The search logic to be used must be developed. This is also a function of the structure. A request to search the database by author would be meaningless, for example, if the field that contains the names included a mix of authors, editors, cited individuals, illustrators and publishers. However, it is possible to create generalized fields, such as name file, without regard to other elements. In this instance, to be useful the name field and the subfields should have a logical relationship to other data elements defined as author or illustrator, etc.

In any given database, some fields will be mandatory and others optional. This is an important consideration in setting up data entry screens and in developing the search strategies to be used.

Related issues revolve around which fields are designed to be searchable, what fields can be sorted (in what sequence), and whether numerical data will be used in calculation or ranges. Many databases allow searching in date ranges, i.e., from 1/1/85 to 1/1/92. To be able to sort dates in ranges requires that a consistent pattern be used in entering the dates. The date field/subfields are often set up so that data can only be entered in the correct format. Computers lend themselves to this type of editing, allowing the designer to set up masks or templates for data entry which check for simple errors like putting alphabetic characters in numeric fields or the reverse. Authority files or tables can also be built which serve as a screen or filter against which input data can be validated before its acceptance into the database.

The rest of this article is only available to active members of Questia

Sign up now for a free, 1-day trial and receive full access to:

  • Questia's entire collection
  • Automatic bibliography creation
  • More helpful research tools like notes, citations, and highlights
  • Ad-free environment

Already a member? Log in now.

Notes for this article

Add a new note
If you are trying to select text to create highlights or citations, remember that you must now click or tap on the first word, and then click or tap on the last word.
One moment ...
Project items

Items saved from this article

This article has been saved
Highlights (0)
Some of your highlights are legacy items.

Highlights saved before July 30, 2012 will not be displayed on their respective source pages.

You can easily re-create the highlights by opening the book page or article, selecting the text, and clicking “Highlight.”

Citations (0)
Some of your citations are legacy items.

Any citation created before July 30, 2012 will labeled as a “Cited page.” New citations will be saved as cited passages, pages or articles.

We also added the ability to view new citations from your projects or the book or article where you created them.

Notes (0)
Bookmarks (0)

You have no saved items from this article

Project items include:
  • Saved book/article
  • Highlights
  • Quotes/citations
  • Notes
  • Bookmarks
Notes
Cite this article

Cited article

Style
Citations are available only to our active members.
Sign up now to cite pages or passages in MLA, APA and Chicago citation styles.

(Einhorn, 1992, p. 25)

(Einhorn 25)

1

1. Lois J. Einhorn, Abraham Lincoln, the Orator: Penetrating the Lincoln Legend (Westport, CT: Greenwood Press, 1992), 25, http://www.questia.com/read/27419298.

Cited article

Database Design and Construction: Database Design - Definitions and Structure
Settings

Settings

Typeface
Text size Smaller Larger
Search within

Search within this article

Look up

Look up a word

  • Dictionary
  • Thesaurus
Please submit a word or phrase above.
Print this page

Print this page

Why can't I print more than one page at a time?

Full screen

matching results for page

Cited passage

Style
Citations are available only to our active members.
Sign up now to cite pages or passages in MLA, APA and Chicago citation styles.

"Portraying himself as an honest, ordinary person helped Lincoln identify with his audiences." (Einhorn, 1992, p. 25).

"Portraying himself as an honest, ordinary person helped Lincoln identify with his audiences." (Einhorn 25)

"Portraying himself as an honest, ordinary person helped Lincoln identify with his audiences."1

1. Lois J. Einhorn, Abraham Lincoln, the Orator: Penetrating the Lincoln Legend (Westport, CT: Greenwood Press, 1992), 25, http://www.questia.com/read/27419298.

Cited passage

Welcome to the new Questia Reader

The Questia Reader has been updated to provide you with an even better online reading experience.  It is now 100% Responsive, which means you can read our books and articles on any sized device you wish.  All of your favorite tools like notes, highlights, and citations are still here, but the way you select text has been updated to be easier to use, especially on touchscreen devices.  Here's how:

1. Click or tap the first word you want to select.
2. Click or tap the last word you want to select.

OK, got it!

Thanks for trying Questia!

Please continue trying out our research tools, but please note, full functionality is available only to our active members.

Your work will be lost once you leave this Web page.

For full access in an ad-free environment, sign up now for a FREE, 1-day trial.

Already a member? Log in now.