34
Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 • Helsinki Eeva Murtomaa National Library of Finland

Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Embed Size (px)

Citation preview

Page 1: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Authority control examples according to

FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21

• Helsinki• Eeva Murtomaa• National Library of Finland

Page 2: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

FRAD, Functional Requirements for Authority Data

• a conceptual model• an extension and expansion of the FRBR model

• The Working Group on functional Requirements and Numbering of Authority Records (FRANAR)

• - was established in April 1999

• Published for IFLA by K.G. Saur, 2009• IFLA Series on Bibliographic Control, vol. 34• ISBN 978-3-598-24282-3

• Available later on IFLANET2

Page 3: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Scope:

1)to define functional requirements of authority records

2) to study the feasibility of an International Standard Authority Data Number, ISADN

3) to serve as the official IFLA liaison to and work with other interested groups concerning authority files

Page 4: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

An authority file is used

-to provide an analytical framework for the analysis of functional requirements

-for relating the data that are recorded in authority records to the needs of the users

- for the international sharing and use of authority data both within the library sector and beyond

Page 5: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

5

Person

Family

Corporate body

work

expression

manifestation

item

concept

object

event

place

rules

agency

name

identifier

Appellation

Known by

assigned

basis for

govrned by

applied bycreated/modified by

Associated with / responsible for

bibliographic entities

Persons, families and corporate bodies are treated as entities for getting much more flexibility in the controlled naming and for for eliminating redundancies because the names for these entities can be controlled in an authority record and linked to other authority records or to bibliographic records or holding records as needed

controlledaccess point

Page 6: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Who are the users

Authority record creators

Reference librarians

Library users

and what are the user tasks

Find

Identify

Contextualize

Justify

Page 7: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

7

search: Astrid Lindgren

Astrid Lindgren

Astrid Lindgren

Page 8: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

entity

relationship

FRAD = entity relationship model

the first step is to identify the entities, that are of interest to the users

to identify the relationships between those entities

to identify the attributes of each entity

entity name

Astrid Lindgren

Page 9: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Helen Lucas (Fonds)

The Christmas Birthday Story production records (Series)

The Christmas Birthday Story (Item)

Earlier: “provenance”” “the organization or individual that created, accumulated and/or maintained and used documents in the conduct of personal or corporate activity”

Now: “the relationships between records and the organizations or individuals that created, accumulated and/or maintained them in the conduct of personal or corporate activity”

relationship

In: JAO, Journal of archival organization

Page 10: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

10

Lindgren, Astrida, 1907-2002 Lindgr¯ene, Astrida,|1907-2002

 Lindgrenová, Astrid, 1907-2002

 Lindgrena, Astrida, 1907-2002

 Lindgrene, Astrida, 1907-2002

 Lindjrin, Astrid, 1907-2002

 Lindgrin, Astrid, 1907-2002

 Lingran, Ästrid,  1907-2002

 Lindgirin, Astrid,  1907-2002

 Lindgran, Astrid, 1907-2002

 Lindjrin, Astrid, 1907-2002

 Lindgrin, Astrid, 1907-2002

 Rindoguren, Asutoriddo, 1907-2002

 Lingelun, Asitelide, 1907-2002

 Rinduguren, Asut'uridu

NAME AUTHORITY FILE

  Lindgren, Astrid 

attributes:14.11.190728.1-2002authorfemaleVimmerbyStockholmSwedenSwedishChildren’s literatureRight Livelihod Award 1994H.C.Andersen Award

•relationships between an entity and specific instances of the ”name” by which that entity is known

an authority record is defined as the aggregate of information about an instance of an entity whose name is used as a controlled access point for bibliographic citations or records in a library catalogue or bibliographic file

Page 11: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

11

Relationshipse.g.earlier nameEricsson, Astridvariant nameEricsson, Anna

later nameLindgren, Astridvariant names and alternative linguistic forms Lindgren, Astrid (Anna Emilia)Lin'gedeng, Aosirui Lin'gelun, AsitelideLimdgren, AstridRindŭgŭren, Asŭt'ŭridŭ

Lindgren, Astrid, 1907-2002 Authority record: authorized form of name for the entity as the preferred form

variant forms of name and related names also usedas controlled acces points

