HKCAN 7XX Model

1
HKCAN 7XX Model

• A Goal achieved or mission impossible !

2
Outline

• 1. Hong Kongs quest for authority format to
  accommodate vernaculars and bilingual headings.
• 2. Traces MARBI discussion re content designation
  for alternative scripts, multilingual headings,
  transliteration, equiv. Headings etc.
• 3. Compare HKCAN records and the latest discussed
  formats in Discussion paper 2001-05
• 4. System design to support the new model
• 5. Q A

3
2 Major Quests on Authority record

• To accommodate CJK vernacular headings
• To accommodate additional heading(s) to meet the
  bilingual characteristics of the local community

4
Local development initiatives

• Jan 1998 Seminar on Chinese Information
  Processing In Libraries at HKUST
• Letter was sent to urge the de-facto world
  leaders
• Feb 1998 Lib-Chinese Listserv
• a lot of valuable discussions
• June 1998 Future of Authority Control for CJK
  Name headings Abraham Yu, UC, Irvine at
  ???????????????
• Jan 1999 - HKCAN Project
• Group effort

5
Format discussions

• Jun 16, 1997, DP100 Recording additional
  characteristics in USMARC Authority records
• May 1, 1998, DP108 Recording language of heading
  in USMARC Authority records
• May 6, 1998, DP109 Identifying transliteration
  schemes in USMARC formats
• May 1,1998, DP111 Alternate graphic without 880
  in Bibliographic, Holdings, Authority, and
  Community Information records
• Oct 1999 MARC21 format for Authority Data
• July 2000 - Adoption of 7xx model (recommended
  by Barbara Tillett)
• Jun 8, 2001, DP2001-05 Multilingual Authority
  Records in the MARC 21 Authority Format

6
DP100

• Discuss the characteristics under 2 models
• Model A Single record
• Model B Multiple records
• Language of catalog 040 b
• Language of heading 7
• Script 6ltScript codegt
• Linking field 8
• Transliteration 6lttransliteration schemegt
• Making 880 obsolete

7
Format Discussion - Language

• Language of catalog ltImplementedgt
• Model A Single record
• Each record is constructed around one heading for
  an entity and that heading is appropriate for a
  catalog in the lang. designated at 040b.
• All parallel forms of the 1xx headings in other
  languages are treated as variant and traced in
  4xx.
• Model B Multiple records
• Each record is constructed ... is appropriate for
  a catalog in the language designated at 040b
• Existence of parallel record

8
Format Discussion - Language (DP100, 108)

• Language of heading (7)
• Model A Single record
• 040 beng
• 100 10aMarx, Karl,d1818-18837eng7ger
• 400 10aMarukusu,d1818-18837jpn
• 400 10aMarx, Carlos,d1818-18837spa
• 400 10aMarks, Karl,d1818-18837rus
• 400 10aMarks, Karol,d1818-18837pol
• 400 10aMarksas, Karolisd1818-18837lit
• 400 10aMac, Cacd1818-18837vie
• Model B Multiple records

9
Format discussion - Script (DP100, 109, 111)

• Script (6) linking field (8)
• 8 to link alternate graphic representations when
  needed
• 6 to indicate explicitly the script(s) in the
  field, if necessary.
• Model A (with or without 880)
• Without 880
• 066 alatinbextended latinccyrillic
• 100 1801\gaZemtsovskii, I. I.q(Izalii
  Iosifovich)
• 100 1801\g6/cyrillicaltname in Cyrillic
  with initialsgtq(ltqualifier in Cyrillicgt)
• 400 1802\gaZemtsovskii, Izalii
  Iosifovich
• 400 1aZemtsovskiy, I.
• 400 1802\g6/cyrillicaltname in Cyrillicgt
• An alternative would be to code the alternate
  graphic form of the
• 1XX as a 4XX

10
Format Discussion - Script

• Script (6) linking field (8)
• Model B (Multiple records)
• (with or without 880 need for 880s is limited)
• 066 alatinbextended latinccyrillic
• 100 1aZemtsovskii, I. I.q(Izalii
  Iosifovich)
• 400 1aZemtsovskii, Izalii Iosifovich
• 400 1aZemtsovskiy, I.
• 700 16/cyrillicaltname in Cyrillic with
• initialsgtq(ltqualifier in Cyrillicgt)
• 066 acyrillicbextended cyrillicclatin
• 100 1altname in Cyrillic with
  initialsgtq(ltqualifier in
• Cyrillicgt)
• 400 1altname in Cyrillicgt
• 700 16/latinaZemtsovskii, I. I.q(Izalii
  Iosifovich)

11
Format Discussion - Transliteration (DP 100, 109)

