HKCAN 7XX ModelHKCAN 7XX Model

A Goal achieved or mission A Goal achieved or mission impossible !impossible !

OutlineOutline

1. Hong Kong’s quest for authority format to 1. Hong Kong’s quest for authority format to accommodate vernaculars and bilingual headings.accommodate vernaculars and bilingual headings.

2. Traces MARBI discussion re content designation for 2. Traces MARBI discussion re content designation for alternative scripts, multilingual headings, transliteration, alternative scripts, multilingual headings, transliteration, equiv. Headings etc.equiv. Headings etc.

3. Compare HKCAN records and the latest discussed 3. Compare HKCAN records and the latest discussed formats in Discussion paper 2001-05formats in Discussion paper 2001-05

4. System design to support the new model4. System design to support the new model 5. Q & A 5. Q & A

2 Major Quests on Authority record2 Major Quests on Authority record

To accommodate CJK vernacular headingsTo accommodate CJK vernacular headings To accommodate additional heading(s) to To accommodate additional heading(s) to

meet the bilingual characteristics of the meet the bilingual characteristics of the local community local community

Local development & initiativesLocal development & initiatives

Jan 1998 Seminar on Chinese Information Jan 1998 Seminar on Chinese Information Processing In Libraries at HKUSTProcessing In Libraries at HKUST– Letter was sent to urge the de-facto world leadersLetter was sent to urge the de-facto world leaders

Feb 1998 Lib-Chinese ListservFeb 1998 Lib-Chinese Listserv– a lot of valuable discussionsa lot of valuable discussions

June 1998 Future of Authority Control for CJK June 1998 Future of Authority Control for CJK Name headings” Abraham Yu, UC, Irvine at Name headings” Abraham Yu, UC, Irvine at 海峽海峽兩岸圖書館與資訊服務研討會兩岸圖書館與資訊服務研討會

Jan 1999 - HKCAN ProjectJan 1999 - HKCAN Project– Group effort Group effort

Format discussionsFormat discussions Jun 16, 1997, DP100Jun 16, 1997, DP100 Recording additional characteristics in Recording additional characteristics in

USMARC Authority recordsUSMARC Authority records May 1, 1998, DP108May 1, 1998, DP108 Recording language of heading in USMARC Recording language of heading in USMARC

Authority recordsAuthority records May 6, 1998, DP109May 6, 1998, DP109 Identifying transliteration schemes in Identifying transliteration schemes in

USMARC formatsUSMARC formats May 1,1998, DP111May 1,1998, DP111 Alternate graphic without 880 in Bibliographic, Alternate graphic without 880 in Bibliographic,

Holdings, Authority, and Community Information records Holdings, Authority, and Community Information records Oct 1999Oct 1999 MARC21 format for Authority DataMARC21 format for Authority Data

* July 2000 - Adoption of 7xx model (recommended by Barbara Tillett)

Jun 8, 2001, DP2001-05Jun 8, 2001, DP2001-05 Multilingual Authority Records in the Multilingual Authority Records in the MARC 21 Authority FormatMARC 21 Authority Format

DP100DP100

Discuss the characteristics under 2 models:Discuss the characteristics under 2 models:

Model A Single recordModel A Single record

Model B Multiple recordsModel B Multiple records Language of catalog 040 $bLanguage of catalog 040 $b Language of heading $7Language of heading $7 Script $6<Script code>Script $6<Script code> Linking field $8Linking field $8 Transliteration $6<transliteration scheme>Transliteration $6<transliteration scheme> Making 880 obsoleteMaking 880 obsolete

Format Discussion - LanguageFormat Discussion - Language

Language of catalog <Implemented>Language of catalog <Implemented>– Model A Single recordModel A Single record

» Each record is constructed around one heading for an Each record is constructed around one heading for an entity and that heading is appropriate for a catalog in the entity and that heading is appropriate for a catalog in the lang. designated at 040$b. lang. designated at 040$b.

» All parallel forms of the 1xx headings in other All parallel forms of the 1xx headings in other languages are treated as variant and traced in 4xx.languages are treated as variant and traced in 4xx.

