To: Joint Steering Committee for Development of RDA From: Alan Danskin, British Library Representative Subject: Revision of RDA

Size: px

Start display at page:

Download "To: Joint Steering Committee for Development of RDA From: Alan Danskin, British Library Representative Subject: Revision of RDA"

Briana Singleton
5 years ago
Views:

1 6JSC/BL/14/rev Page 1 of 6 To: Joint Steering Committee for Development of RDA From: Alan Danskin, British Library Representative Subject: Revision of RDA Introduction This proposal seeks to address problems encountered when constructing authorised access points for conferences. There is overlap between Place Associated with the Body, Associated Institution, and Number, Date and Location of a Conference, Etc. which may result in ambiguity or variation in the way access points are constructed. The table below is an extract from LC NACO Authority File, illustrating the variation between authorised access points for two conferences for which collective and individual access points have been established. Conference Heading (10th : 1998 : (12th : 2000 : (16th : 2006 : (17th : 2008 : (1st : 1989 : (3rd : 1991 : (5th : 1993 : (6th : 1994 : (7th : 1995 : que sobre "Mitos, Tópicos y Realidades del Poder en Europa y América" Conference 1 conference series

2 Conference Heading ( sobre Cultura, Educación y Sociedad en Europa y América (1st : 1999 : Bilbao, Spain), sobre "Problemas de la Historia Hoy" (Universidad del País Vasco) (Universidad del País Vasco) (3rd : 2001 : Bilbao, Spain) (Universidad del País Vasco) (6th : 2004 : Vitoria, Spain) (Universidad del País Vasco) (8th : 2006 : Vitoria, Spain Conference 2 conference series 6JSC/BL/14/rev Page 2 of 6 This results in inconsistency between the collective and individual access points created for the same series of conferences. For example: Collective access point: ( Individual access point: (6th : 1994 : Salamanca, Spain) The level of specificity required by Place Associated with the Body, is broader than required by Number, Data, and Location of a Conference, Etc., which may result in inconsistency, for example: (Spain) (

3 6JSC/BL/14/rev Page 3 of 6 The same issues also arise between Associated Institution used for disambiguation ( ) and Associated Institution used as a Location of a Conference To address the problem, it is proposed that, when an access point represents a series of conferences that were all held in the same place, the location of the conference should be recorded as an attribute of the conference. The instruction for adding them to access points should be consistent with the general instructions at for Place Associated with the Body.. This will avoid confusion between the location of the entity, and terms added to access points for disambiguation. In effect, this follows the provisions of LCRI 24.7B On the name authority record for a conference heading, do not add the number, date, or place to the name when the conference is an ongoing one, even if all the meetings were held in one place (cf. 24.7B4). Apply this both to meetings entered directly under their own names and to meetings entered subordinately to headings for corporate bodies. Change Access Point for a Series of Conferences, Etc. Change the current text of and move the examples block: Current text If all conferences, etc., in a series were held in the same place, add the location to an access point representing the series of the conference, etc. Do not add the number or date of the conferences, etc. Change to: Marked up copy If all conferences, etc., in a series were held in the same place, add the location to an access point representing the series of the conference, etc. Do not add the number or date of the conferences, etc. EXAMPLE Blue Ridge Folklife Festival (Ferrum, Va.) Access point for its annual program book described as a serial. Held in the same location each year Salzburger Festspiele (Salzburg, Austria)

4 Access point for an audio recording of music performed at the festivals Intermountain West Student Philosophy Conference (University of Utah) Access point for its web site. Held at the University of Utah each year 6JSC/BL/14/rev Page 4 of 6 If the access point represents a series of conferences, etc., do not add the number, date or location of the conferences, etc. For access points for two or more conferences that have the same name, or names so similar that they may be confused, apply the instructions at , as applicable. EXAMPLE Blue Ridge Folklife Festival (Ferrum, Va.) Access point for its annual program book described as a serial. Held in the same location each year Salzburger Festspiele (Salzburg, Austria) Access point for an audio recording of music performed at the festivals Intermountain West Student Philosophy Conference (University of Utah) Access point for its web site. Held at the University of Utah each year Annual Symposium on Sea Turtle Biology and Conservation Access point for its proceedings described as a serial. Held in a different location each year World Series (Baseball) Access point for a collection of souvenir programs from various years. Held in different locations each year Clean copy If the access point represents a series of conferences, etc., do not add the number, date or location of the conferences, etc. For access points for two or more series of conferences that have the same name, or names so similar that they may be confused, apply the instructions at , as applicable. EXAMPLE Blue Ridge Folklife Festival Access point for its annual program book described as a serial. Held in the same location each year Salzburger Festspiele Access point for an audio recording of music performed at the festivals Intermountain West Student Philosophy Conference Access point for its web site. Held at the University of Utah each year Annual Symposium on Sea Turtle Biology and Conservation Access point for its proceedings described as a serial. Held in a different location each year World Series (Baseball) Access point for a collection of souvenir programs from various years. Held in different locations each year Outcome Clarifies the distinction between 1. Places and institutions recorded for disambiguation, which are always added immediately after the preferred name in both collective and individual access points. 2. Places and institutions recorded as the location of the conference: recorded in the individual access points only.

5 6JSC/BL/14/rev Page 5 of 6 3. Access points constructed consistently with conferences with non-unique names that are not always held in the same location. Conference Heading ( ( (10th : 1998 : ( (12th : 2000 : ( (16th : 2006 : ( (17th : 2008 : ( (1st : 1989 : ( (3rd : 1991 : ( (5th : 1993 : ( (6th : 1994 : ( (7th : 1995 : que sobre "Mitos, Tópicos y Realidades del Poder en Europa y América" sobre Cultura, Educación y Sociedad en Europa y América (1st : 1999 : Bilbao, Spain), sobre "Problemas de la Historia Hoy" (Universidad del País Vasco) Conference 1 conference Series Conference 2 conference series

6 Conference Heading (Universidad del País Vasco) (3rd : 2001 : Bilbao, Spain) (Universidad del País Vasco) (6th : 2004 : Vitoria, Spain) (Universidad del País Vasco) (8th : 2006 : Vitoria, Spain 6JSC/BL/14/rev Page 6 of 6 We estimate that the impact on existing headings is small. We have identified 84 records in LC/NACO in which the preferred form of name matches the pattern. In some, the place name is duplicated, once for uniqueness and once because all held in the same place: $asemana de Estudios Medievales (Estella, Spain)$c(Estella, Spain) $abiennale d'art contemporain (Brest, France)$c(Brest, France) In some the place name is redundant: $abiennale di Venezia$c(Venice, Italy) $atriennale di Milano$c(Milan, Italy) $aseattle Lesbian & Gay Film Festival$c(Seattle, Wash.)

Joint Steering Committee for Development of RDA Dave Reser, LC Representative Subject: Revision of RDA

To: From: Joint Steering Committee for Development of RDA Dave Reser, LC Representative Subject: Revision of RDA 11.13.1.8.2 Page 1 of 7 LC appreciates the efforts of the BL to address the distinction