• Transliteration (6)
• 6ltlinking taggt-ltoccurrence numbergt/ltscript
  codegt/ltfieldorientation codegt/lttransliteration
  schemegt
• Model A Model B
• 040 beng
• 151 aMoscow (Russia)
• 451 aMoskva (Russia)6///lttranslit.
  scheme for Cyrillicgt
• 451 aMoscou (Russia)6///ltthanslit.
  scheme for Cyrillicgt
• 451 aMoskau (Russia)6///lttranslit.
  scheme for Cyrillicgt
• 451 aMoscova (Russia)6///lttranslit.
  scheme for Cyrillicgt
• 451 aMo-ssu-k'o (Russia)6///lttranslit.
  scheme for
• Cyrillicgt

12
Format Discussions

• Summary of DP100
• Use subfield 6
• linking tag, script code, transliteration code
• Use subfield 7
• language of heading at the field level
• Use subfield 8
• linking alternative script in directly tagged
  fields
• Make 880 obsolete

DP2001-05
13
Format Discussions

• Discussion Paper 2001-DP05
• Date June 8, 2001
• Name Multilingual Authority Records in the
  MARC21 Authority Format
• Questions
• Can the authrity record support multilingual and
  multiscripts functions with respect to both
  record management and display?
• Can the format support multilingual and
  multiscript OPAC displays more effectively?
• Are adjustments needed for the bibliographic
  forma, or any of the other MARC 21 formats?

14
Task identified

• Propose changes to MARC21 coding structure that
  would support the identification of equivalent
  headings in multiple languages and/or scripts,
  and would provide for the syndetic structure
  needed to support those equivalent headings.
• The proposed solution should be generalizable and
  extensible, to accommodate a variety of data
  models, if possible.

15
General conclusions

• Identification at the field level of the lang. of
  a heading by itself is not generally useful,
• Identification at the field level of the script
  of a heading does not appear to be necessary
  with UNICODE implementation, scripts can be
  identified programmatically
• The rules by which a heading is formulated,
  usually expressed by identification of
  cataloguing codes or thesauri, need to be
  identified at the appropriate levels.
• Coding may be appropriate for different aspects
  of a heading, including an identification of what
  it is and its intended purposes.

16

• 3 Models

17
Model A - Single record

• Model A One authority record is constructed for
  each entity. Different forms of the 1xx heading
  (in other languages, scripts, etc.) are treated
  as variant reference
• Example

18
Model A - single record

• (1) 040 a XXX b eng c XXX
• (2) 100 0 a Cleopatra, c Queen of Egypt, d d.
  30 B.C.
• Form used in the Library of Congress
  catalog
• (3) 400 0 a Cleopatre, c Queen of Egypt, d d.
  30 B.C.
• (4) 400 0 a Kilyubatra, c Queen of Egypt, d
  d. 30 B.C.
• (5) 400 0 a Kleopatra, c Queen of Egypt, d d.
  30 B.C.
• (6 400 0 a Kliyubatra, c Queen of Egypt, d
  d. 30 B.C.
• (7) 400 0 a Cleopatre b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.) ? fre
• Form used in the Bibliotheque Nationale de
  France catalog
• (8) 400 0 a Cleopatra b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.)
• (9) 400 0 a Kleopatra b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.)
• (10) 400 0 a ltarabic form of name romanized
  according to French conventiongt b VII
• c (reine d'Egypte d 0069-0030 av. J.-C.)
  
• (11) 400 0 a Kleopatra, c Agypten, Konigin, b
  VII d av69-v30 ? ger
• Form used in the Deutsche Bibliothek
  catalog
• (12) 400 0 a Cleopatra, c Agypten, Konigin, b
  VII
• (13) 400 0 a Kleopatra, c die Grosse
• (14) 400 0 a ltarabic name romanized according
  to German conventiongt, c Agypten, Konigin,
• b VII

19
Model B - Multiple records

• Model B An authority record is constructed for
  each separate established heading for an entity.
  The heading in the 1xx field is appropriate for a
  catalog in the language designated at the record
  level by the code in subfield b of the 040
  field. The 4xx and 5xx traced headings
  constitute the reference structure for the 1xx
  heading
• Example

20
Model B - Multiple records

• 001 ea55555
• 040 a XXX b eng c XXX
• 100 0 a Cleopatra, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Cleopatre, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Kilyubatra, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Kleopatra, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Kliyubatra, c Queen of Egypt, d d. 30
  B.C.
• 700 04 a Cleopatre b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.) ? fre 0 fa44444
• 700 04 a Kleopatra, c Agypten, Konigin, b VII
  d av69-v30 ? ger
• 700 04 a ltHeading for Cleopatra for an Arabic
  catalog, formulated according to appropriate
  conventiongt ? ara 0 aa66666