– Model B Multiple recordsModel B Multiple records» Each record is constructed ... is appropriate for a catalog Each record is constructed ... is appropriate for a catalog

in the language designated at 040$bin the language designated at 040$b» Existence of parallel recordExistence of parallel record

Format Discussion - Language Format Discussion - Language (DP:100, (DP:100, 108))

Language of heading ($7)Language of heading ($7)– Model A Single recordModel A Single record 040 $beng040 $beng

100 10$aMarx, Karl,$d1818-1883$7eng$7ger100 10$aMarx, Karl,$d1818-1883$7eng$7ger

400 10$aMarukusu,$d1818-1883$7jpn400 10$aMarukusu,$d1818-1883$7jpn

400 10$aMarx, Carlos,$d1818-1883$7spa400 10$aMarx, Carlos,$d1818-1883$7spa

400 10$aMarks, Karl,$d1818-1883$7rus400 10$aMarks, Karl,$d1818-1883$7rus

400 10$aMarks, Karol,$d1818-1883$7pol400 10$aMarks, Karol,$d1818-1883$7pol

400 10$aMarksas, Karolis$d1818-1883$7lit400 10$aMarksas, Karolis$d1818-1883$7lit

400 10$aMac, Cac$d1818-1883$7vie400 10$aMac, Cac$d1818-1883$7vie

– Model B Multiple recordsModel B Multiple records

Format discussion - Script Format discussion - Script (DP:100, 109, 111)(DP:100, 109, 111)

Script ($6) linking field ($8)Script ($6) linking field ($8) $8 to link alternate graphic representations when needed$8 to link alternate graphic representations when needed $6 to indicate explicitly the script(s) in the field, if necessary.$6 to indicate explicitly the script(s) in the field, if necessary.

– Model A (with or without 880)Model A (with or without 880)» Without 880Without 880

066 $alatin$bextended latin$ccyrillic066 $alatin$bextended latin$ccyrillic

100 1#$801\g$aZemtsovskii, I. I.$q(Izalii Iosifovich)100 1#$801\g$aZemtsovskii, I. I.$q(Izalii Iosifovich)

100 1#$801\g$6/cyrillic$a<name in Cyrillic with initials>$q(<qualifier in Cyrillic>)100 1#$801\g$6/cyrillic$a<name in Cyrillic with initials>$q(<qualifier in Cyrillic>)

400 1#$802\g$aZemtsovskii, Izalii Iosifovich400 1#$802\g$aZemtsovskii, Izalii Iosifovich

400 1#$aZemtsovskiy, I.400 1#$aZemtsovskiy, I.

400 1#$802\g$6/cyrillic$a<name in Cyrillic>400 1#$802\g$6/cyrillic$a<name in Cyrillic>

An alternative would be to code the alternate graphic form of theAn alternative would be to code the alternate graphic form of the

1XX as a 4XX:1XX as a 4XX:

Format Discussion - ScriptFormat Discussion - Script Script ($6) linking field ($8)Script ($6) linking field ($8)

– Model B (Multiple records)Model B (Multiple records)– (with or without 880; need for 880s is limited)(with or without 880; need for 880s is limited)

066 $alatin$bextended latin$ccyrillic066 $alatin$bextended latin$ccyrillic

100 1#$aZemtsovskii, I. I.$q(Izalii Iosifovich)100 1#$aZemtsovskii, I. I.$q(Izalii Iosifovich) 400 1#$aZemtsovskii, Izalii Iosifovich400 1#$aZemtsovskii, Izalii Iosifovich 400 1#$aZemtsovskiy, I.400 1#$aZemtsovskiy, I. 700 1#$6/cyrillic$a<name in Cyrillic with700 1#$6/cyrillic$a<name in Cyrillic with initials>$q(<qualifier in Cyrillic>)initials>$q(<qualifier in Cyrillic>)

066 $acyrillic$bextended cyrillic$clatin066 $acyrillic$bextended cyrillic$clatin 100 1#$a<name in Cyrillic with initials>$q(<qualifier in100 1#$a<name in Cyrillic with initials>$q(<qualifier in Cyrillic>)Cyrillic>) 400 1#$a<name in Cyrillic>400 1#$a<name in Cyrillic> 700 1#$6/latin$aZemtsovskii, I. I.$q(Izalii Iosifovich)700 1#$6/latin$aZemtsovskii, I. I.$q(Izalii Iosifovich)