Page 12: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

12

sequential relationship

• Split

• BodyBody A

Body A1

Body A2

Page 13: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

13

Body A

Body B

MergedBody

Page 14: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Kandinsky, Vassily (1866-1944)

• Kandinskii, Vasilii Vasilevich

• Kandinskij, Vasilij• Kang-ting-ssu-chi,

Wahsili• Kandinsky, Wassily

Wassiljewitsch• Kandinsky, Vasili

Vasilevich• Etc.

• Roles:• artist (preferred)

• painter

• author

• draftsman

• engraver (printmaker)• theorist• teacher

•  

• Nationalities:• Russian (preferred)• French• German

14

Gender: male

Born:  Moscov Died:  Neuilly-sur-Seine

Page 15: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Kandinsky, Vassily (Russian painter, 1866-1944)• Relationships:

• Person to institution

• member of .... 

• president of…

• New Artists Association of Munich

• (International artists' organization, active ca. 1909-1912 )

• professor at .... 

• Bauhaus

• (German art school, 1919-1933)

• Events: active:

• Germany

• France

• Moscow

• Biographies:

• Russian painter, 1866-1944)(Russian artist, 1866-1944)

• etc.

• Sources and Contributors: • Canadian Centre for Architecture database• etc.

• Subject:• Bibliography of the History of Art (BHA)• [online], 1990-• Etc.

15

Person to person

teacher of .... Ardon Mordecai(Israeli painter, 1896-1992) Braiq, Paul(French painter and engraver, 1906-1972)  Feininger, T.Lux(American photographer, born 1910, active in Germany and the United States) …

etc.

cousin of .... Cimiakin, An’ja (1892-1911)spouse of Cimiakin, An’ja (1892-1911)

Page 16: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

16

000.01856cz a2200385n 450 001 3286633005 20081212071809.0008 800418|n acannaabn |b aaa010_ |a n79059310 035_ |a(OCoLC)oca00292352040_ |aDLC|b eng100.1_ |a Kandinsky, Wassily, |d 1866-1944400.1 _ |a Kandinskii, Vasilii Vasilʹevich, |d 1866-1944400.1 _ |a Kʻang-ting-ssu-chi, Wa-hsi-li, |d 1866-1944…670__ |a Author’s The art of spiritual harmony ... 1914.670__ |a His Kandinsky in Paris, 1934-1944, 1985: |b CIP galley (Vasily Kandinsky)… 046 Special coded dates -|f1866|f1944 370 Associated place__ |a Kandinsky, Wassily |a Moscov |b Neuilly-sur-Seine[born in Moscov; died in Neuilly-sur-Seine]373 Activities__ |a New Artists Association of Munich |s1909|t1912$6 - linkage (NR) …to link field data to specific institutions, to other records, or to other fields374 _|a professor at Bauhaus (German art school) |s1919 |t1933 375 gender _|a male

Page 17: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Field 370 associated place

100 1 $aKandinsky, Wassily, $d 1866-1944

370 $a Moscow $b Neuilly-sur-Seine

370 $e Munich $s 1896$t 1913

370 $e Russia $s 1914 $t1920

370 $e Germany $s 1921

370 $e France (citizen 1939)

• $u - Uniform Resource Identifier Uniform Resource Identifier (URI), for example a URL or URN, which provides electronic access data in a standard syntax. This data can be used for automated access to an electronic item using one of the Internet protocols.

• In field 370, subfield $u is used to record the location of the source of information about a place recorded in the field that is accessible electronically.

Page 18: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Field 046

110.2 # $a New Artists Association of Munich

410.2 #$a Neue Künstlervereinigung München

046 $s1909 $t1912 New artists' organization,was active ca. 1909-1912

$s Start period

$t End period

$u link to a source of information

Page 19: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Relational/object-oriented database structureaccording to Tom Delsey

1.Manifestation record 245 $a Voyage au Cap-Nord, par la Suede, la Finlande et la Laponie740 $a Voyage en Suede par J. Acerbi I / II / III740 $a Voyage au Cap-Nord (Lapponica)245 $c par Joseph Acerbi260 $a Paris260 $b Levrault, Schoell et Comp260 $c 1804300 $a 3 nid. (1: XLIV, 320 ; 2: xiv, 429 ; 3: vi, 382 s.)