• 700 06 a Cleopatre b VII, c reine d'Egypte, d
  m. 30 av. J.-C. ? fre 0 cfa77777
• 001 fa44444
• 040 a XXX b fre c XXX
• 100 0 a Cleopatre b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.)
• 400 0 a Cleopatra b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.)
• 400 0 a Kleopatra b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.)
• 400 0 a ltArabic name romanized according to
  French conventiongt b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.)
• 700 04 a Cleopatra, c Queen of Egypt, d d. 30
  B.C. ? eng 0 ea55555
• 700 04 a Kleopatra, c Agypten, Konigin, b VII
  d av69-v30 ? ger 0 ga33333

Prologue for global sharing?
21
Model C (Recommended)

• Model C is the linked record model presented of
  Model B, but rather than defining the established
  headings and equivalent established headings
  solely in terms of the language of the catalog,
  they are defined by a catalog context. The
  context of a catalog is a composite entity.

22
Attributes of Model C

• 1. The context of a catalog is a composite
  entity
• primary component rules
• language of catalog or audience
• 2. The 4xx and 5xx reference tracings in the
  record are appropriate to the 1xx heading in that
  contexts
• 3. Alternative headings would be recorded in the
  7xx fields in the authority record, with context
  marker
• NOTE Separate records for alternative headings
  are not required ...

23

• Example of Model C record
• 001 ea55555
• 008/10 (Cataloging rules) c (AACR2)
• 008/11 (Subject system/thesaurus rules) a (LCSH)
• 040 b (Language of cataloging) eng (English)
• 100 0 a Cleopatra, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Cleopatre, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Kilyubatra, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Kleopatra, c Queen of Egypt, d d. 30
  B.C.
• 400 0 a Kliyubatra, c Queen of Egypt, d d. 30
  B.C.
• 700 04 a Cleopatre b VII c (reine d'Egypte
  d 0069-0030 av. J.-C.)
• ? ltcontextgt 0 fa44444
• 700 04 a Kleopatra, c Agypten, Konigin, b VII
  d av69-v30 ? ltcontextgt
• 0 ga33333
• 700 04 a ltHeading for Cleopatra in Arabic,
  formulated according to appropriate
• conventiongt ? ltcontextgt 0 aa66666
• 700 06 a Cleopatre b VII c reine d'Egypte, d
  30 av. J.-C. ? ltcontextgt

?
?
24
Model C - context marker

• Context Marker 7
• ltrulescataloging code or thesaurus
  designationgt / ltaudiencegt / ltlanguage of cataloggt
  
• e.g. 7aacr//chi 7aacr//spa 7rak
• Example

25
Example 1 - Multilingual name headings (no linked
records illustrated) 008/10 (Cataloging rules)
c (AACR2) 008/11 (Subject system/thesaurus
rules) a (LCSH) 040 b (Language of
cataloging) eng (English) 100 0 a John Paul b
II, c Pope, d 1920- 400 0 a Joannes Paulus b
II, c Pope, d 1920- 400 0 a Juan Pablo b II,
c Pope, d 1920- 400 0 a Jean Paul b II, c
Pope, d 1920- 400 0 a Johannes Paul b II, c
Pope, d 1920- 400 0 a Joann Pavel b II, c
Pope, d 1920- ltetc.gt 510 2 a Catholic Church.
b Pope (1978- John Paul II) 700 04 a Juan
Pablo b II, c Papa, d 1920- 7 aacr//spa 700
06 a Jean Paul b II c pape, d 1920- 7
aacr//fre 700 04 a Jean Paul b II c (Pape), d
1920- 7 ncafnor 700 04 a Johannes Paul c
Papst, b II 7 rak 700 04 a ltChinese heading
for John Paulgt b II c ltChinese designation for
Popegt d 1920- 7 aacr//chi
700 _4source not specified
26
Advantages

• Because the notion of contextmay be adjusted
  to suit various situations, Model C is extensible
  and flexible.
• It supports any reference structures required by
  the cataloguing or thesaurus rules used
• It supports simple identification of alternative
  headings for display, in addition to linking to
  alternative authority records with their full
  reference structures.
• Context markers would be optional or records that
  apply only to a single context, or when the
  context functionality is not needed for record
  management or displays.