Format DiscussionFormat Discussion - - Transliteration Transliteration (DP: 100, 109)(DP: 100, 109)

Transliteration ($6)Transliteration ($6) $6<linking tag>-<occurrence number>/<script code>/<fieldorientation $6<linking tag>-<occurrence number>/<script code>/<fieldorientation

code>/<transliteration scheme>code>/<transliteration scheme> Model A & Model BModel A & Model B 040 $beng040 $beng 151 ##$aMoscow (Russia)151 ##$aMoscow (Russia) 451 ##$aMoskva (Russia)$6///<translit. scheme for Cyrillic>451 ##$aMoskva (Russia)$6///<translit. scheme for Cyrillic> 451 ##$aMoscou (Russia)$6///<thanslit. scheme for Cyrillic>451 ##$aMoscou (Russia)$6///<thanslit. scheme for Cyrillic> 451 ##$aMoskau (Russia)$6///<translit. scheme for Cyrillic>451 ##$aMoskau (Russia)$6///<translit. scheme for Cyrillic> 451 ##$aMoscova (Russia)$6///<translit. scheme for Cyrillic>451 ##$aMoscova (Russia)$6///<translit. scheme for Cyrillic> 451 ##$aMo-ssu-k'o (Russia)$6///<translit. scheme for451 ##$aMo-ssu-k'o (Russia)$6///<translit. scheme for Cyrillic>Cyrillic>

Format DiscussionsFormat Discussions

Summary of DP100 Summary of DP100 – Use subfield 6 Use subfield 6

» linking tag, script code, transliteration codelinking tag, script code, transliteration code

– Use subfield 7 Use subfield 7 » language of heading at the field levellanguage of heading at the field level

– Use subfield 8Use subfield 8» linking alternative script in directly tagged fieldslinking alternative script in directly tagged fields

– Make 880 obsoleteMake 880 obsolete

DP2001-05

Format DiscussionsFormat Discussions

Discussion Paper 2001-DP05Discussion Paper 2001-DP05 Date : June 8, 2001Date : June 8, 2001 Name : Multilingual Authority Records in the MARC21 Authority Name : Multilingual Authority Records in the MARC21 Authority

FormatFormat Questions:Questions:

– Can the authrity record support multilingual and multiscripts Can the authrity record support multilingual and multiscripts functions with respect to both record management and functions with respect to both record management and display?display?

– Can the format support multilingual and multiscript OPAC Can the format support multilingual and multiscript OPAC displays more effectively?displays more effectively?

– Are adjustments needed for the bibliographic forma, or any of Are adjustments needed for the bibliographic forma, or any of the other MARC 21 formats?the other MARC 21 formats?

Task identifiedTask identified

Propose changes to MARC21 coding structure that Propose changes to MARC21 coding structure that would support the identification of equivalent would support the identification of equivalent headings in multiple languages and/or scripts, and headings in multiple languages and/or scripts, and would provide for the syndetic structure needed to would provide for the syndetic structure needed to support those equivalent headings. …support those equivalent headings. …

The proposed solution should be generalizable and The proposed solution should be generalizable and extensible, to accommodate a variety of data extensible, to accommodate a variety of data models, if possible.models, if possible.

General conclusionsGeneral conclusions

Identification at the field level of the lang. of a heading by itself is not Identification at the field level of the lang. of a heading by itself is not generally useful,generally useful,

Identification at the field level of the script of a heading does not Identification at the field level of the script of a heading does not appear to be necessary; with UNICODE implementation, scripts can appear to be necessary; with UNICODE implementation, scripts can be identified programmaticallybe identified programmatically

The rules by which a heading is formulated, usually expressed by The rules by which a heading is formulated, usually expressed by identification of cataloguing codes or thesauri, need to be identified at identification of cataloguing codes or thesauri, need to be identified at the appropriate levels.the appropriate levels.

Coding may be appropriate for different aspects of a heading, Coding may be appropriate for different aspects of a heading, including an identification of what it is and its intended purposes.including an identification of what it is and its intended purposes.

