h engine crawled the Web.
The web site itself may have changed. You can check the current page or check for previous versions at the Internet Archive. Yahoo! is not affiliated with the authors of this page or responsible for its content.
THE LOGICAL STRUCTURE OF THE 7+( /2*,&$/ 6758&785( 2) 7+(
$1*/2$0(5,&$1 &$7$/2*8,1* 58/(6 � 3$57 ,
'UDIWHG IRU
7KH -RLQW 6WHHULQJ &RPPLWWHH IRU 5HYLVLRQ RI $$&5
E\
7RP 'HOVH\
1DWLRQDO /LEUDU\ RI &DQDGD
ZLWK DVVLVWDQFH IURP
%HWK 'XODEDKQ /LEUDU\ RI &RQJUHVV
0LFKDHO +HDQH\ 2[IRUG 8QLYHUVLW\
-HDQ +LURQV /LEUDU\ RI &RQJUHVV
$XJXVW  &217(176
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
3$*(
OBJECTIVE
1
METHODOLOGY
1
OVERVIEW OF THE MODEL
4
KEY ISSUES
25
(17,7<  $775,%87(  '$7$ (/(0(17 '(6&5,37,216
7$%
ITEM
1
SERIES
2
SUBSERIES
3
CLASS OF MATERIALS
4
TYPE OF PUBLICATION
5
CHIEF SOURCE OF INFORMATION
6
DOCUMENT
7
DOCUMENT PART
8
CONTENT
9
CONTENT PART
10
INFIXION
11
PHYSICAL CARRIER
12
CONTAINER
13
PERSON
14
CORPORATE BODY
15
PRODUCTION
16
CREATION
17
OWNERSHIP
18
EQUIPMENT
19
MANUFACTURE
20
RELEASE
21
COPY
22
IMPRESSION
23
ISSUE
24
EDITION
25
COLLECTION
26
5(/$7,216+,3  '$7$ (/(0(17 '(6&5,37,216
7$%
ITEM
�
ITEM
27
SERIES
�
SUBSERIES
28
SERIES
�
ITEM
29
SUBSERIES
�
ITEM
30
DOCUMENT
�
DOCUMENT PART
31
CONTENT
�
CONTENT
32
CONTENT
�
CONTENT PART
33
PERSON / CORPORATE BODY
�
PRODUCTION
34
PERSON / CORPORATE BODY
�
CREATION
35
PERSON / CORPORATE BODY
�
OWNERSHIP
36 7+( /2*,&$/ 6758&785( 2) 7+(
$1*/2$0(5,&$1 &$7$/2*8,1* 58/(6 � 3$57 ,
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
2%-(&7,9(
The principal objective of this study is to develop a formalized schema to reflect the
internal logic of the
$QJOR$PHULFDQ &DWDORJXLQJ 5XOHV
.
The schema is intended to serve as a tool to assist in the re-examination of the
principles underlying the code and in setting directions for its future development.
The presentation of the analytic model is designed specifically to:
�
assist in clarifying the concepts that are integral to the logical design of the code;
�
highlight anomalies within the rules and inconsistencies in the application of
basic principles;
�
provide a clearly defined frame of reference to be used in determining how to
develop and extend the code to reflect new media used as information carriers,
new forms of publication, and new modes of dissemination and access.
0(7+2'2/2*<
The methodology used in this study is derived from techniques used in systems
development projects to create entity-relationship models or object-oriented models. As
analytic tools, entity-relationship and object-oriented models are used as the basis for
identifying the key entities or objects about which an organization needs to keep data
and clarifying the data-related business rules that apply within the organization prior to
designing the layout of databases to support the organizations business activities.
The modeling technique as applied in this study focuses on the cataloguing process as
the activity to be analyzed, and the code itself as the set of business rules that govern
that activity. The model is not designed to reflect in the abstract the information
universe or the universe of recorded knowledge. It is designed to represent in specific
terms how that universe is reflected in the logic of the cataloguing code
SHU VH
.
This first segment of the study has taken as its starting point a detailed analysis of the
data elements in Part I of the code. Each data element in the descriptive record has
been mapped either to an attribute of a particular entity or object or to a relationship
between particular entities or objects. Because it is intended to serve as a schema
mirroring the
LQWHUQDO
logic of the code, the model reflects only what is made explicit
through the rules as currently set out in the code, and only what is recorded in the
descriptive record as a result of applying those rules. Other entities or objects, other
attributes, and other relationships that might be inferred from an analysis of phenomena
H[WHUQDO
to the code itself have not been reflected in the model. 2
7HUPLQRORJ\  GHILQLWLRQV
As far as possible the terms used in the model to identify entities or objects, their
attributes, and their relationships have been derived directly from the code itself.
The definitions for the terms used to identify entities, etc. have also been derived, to the
extent possible, either from the glossary or from the wording of the rules themselves, in
some cases in a modified form. Where definitions could not be derived from the code
itself, they have been derived from other sources such as the
$/$ JORVVDU\ RI OLEUDU\
DQG LQIRUPDWLRQ VFLHQFH
, the
)XQFWLRQDO UHTXLUHPHQWV IRU ELEOLRJUDSKLF UHFRUGV
, and
technical dictionaries. In other instances definitions have been developed specifically
for the purposes of the model.
Specifications as to what is included within the scope of a particular entity, attribute, or
relationship, or excluded from it, have been derived, wherever possible, directly from the
rules themselves.
(QWLWLHV  UHODWLRQVKLSV
The entities or objects defined in the model represent the key agents, processes,
objects, and concepts around which the code operates; they are in effect the primary
points of reference or coordinates for mapping the logic of the code.
Similarly the relationships defined in the model represent the key associations between
entities or objects reflected in the code; they are in effect the logical connectors between
the key entities or objects.
$WWULEXWHV  GDWD HOHPHQWV
The attributes associated with each entity or object in the model have been defined at a
logical level, i.e., as characteristics of the entity or object as they would be defined with
reference to the entity or object itself, not as specific data elements defined with
reference to the bibliographic record. For example, title is defined as an attribute of
the entity or object document in such a way as to encompass all the names by which
the document may be identified.
Each logical attribute is in turn linked to the specific data elements that fall within its
defined scope (e.g., title as a logical attribute is linked to the data elements title
proper, parallel title, variant title, romanized title, and key-title). In many
instances, however, the logical attribute is linked to only one data element.
If the rules permit the recording of a data element in more than one area of the
description the reference to the rules for that data element will indicate those
distinctions. For example, the references under the data element parallel title to the
rules pertaining to that data element distinguish between those that give instructions for
recording a parallel title in the title and statement of responsibility area and those that
give instructions for noting a parallel title in the note area. In such cases the data
element is treated as a single data element irrespective of its placement within the
record. 3
*HQHUDO UXOHV  VSHFLILF UXOHV
The data elements associated with each logical attribute are linked to the rules in the
code that pertain to that data element.
The rules relating to each data element are identified under two categories: general
rules that are applicable across all classes of material and types of publication; and
specific rules that apply only to specific classes of material and types of publication.
Apparent anomalies in the rules have been noted in the detailed analysis that is
provided for each data element.
'LDJUDPPLQJ
The conventions used for diagramming the logic of the code are as follows:
A rectangle with rounded corners represents a
bibliographic entity (i.e., an abstract concept
used in the code as a point of reference or as a
structuring device for the rules).
A rectangle with right-angled corners represents
a real world entity (i.e., an agent, process, or
object) the characteristics of which are reflected
in the descriptive record.
A single-headed arrow on a line represents a
relationship in which any given instance of the
entity at the opposite end of the line may be
associated with only one instance of the entity to
which the arrow is pointing.
A double-headed arrow on a line represents a
relationship in which any given instance of the
entity at the opposite end of the line may be
associated with one or more instances of the
entity to which the arrows are pointing.
A zero on a line indicates that the relationship
between any given instance of the entity at the
opposite end of the line and the entity to which
the arrow is pointing is optional (i.e., the
relationship may not be operative in all
instances).
0
0 4
29(59,(: 2) 7+( 02'(/
An overview of the model developed for this study is presented in a series of entity-
relationship diagrams (Figures 1-10), accompanied by a summary explanation of the
entities and relationships depicted in each of the diagrams. The first diagram (Figure 1)
sets out the bibliographic entities that are used to give Part I of the code its structure
(i.e., the abstract concepts used