Title: CORPORATE REFERENCES
1CORPORATE REFERENCES
2LCRI 26.1
110 2_ Electoral Reform Society
410 2_ ERS
Published by Electoral Reform Society
3110 1_ Guam. b Dept. of Youth Affairs
410 1_ Guam. b Dipattamenton Asunton
Manhoben
410 1_ Guam. b Youth Affairs, Dept. of
4110 2_ C.I. White, Inc.
LCRI 26.1 26.3A3
410 2_ White, Inc.
5110 1_ Hawaii. b Executive Office on Aging
LCRI 26.3A3
410 1_ Hawaii. b Office on Aging, Executive 410
1_ Hawaii. b Aging, Executive Office on
6LCRI 26.3A3
110 1_ Hawaii. b Dept. of Human
Resources Development
410 1_ Hawaii. b Human Resources
Development, Dept. of
7LCRI 26.3A7Government body entered
independentlyAlways provide reference under
jurisdiction
- 410 1_ United States. b National Institutes of
Health - 410 1_ Baltimore (Md.). b Redevelopment
Corporation
- 110 2_ National Institutes of Health (U.S.)
- 110 2_ Baltimore Redevelopment Corporation
8110 2_ Ombudsman Commission of Papua New Guinea
410 1_ Papua New Guinea. b Ombudsman
Commission
LCRI 26.3A7
9LCRI 26.3A7
110 2_ Centre for European Affairs (Institute of
International Relations)
410 2_ Institute of International Relations.
b Centre for European Affairs
If higher body Institute of International
Relations is not established, make an NAR for it
10LCRI 26. 3
Reference added from key word and immediate
parent body
110 1_ Wisconsin. b Bureau of Chronic Disease
Prevention and Health Promotion
410 1_ Wisconsin. b Chronic Disease Prevention
and Health Promotion, Bureau of
410 1_ Wisconsin. b Division of Public Health.
b Bureau of Chronic Disease Prevention and
Health Promotion
11CONFERENCE 4XX REFERENCES
12111 2_ International Conference on Database
Systems for Advanced Applications
411 2_ Conference on Database Systems for
Advanced Applications, International 411 2_
DASFAA
13LCRI 26.3A3
111 2_ IEEE International Conference on Network
Protocols d (2002 c Paris, France)
411 2_ International Conference on Network
Protocols, IEEE 411 2_ Conference on Network
Protocols, IEEE
International
14- Verso t.p.
- The Institute of Electrical and Electronic
Engineers International Conference on Network
Protocols
111 2_ IEEE International Conference on Network
Protocols d (2002 c Paris, France)
411 2_ Institute of Electrical and Electronic
Engineers International Conference on Network
Protocols d (2002 c Paris, France)
15CORPORATE 4XX REFERENCESTHINGS TO REMEMBER
16CORPORATE REFERENCES THINGS TO REMEMBER
- Justify in 670 field unless allowed by the rules
- All elements of hierarchy used in references must
also be established - References made through parent body must use
established form of the parent body
17CORPORATE REFERENCES THINGS TO REMEMBER
- Supply references through jurisdictions for
government headings ONLY (cf. LCRI 26.3A7) - Make inverted references ONLY for government
headings entered under jurisdiction (cf. LCRI
26.3A3)
18CORPORATE REFERENCES THINGS TO REMEMBER
- SEARCH all x-refs. to assure they do not conflict
with ESTABLISHED HEADINGS - Resolve conflicts between headings and references
by qualifying the reference (cf. LCRI 24.4C) - Remember references may conflict with each other
19CONFERENCE REFERENCES(4XX)THINGS TO REMEMBER
20CONFERENCE REFERENCES THINGS TO REMEMBER
- Inverted references are allowed only when the
heading begins with the name of the sponsor
and/or when the word for conference is not the
first element of the heading (LCRI 26.3A3) - References are NOT made from subject words in
conference names (LCRI 26.3A3)
21CONFERENCE REFERENCES THINGS TO REMEMBER
- References may include qualifiers if appropriate
- Example
- 111 2_ Tools 94 d (1994 c
Melbourne, Vic.) - 411 2_ Workshop on Technology of
Object-Oriented Language and Systems d
(1994 c Melbourne, Vic.)
22CONFERENCE REFERENCES THINGS TO REMEMBER
- Qualifiers are not included in inverted headings
(LCRI 26.3A3) - Example
- 111 2_ Microsoft Workshop on
Technology of Object- Oriented Language
and Systems d (1994 c
Melbourne, Vic.) - 411 2_ Workshop on Technology of
Object-Oriented Language and Systems,
Microsoft
23CONFERENCE REFERENCES THINGS TO REMEMBER
- Refer from the general form of the conference
name when using the specific name as the
established heading (AACR2 24.3F2) - Example 111 2_ Conference on Corn d
(1990 c El Paso, Tex.) - 411 2_ Conference on Agriculture n
(2nd d 1990 c El Paso,
Tex.)
24CORPORATE BODY SEE ALSO REFERENCES (5XX)
25UNUSED SUBDIVISIONS
LCRI 26.3
IF BODY IS NEEDED CREATE NAR, CHANGE 4XX TO
5XX, DELETE NAME FROM 667
26WHAT IF THE RELATIONSHIP IS UNCLEAR?
- IF EARLIER/LATER SITUATION IS NOT CLEAR
- 2 NARs IN DATABASE
- MAKE 5XX LINKING REFERENCES
- DO NOT INCLUDE SUBFIELD w IN THESE 5XX
REFERENCES
27(No Transcript)
28BODY CHANGED NAME
- CLEAR INDICATION FROM ITEM THAT BODY CHANGED ITS
NAME - MAKE 5XX REFERENCES AND INCLUDE CONTROL SUBFIELD
w - ADD 670 OR 675 TO JUSTIFY 5XX REFERENCES
LCRI 26.3B-C
29(No Transcript)
30- Verso t.p.
- Beginning April 1962 Mississippi Southern College
will be called University of Southern Mississippi
COVER
31EARLIER HEADING
5XX REF.
ADDED 670
LATER HEADING
5XX REF.
32NAR FOR EARLIER HEADING
675 ADDED TO JUSTIFY 510 REF.
LCRI 26.3B-C
33BODY A CHANGED TO B
BODY B CHANGED TO C
34BODY A BECAME BODY B BODY B BECAME BODY C BODY
C BECAME BODY D
35Body A make later see also reference to Body
B Body B make earlier see also reference to
Body A
Body B make later see also reference to Body
C Body C make earlier see also reference to
Body B
Body C make simple see also reference to Body
A Body A make simple see also reference to Body
C
Simple see also references needed between body
A C because A precedes C but also follows C
361
2
3
ABC BECAME D
4
37SEE ALSO REFERENCESTHINGS TO REMEMBER
- Each name that a corporate body has had is to be
represented in the NAF by a separate record for
each name - Use w to show special relationships
(earlier/later) value a (earlier) or value b
(later)
38SEE ALSO REFERENCES THINGS TO REMEMBER
- When the relationship of related headings is
unclear make a simple see also 5XX references (no
w) - When relationship of related headings is clear
make 5XX see also references coded with w - Connect only immediately preceding and succeeding
names
39SEE ALSO REFERENCES THINGS TO REMEMBER
- 5XX references must be justified in a 670 or 675
- Use 675 to cite other sources which justify only
5XX references and not 1XX - Be aware of NARs in file for older headings that
have earlier names of bodies in 667 field
40CANADIAN CORPORATE NAME HEADINGS
DCM Z1 (1XX Headings) Canadian Headings
41- CANADIAN CORPORATE NAME HEADINGS
- (Canadian Imprints)
- Use LAC-established form from
- Can. CIP data
- Headings on AACR2 LAC bibliographic records in
utility databases - LAC NARs and AACR2 bib. record headings in AMICUS
42CANADIAN CORPORATE NAME HEADINGS
- If found cite in 670 as
- 670 Title of work, date b t.p. (usage) Can.
CIP (data found) - 670 OCLC, Sept. 15, 2005 b (LAC hdg.____
usage_______ ) - 670 AMICUS, Aug. 29, 2005 b (LAC bib. hdg.
_____ usage _____) - 670 LAC database, Aug. 15, 2007 b (hdg.
______ variant _______)
43CANADIAN CORPORATE NAME HEADINGS
- If NOT found on a Can. CIP or on a LAC
- AACR2 bibliographic record
- Search AMICUS database
- http//amicus.nlc-bnc.ca/aaweb/aalogine.htm
44CANADIAN CORPORATE NAME HEADINGS
- If still not found
- Cataloger creates an NAR based on information
found in the resource and any other additional
reference sources contribute the record to OCLC
once reviewed by your reviewer - Send Web form request to LAC to verify the
heading - (Note the required areas of the form)
- http//www.loc.gov/catdir/pcc/naco/LAC-nacohdgform
.html - LAC will respond directly to the cataloger who
is requesting the verification - Adapt NAR hdg., if necessary, based on LAC
response adjust refs. punctuation as necessary
(i.e. add, modify, etc.)
45(No Transcript)
46CORPORATE NAME REFERENCES
- Trace see references found on LAC NARs or as
provided by LAC unless incompatible with other
existing entries - Trace see also references given by LAC
according to normal guidelines (cf. LCRI 26.3B-C) - Justification of these references is not
necessary. - If a subfield w is found on a LAC NAR analyze
the reference to determine if this subfield is
needed. Delete or adjust the subfield (or the
reference) if it does not follow LC/PCC
conventions.
47CORPORATE NAME REFERENCES
- When making connections between earlier and later
corporate names, LAC formerly used simple see
alsos (no subfield w coding used). -
- If using an older LAC record, and if information
is available, code the references earlier/later
per LC practice. - Additional references may be given if required,
justified according to normal practice.
48CANADIAN CONFERENCE NAMES
- Use judgment in considering meetings held in
Canada as Canadian -
- LAC establishes ongoing conferences with
qualifiers for each individual conference. Delete
these qualifiers and establish one authority
record for the series of conferences (cf. LCRI
24.7B)
49CAPITALIZATION/PUNCTUATION
- If the LAC form differs from the LC/PCC AACR2
practice for capitalization or punctuation,
accept the LAC form.
50Corporate Names Exceptions
- If LAC indicates that the name is not a corporate
body (e.g., a plan, a project) establish the
heading according to the usual LCC/PCC practice.
Record the LAC decision in a 670 field. - LC/NACO libraries do not have to contact LAC for
Canadian corporate bodies associated with the
Society of Friends (see DCM Z1 for more details).
51Corporate Names Exceptions
- LAC does not establish agency corporate headings
for Canadian parks, forests, etc. - LAC establishes headings for Canadian First
Nations as corporate bodies (110), not as
jurisdictions (151). Accept the LAC coding.
52CORPORATE HEADINGS FOR Québec
- See DCM Z1. If the French form of name is chosen
as the heading and it includes a qualifying term
in French, change the qualifying term to English
53CORPORATE BODIES