3 3 ModelsModels

Model A - Single recordModel A - Single record

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

ExampleExample

Model A - single record Model A - single record (1) 040 $a XXX $b eng $c XXX (1) 040 $a XXX $b eng $c XXX

(2) 100 0# $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. (2) 100 0# $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C.

[Form used in the Library of Congress catalog] [Form used in the Library of Congress catalog]

(3) 400 0# $a Cleopatre, $c Queen of Egypt, $d d. 30 B.C. (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.(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. (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. (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 (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] [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.) (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.) (9) 400 0# $a Kleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)

(10) 400 0# $a <arabic form of name romanized according to French convention> $b VII (10) 400 0# $a <arabic form of name romanized according to French convention> $b VII

$c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)

(11) 400 0# $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger (11) 400 0# $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger

[Form used in the Deutsche Bibliothek catalog] [Form used in the Deutsche Bibliothek catalog]

(12) 400 0# $a Cleopatra, $c Agypten, Konigin, $b VII (12) 400 0# $a Cleopatra, $c Agypten, Konigin, $b VII

(13) 400 0# $a Kleopatra, $c die Grosse (13) 400 0# $a Kleopatra, $c die Grosse

(14) 400 0# $a <arabic name romanized according to German convention>, $c Agypten, Konigin, (14) 400 0# $a <arabic name romanized according to German convention>, $c Agypten, Konigin,

$b VII $b VII

(15) 400 0# $a <name in Arabic script>, $c Agypten, Konigin, $b VII (15) 400 0# $a <name in Arabic script>, $c Agypten, Konigin, $b VII

(16) 400 0# $a <heading for Cleopatra in an Arabic catalog, formulated according to (16) 400 0# $a <heading for Cleopatra in an Arabic catalog, formulated according to

appropriate convention> $? araappropriate convention> $? ara

[Form used in an Arabic language catalog] [Form used in an Arabic language catalog]

(17) 400 0# $a <reference tracing(s) for heading in Arabic>(17) 400 0# $a <reference tracing(s) for heading in Arabic>

(18) (18) 400 0# $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre 400 0# $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre

[Form used in the National Library of Canada French language catalog][Form used in the National Library of Canada French language catalog]

Model B - Multiple recordsModel B - Multiple records

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

ExampleExample

Model B - Multiple recordsModel B - Multiple records001 ea55555001 ea55555

040 ## $a XXX $b eng $c XXX040 ## $a XXX $b eng $c XXX

100 0# $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C.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 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 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 Kleopatra, $c Queen of Egypt, $d d. 30 B.C.

400 0# $a Kliyubatra, $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 fa44444700 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 $? ger700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger

700 04 $a <Heading for Cleopatra for an Arabic catalog, formulated according to appropriate convention> $? ara 700 04 $a <Heading for Cleopatra for an Arabic catalog, formulated according to appropriate convention> $? ara $0 aa66666$0 aa66666

700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre $0 cfa77777700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre $0 cfa77777

001 fa44444001 fa44444

040 $a XXX $b fre $c XXX040 $a XXX $b fre $c XXX

100 0# $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)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 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 Kleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)

400 0# $a <Arabic name romanized according to French convention> $b VII $c (reine d'Egypte ; $d 0069-0030 av. 400 0# $a <Arabic name romanized according to French convention> $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)J.-C.)

700 04 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? eng $0 ea55555700 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 ga33333700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger $0 ga33333

700 04 $a <Heading for Cleopatra for an Arabic catalog, formulated according to 700 04 $a <Heading for Cleopatra for an Arabic catalog, formulated according to

appropriate convention> $? ara $0 aa66666appropriate convention> $? ara $0 aa66666

700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre $0 cfa77777700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre $0 cfa77777

Prologue for global sharing?Prologue for global sharing?

Model CModel C (Recommended)(Recommended)

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

Attributes of Model CAttributes of Model C

1. The context of a catalog is a composite entity1. The context of a catalog is a composite entity

– primary component: rulesprimary component: rules

– language of catalog; or audiencelanguage of catalog; or audience 2. The 4xx and 5xx reference tracings in the record are 2. The 4xx and 5xx reference tracings in the record are