"How are about HKCAN records?
27
08941020nc acannaabn a aaa 010 anr
94034993 035 a(DLC)nr 94034993a 040
aDLC-RbengcDLC-RdOCoLCdHkCUdHkCAN 066
c1 100 1 aZhou, Ying,d17th cent. 400 1
wnneaChou, Ying,d17th cent. 400 1 aZhou,
Fangshu,d17th cent. 400 1 a???,d17th cent. 400
1 aChou, Fang-shu,d17th cent. 670 aChih lin
(??), 1992bt.p. (Chou Ying) 670 aChung wen ta
tz176u tien (?????)bv. 6, p. 290 (Chou Ying
of Ming native of P176u-t176ien t.
Fang-shu author of Chih lin lived around the
mid of Emperor Ch176ung-chen reign) 670 aHis
?? 10?, ???1?, 1963bt.p. (??) 670
a???????, 1934bp. 545 (??, ????, ???,
??????? ???, ????, ????) 700 1 a??,d17th cent.
7aacr//chi
Subfield 7 context marker
2nd indicator 4 or 7
28
Another example
100 1 a??,d17th cent. 400 1 wnneaChou,
Ying,d17th cent. 400 1 aZhou, Fangshu,d17th
cent. 400 1 a???,d17th cent. 400 1 aChou,
Fang-shu,d17th cent. 670 aChih lin (??),
1992bt.p. (Chou Ying) 670 aChung wen ta
tz176u tien (?????)bv. 6, p. 290 (Chou Ying
of Ming native of P176u-t176ien t.
Fang-shu author of Chih lin lived around the
mid of Emperor Ch176ung-chen reign) 670 aHis
?? 10?, ???1?, 1963bt.p. (??) 670
a???????, 1934bp. 545 (??, ????, ???,
??????? ???, ????, ????) 700 1 aZhou,
Ying,d17th cent.
Allow swap of headings
29
040 aNICbengcNICdNICdOCoLCdHkCUdHkCAN 066
c1 100 1 aDong, Jianhua,d1937- 400 1
wnneaTung, Chien-hua,d1937- 400 1 aTung, C.
H.d1937- 400 1 aTung, Chee-Hwa,d1937- 510 1
aHong Kong (China).bChief Executive (1997-
Dong) 510 1 a??(??).b????(1997- ?) 670 aTung
Chien-hua p176ing chuan (?????), 1996bp. 12
(English name C.H. Tung) p. 111 (b. 1937 in
Shanghai) 670 aRadio broadcast, Dec. 11,
1996b(elected chief executive of the Hong Kong
Special Administrative Region of the People's
Republic of China) 670 aABC World News To-night,
Dec. 23, 1996bcaption (Tung Chee-Hwa) 700 1
a???,d1937-
30
040 aHkCUcHkCU 066 c1 110 1 aHong Kong
(China).bProvisional Legislative Council
Commission 410 2 aProvisional Legislative
Council Commission (Hong Kong, China) 410 2 aLin
shi li fa hui xing zheng guan li wei yuan hui
(Hong Kong, China) 410 2 a????????????(??,
??) 510 1 waaHong Kong.bLegislative Council
Commission 510 1 waa??.b?????????? 510 1
wbaHong Kong (China).Legislative Council
Commission 510 1 wba??(??).b?????????? 670
aIts ????, 1997-98bcover (????????? ??? The
Provisional Legislative Council Commission) 710
1 a??(??).b????????????
Parallel field needed? Linking needed? For
maintenance? For display?
31
INNOPAC System interface

• Working on it , improving , and ... in the
  right direction
• Your input is important!

32
OK ?
See also earlier
See also later
33

• Goal achieved?
• Yes or No

34
(No Transcript)
35
(No Transcript)
36
100 0 aBingxin,d1900- 400 0 aBing-xin,d1900-
400 0 wnneaPing-hsin,d1900- 400 1
wnnaaaHsieh, Wan-ying,d1902- 400 1 aXie,
Wanying,d1900- 400 1 a???,d1900- 400 1 aXie,
Bingxin,d1900- 400 1 a???,d1900- 400 0
aNanshi,d1900- 400 0 a??,d1900- 400 1 aXie,
Shuixin,d1900- 400 1 aWu Xie,
Wanying,d1900- 400 2 a????,d1900- 400 1
aHsieh, Wan-ying,d1900- 400 1 aHsieh,
Ping-hsin,d1900- 400 0 aNan-shih,d1900- 400 1
aHsieh, Shui-hsin,d1900- 400 1 aWu Hsieh,
Wan-ying,d1900- 400 0 aBing Xin,d1900- 700 0
a??,d1900-
37
(No Transcript)
38
?
39
There are still more to do ...

• Standardization of HKCAN records, more
  discussion on the HKCAN 7xx model
• More members to join and contribute
• Enhancement of HKCAN OPAC
• More testing on the OPAC linking. Is there other
  display options?
• How does INNOPAC support the authority control
  of 7xx when data maintenance is concerned?

40

• Thank you )
• Maria Lau (CUHK) Dec 11, 2001 HKIUG