2.Work record 100 $t Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799500 $a text100 $0 Acerbi, Giuseppe $e creatorISTC xxx-xxxx-xxxxxxxx-x

3. Expression record240 $l French…700 $0 Lavallee, Joseph $e translator

4. Authority record (Person)100 $a Acerbi, Giuseppe400 $a Acerbi, G.100 $d 1773-1846

Authority record(Person)100 $a Lavallee, Joseph374 $a translator

Item record561 $a Reenpää Collection562 $a Numbered 56/150

(Lapponica)

Work embodied

Expression empodied Expression of work

Page 20: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

100 $a a Acerbi, Giuseppe, $d 1773-1846. $t Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799 $l Dutch

100 $a a Acerbi, Giuseppe, $d 1773-1846. $t Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799 $l French

100 $a a Acerbi, Giuseppe, $d 1773-1846. $t Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799 $l Italian100 $a a Acerbi, Giuseppe, $d 1773-1846.

$t Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799 $l Swedish

Expression level name-title authority records

Page 21: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

Relational / object-oriented database structure245 $ Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799 740 $a Voyage en Suede par J. Acerbi740 $a Voyage au Cap-Nord (Lapponica) 245 $c par Joseph Acerbi ; traduction d’apres l’original anglais, revue sous les yeux de l’auteur, par Joseph Lavallee.260 $a Paris 260 $b Levrault, Schoell et Comp., 260 $c 1804300 $a 3 nid. (1: XLIV, 320 ; 2: xiv, 429 ; 3: vi, 382 s.) ; $c 8:o…

100 $t a Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799 …100 $a Acerbi, Giuseppe$e creator

Relationship information530 $0 General and miscellaneous remarks concerning Lapland

240 $l French…700 $0 Lavallee, Joseph $e translator

EXPRESSION RECORD

130 $a Generl and miscellaneous remarks concerning Lapland / by Knud Leem …500 $i based on (work) $a Acerbi, Giuseppe, $d 173-1846 $t Travels through Sweden, Finland, and Lapland to the North Cape in the years 1798 and 1799

WORK RECORD

100 $a Acerbi, Giuseppe 400 $a Acerbi, G.100 $d 1773-1846…

REGISTRATION RECORD(PERSON)

100 $a Lavallee, Joseph 400 $a Bois-Robert, Joseph L. de100 $c translator…

REGISTRATION RECORD(PERSON)

work embodied

expression embodied

expression of work

561 $a Reenpää Collection562 $a Numbered 56/150 (Lapponica)…

ITEM RECORD

exemplar of manifestation

WORK RECORD

100 $a Leem, Knud 400 $a Lemius, Canutus…100 $d 1697-1774