appropriate to the 1xx heading in that contextsappropriate to the 1xx heading in that contexts 3. Alternative headings would be recorded in the 7xx 3. Alternative headings would be recorded in the 7xx

fields in the authority record, with context markerfields in the authority record, with context marker NOTE: Separate records for alternative headings are not NOTE: Separate records for alternative headings are not

required ...required ...

Example of Model C recordExample of Model C record 001 001 ea55555ea55555 008/10 (Cataloging rules): c (AACR2)008/10 (Cataloging rules): c (AACR2) 008/11 (Subject system/thesaurus rules): a (LCSH)008/11 (Subject system/thesaurus rules): a (LCSH) 040 $b (Language of cataloging): eng (English)040 $b (Language of cataloging): eng (English)

100 0# $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C.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 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 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 Kleopatra, $c Queen of Egypt, $d d. 30 B.C. 400 0# $a Kliyubatra, $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.) 700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? <context> $0 fa44444$? <context> $0 fa44444 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? <context> 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? <context> $0 ga33333$0 ga33333 700 04 $a <Heading for Cleopatra in Arabic, formulated according to appropriate 700 04 $a <Heading for Cleopatra in Arabic, formulated according to appropriate convention> $? <context> $0 aa66666convention> $? <context> $0 aa66666 700 06 $a Cleopatre $b VII $c reine d'Egypte, $d 30 av. J.-C. $? <context> 700 06 $a Cleopatre $b VII $c reine d'Egypte, $d 30 av. J.-C. $? <context> $0 cfa77777$0 cfa77777

?

?

Model C - context markerModel C - context marker

Context Marker $7Context Marker $7

<rules=cataloging code or thesaurus designation> / <audience> / <rules=cataloging code or thesaurus designation> / <audience> / <language of catalog><language of catalog>

e.g. $7aacr//chi $7aacr//spa $7rake.g. $7aacr//chi $7aacr//spa $7rak

Example Example

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- <etc.>510 2# $a Catholic Church. $b Pope (1978-: John Paul II)700 04 $a Juan Pablo $b II, $c Papa, $d 1920- $7 aacr//spa700 06 $a Jean Paul $b II $c pape, $d 1920- $7 aacr//fre700 04 $a Jean Paul $b II $c (Pape), $d 1920- $7 ncafnor700 04 $a Johannes Paul $c Papst, $b II $7 rak700 04 $a <Chinese heading for John Paul> $b II $c <Chinese designation for Pope> $d 1920- $7 aacr//chi

700 _4=source not specified

AdvantagesAdvantages

Because the notion of “context”may be adjusted to suit various Because the notion of “context”may be adjusted to suit various situations, Model C is extensible and flexible.situations, Model C is extensible and flexible.

It supports any reference structures required by the cataloguing It supports any reference structures required by the cataloguing or thesaurus rules usedor thesaurus rules used

It supports simple identification of alternative headings for It supports simple identification of alternative headings for display, in addition to linking to alternative authority records with display, in addition to linking to alternative authority records with their full reference structures.their full reference structures.

Context markers would be optionalContext markers would be optional or records that apply only to a or records that apply only to a single context, or when the context functionality is not needed for single context, or when the context functionality is not needed for record management or displays.record management or displays.

"How are about HKCAN records?”"How are about HKCAN records?”

08941020nc acannaabn |a aaa |||010 $anr 94034993035 $a(DLC#)nr 94034993a040 $aDLC-R$beng$cDLC-R$dOCoLC$dHkCU$dHkCAN066 $c$1100 1 $aZhou, Ying,$d17th cent.400 1 $wnne$aChou, Ying,$d17th cent.400 1 $aZhou, Fangshu,$d17th cent.400 1 $a 周方叔 ,$d17th cent.400 1 $aChou, Fang-shu,$d17th cent.670 $aChih lin ( 卮林 ), 1992:$bt.p. (Chou Ying)670 $aChung wen ta tz{176}u tien ( 中文大詞典 ):$bv. 6, p. 290 (Chou Ying; of Ming; native of P{176}u-t{176}ien; t. Fang-shu; author of Chih lin; lived around the mid of Emperor Ch{176}ung-chen reign)670 $aHis 卮林 : 10 卷 , 附補遺 1 卷 , [1963]:$bt.p. ( 周嬰 )670 $a 中國人名大辭典 , 1934:$bp. 545 ( 周嬰 , 明莆田人 , 字方叔 , 崇禎中以貢生知上猶縣 , 所著卮林 , 体近類書 )700 1 $a 周嬰 ,$d17th cent.

$7aacr//chi2nd indicator 4 or 7

Subfield 7 context marker

100 1 $a 周嬰 ,$d17th cent. 400 1 $wnne$aChou, Ying,$d17th cent.400 1 $aZhou, Fangshu,$d17th cent.400 1 $a 周方叔 ,$d17th cent.400 1 $aChou, Fang-shu,$d17th cent.670 $aChih lin ( 卮林 ), 1992:$bt.p. (Chou Ying)670 $aChung wen ta tz{176}u tien ( 中文大詞典 ):$bv. 6, p. 290 (Chou Ying; of Ming; native of P{176}u-t{176}ien; t. Fang-shu; author of Chih lin; lived around the mid of Emperor Ch{176}ung-chen reign)670 $aHis 卮林 : 10 卷 , 附補遺 1 卷 , [1963]:$bt.p. ( 周嬰 )670 $a 中國人名大辭典 , 1934:$bp. 545 ( 周嬰 , 明莆田人 , 字方叔 , 崇禎中以貢生知上猶縣 , 所著卮林 , 体近類書 )700 1 $aZhou, Ying,$d17th cent.

Another exampleAnother example

Allow swap of headingsAllow swap of headings

040 $aNIC$beng$cNIC$dNIC$dOCoLC$dHkCU$dHkCAN066 $c$1100 1 $aDong, Jianhua,$d1937-400 1 $wnne$aTung, 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 p{176}ing chuan ( 董建華評傳 ), 1996:$bp. 12 (English name C.H. Tung) p. 111 (b. 1937 in Shanghai)670 $aRadio broadcast, Dec. 11, 1996$b(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, 1996:$bcaption (Tung Chee-Hwa)700 1 $a 董建華 ,$d1937-

040 $aHkCU$cHkCU066 $c$1110 1 $aHong Kong (China).$bProvisional Legislative Council Commission410 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 $wa$aHong Kong.$bLegislative Council Commission510 1 $wa$a 香港 .$b 立法局行政管理委員會

510 1 $wb$aHong Kong (China).Legislative Council Commission510 1 $wb$a 香港 ( 中國 ).$b 立法會行政管理委員會

670 $aIts 事務報告 , 1997-98:$bcover ( 臨時立法會行政管理委員會 The Provisional Legislative Council Commission)

710 1 $a 香港 ( 中國 ).$b 臨時立法會行政管理委員會

Parallel field needed?Parallel field needed?

Linking needed?Linking needed?

For maintenance?For maintenance?

For display?For display?

INNOPAC System interfaceINNOPAC System interface

Working on it …, improving …, Working on it …, improving …, and ... in the right direction …and ... in the right direction …

Your input is important!Your input is important!

See also earlier

See also later

Goal achieved?Goal achieved?

Yes or NoYes or No

100 0 $aBingxin,$d1900-

400 0 $aBing-xin,$d1900-400 0 $wnne$aPing-hsin,$d1900-400 1 $wnnaa$aHsieh, 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-

??

There are still more to do ...There are still more to do ...

Standardization of HKCAN records, more Standardization of HKCAN records, more discussion on the HKCAN 7xx modeldiscussion on the HKCAN 7xx model More members to join and contributeMore members to join and contribute

Enhancement of HKCAN OPACEnhancement of HKCAN OPAC More testing on the OPAC linking. Is there More testing on the OPAC linking. Is there other display options?other display options? How does INNOPAC support the authority How does INNOPAC support the authority control of 7xx when data maintenance is control of 7xx when data maintenance is concerned?concerned?

Thank you :)Thank you :)

Maria Lau (CUHK) Dec 11, 2001 HKIUGMaria Lau (CUHK) Dec 11, 2001 HKIUG