REGISTRATION RECORD(PERSON

Page 22: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

22

RDA is based on the FRBR and FRAD Models

RDA provides instructions for recording attributes of persons, families, corporate bodies and places.

RDA defines vocabularies for expressing relationships between persons, families and corporate bodies and between these entities and FRBR Group 1 entities.

RDA

http://www.rda-jsc.org

http://www.rda-jsc.org/rda.html

Page 23: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

23

http://www.isni.org/ International standard name IdentifierDraft ISO Standard (ISO 27729)Libraries, rights management, book trade, publishers, media content industries

VIAF: The Virtual International Authority File http://viaf.org/

EAC-CPF: Encoded Archival Context – Corporate Bodies, Persons, and FamiliesCommunication standard for exchange of authority recordsISAAR (CPF) Draft Standard http://eac.staatsbibliothek-berlin.de

FO:AF Friend of a Friend Social networking metadataGranularity of parts of a name http://xmlns.com/foaf/spec/

Encoded Archival Context - Corporate Bodies, Persons, and Families" (EAC-CPF) to emphasize its important role in archival description and its relationship with the Encoded Archival Description standard http://eac.staatsbibliothek-berlin.de/

Names Funded by JISC Repositories and preservation programmeLed by MIMAS British Library is a partner

National Names Service Phase 1 – prototypeData model based on FRADMappings from MARC 21; ISAAR CPF; SWAP; NLM DTD

Phase 2 – Develop national names service Author submission Institutional Repositories UKPMC Intute

Page 24: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

24

JISC Names Projecthttp://names.mimas.ac.uk/documents/ISAAR-CPF_mapping.pdfElement Definition Additional information FRAD FRAD Entity Attribute/relationship CommentAdditional instructions

RDA to FRAD mapping

http://www.rda-jsc.org/docs/5rda-rdafradmappingrev2.pdf

ISAAR(CPF)2The final version of ISAAR(CPF)2 will be available on the home page of ICA/CDS— http://www.hmc.gov.uk/icacds/eng/standards.htm | http://www.ica.org/biblio.php?pbodycode=CDS&ppubtype=pub&plangue=eng..

Page 25: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

25

Relationships between Names and Persons, Families, Corporate bodies, and Works

• Entity Type Sample Relationship Types

• Person Name• Name Name• real name relationship• pseudonym relationship• secular name relationship• name in religion relationship• official name relationship• earlier name relationship• later name relationship• alternative linguistic form relationship• other variant name relationships• Family Name• alternative linguistic form relationship

Page 26: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

26

Relationships between Names and Persons, Families, Corporate bodies, and Works

• Corporate Body Name• expanded name relationship• acronym / initials / abbreviations relationship• pseudonym relationship• alternative linguistic form relationship• other variant name relationships• Work Name• alternative linguistic form relationship• conventional name relationship• other variant name relationships

Page 27: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

27

Relationships between controlled access points

• Entity Type Relationship Type• Access Point Access Point • Parallel language relationship• Alternate script relationship• Different rules relationship• Name/corresponding subject term

or • Classification number relationship

Name/identifier relationshipRelationships in this category may be made explicit by means of linking devices such as linking fields and control subfields

Page 28: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

28

MARC21

100 1#$aCoughlan, Dan 500 1 ##$wr$i alternate identity$a Blair, Eric

  User display example: Blair, Eric   See also his real identity: Coughlan, Dan Reciprocal of previous example: 100 1#$a Blair, Eric 500 ##$wr $i real identity $a Coughlan, Dan

  User display example: Coughlan, Dan See also his alternate identity Blair, Eric

Page 29: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

29

Relationships between persons and corporate bodies

Associated Artists (1881-1883)(American design group, NYC)

Related people

Tiffany, Louis ComfortAmerican painter, designer, patron, 1848-1933

Colman, Samuel

De Forest, Lockwood American painter, designer, 1850-1932

… etc.

founder

member

member

Page 30: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

30

MARC21

110 2 $a Associated Artists (1881-1883)(American design group, NYC)

500 $wr $i founder $a Tiffany, Louis Comfort $d 1848-1933

User display example:

Tiffany, Louis ComfortSee also founded organization: Associated Artists

Associated ArtistsSee also founder: Tiffany, Louis Comfort,1848-1933

Members are given in the same way

Page 31: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki
Page 32: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

• 110 2#$aLoblaw Companies Limited • 510 2#$wt$aGeorge Weston Limited  

• Cross reference display example: Loblaw Companies Limited   • search also under the immediate parent body:  • George Weston Limited

• t - Immediate parent body • Heading in the 5XX field is the name of a parent body of the entity in

the 1XX field. Code t is applicable only to corporate bodies. It may be used for archival material where there is a need to identify fully the hierarchical structure of a corporate entity.

32

Page 33: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

33

• But

In certain instances, the model treats an association between one entity and another simply as an attribute of the first entity.

For example the place of the birth is treated simply as an attribute of person

However, it is possible to develop the model further to create a relationship ”born in” as a relationship between the two entities person and place.

Page 34: Authority control examples according to FRAD, (Functional Requirements for Authority Records), RDA (Resource Description and Access),and MARC21 Helsinki

FRAD relationships are also to be seen in RDA

• Recording Relationships• Section 5 -Recording primary relationships• Section 6 -Recording relationships to persons, families, and

corporate bodies associated with a resource• Section 7 -Recording subject relationships• Section 8 -Recording relationships between works, expressions,

manifestations and items• Section 9 -Recording relationships between persons, families, and

corporate bodies• Section 10 -Recording relationships between concepts, objects,

events, and places• Supplementary Guidelines and Instructions

34