Many cataloguers following this thread will recognize that the idea of controlling for a concept but allowing the application (or user) to select the desired linguistic form to display isn't new - it's the very idea of "access control" that Barbara Tillett advanced many years ago. (See, for example, this paper: http://www.loc.gov/catdir/bibcontrol/tillett_paper.html). I hadn't noticed that AAT stores singular and plural forms as variants and was very interested to see the example that Steven gives below.
Looked at more broadly, it's an issue that arises not only for qualifiers, or for singular vs plural forms, but in many other contexts as well. Romanized vs vernacular forms of names are an obvious example. Some cataloguers may also have noticed examples of a similar problem in the RDA relationship designators, where a term such as "sponsoring body" or "issuing body" is applicable not only to corporate bodies but also (less elegantly) to individual persons.
In other words, there is a general problem here waiting for a solution.
Naun.
--
Chew Chiat Naun
Director, Cataloging & Metadata Services
110D Olin Library
Cornell University
(607) 254 8031
-----Original Message-----
From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Steven Folsom
Sent: Sunday, March 01, 2015 10:29 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Best practices in updating authority records
Ted,
I don’t know about cases where the subfield $a is repeated in the 1XX, but I’ve trolled id.loc.gov quite a bit and have never seen one. If this is happening, I have to imagine that when we’re doing this work in linked data that the entities will be separated, with a relationship likely created between them. If the repeated $a's truly are a group that would be a singular entity (hopefully with has member/part relationships to the individual member/parts). In this case the singular of a group noun should be the qualifier for the corporate entity. Either way, the singular noun from the concept linked to by the 374 would be appropriate for qualifying the 1XX. For example:
374 Dancers $u http://id.loc.gov/authorities/subjects/sh85035655 $v lcsh could/should store the singular noun ‘Dancer’.
374 Dance companies $u http://id.loc.gov/authorities/subjects/sh85035631
$v lcsh could/should store the singular noun ‘Dance company’.
The plural of these concepts (Dancers and Dance companies) could still be used for subject headings if an institution preferred that. This should be configurable in the application.
Getty AAT is an example of a vocabulary storing and encoding plural and singular nouns for a concept, e.g.
http://www.getty.edu/vow/AATFullDisplay?find=dancers&logic=AND¬e=&englis
h=N&prev_page=1&subjectid=300025653
I dream of a time when there is no need for a cataloger to struggle to
create an AAP, seriously I do. Instead the display value is created from a
concatenation those traits we can assert about the entity; these traits
need to point to a URI. This isn’t science fiction, RIMFF is currently
attempting something like this.
http://www.marcofquality.com/wiki/rimmf3/doku.php?id=rimmf
Again, I’m new to this group, so… perhaps I’m missing something.
Thanks,
Steven
On 3/1/15, 3:05 PM, "Ted P Gemberling" <[log in to unmask]> wrote:
>Steven wrote: "The authority should store the singular and plural… and
>with the URI, an application can access the most appropriate literal."
>
>Steven, would you tell us more about how the application would access the
>most correct form from the URI? Do you mean the application determines
>the form or the application makes it possible for the cataloger to do so
>from the URI?
>
>If the cataloger is going to put both a singular and a plural form on the
>authority, presumably that means she already knows what are singular and
>what are plural forms in that language. So she probably already knows
>which would be more appropriate for the AAP. So why put both forms on the
>authority?
>
>Ted Gemberling
>UAB Lister Hill Library
>
>
>-----Original Message-----
>From: Program for Cooperative Cataloging
>[mailto:[log in to unmask]] On Behalf Of Steven Folsom
>Sent: Friday, February 27, 2015 12:25 PM
>To: [log in to unmask]
>Subject: Re: [PCCLIST] Best practices in updating authority records
>
>I’m new to following PCC efforts and this list, so maybe I need to
>understand some of the issues more, but...
>
>There’s a lot of focus on the literal here. Is there any effort to
>encourage/require $u’s and $v's in authorities? If not already, I hope
>this is in scope for PCC Strategic Direction 3. The authority should
>store the singular and plural… and with the URI, an application can
>access the most appropriate literal.
>
>Similarly, I’d like to be able to use the 024 (or another field) for
>capturing URIs *distinguishable from other identifier numbers*.
>
>Related, it would be nice if we could visit best practice for storing
>dereferenceable URIs in bibs, *distinguishable from other control
>numbers*. I realize that there is the $0 for this (we’re using this in a
>couple cases), but I would like to see something more like the $u $v
>structure (where you know it’s a URI in the $u and the source is kept
>separately). The following is almost there.
>
>700 1 ‡a Ceci, Stephen John ‡e thesis advisor
>‡0(uri)http://vivo.cornell.edu/individual/individual23258
>
>
>
>
>
>
>On 2/27/15, 8:20 AM, "Ehlert, Mark K." <[log in to unmask]> wrote:
>
>>From: Program for Cooperative Cataloging
>>[mailto:[log in to unmask]] On Behalf Of Ted P Gemberling
>>>
>>> Here is the document we got in training which said repeat the 372 and
>>>374
>>> for different controlled vocabularies.
>>> http://www.loc.gov/catdir/cpso/dcmz1.pdf
>>
>>
>>Also supported by the fact that the $2 is non-repeatable.
>>
>>--
>>Mark K. Ehlert O'Shaughnessy-Frey Library
>>Cataloging and Metadata University of St. Thomas
>> Librarian 2115 Summit Avenue
>>Phone: 651-962-5488 St. Paul, MN 55105
>><http://www.stthomas.edu/libraries/>
>>
>> "Experience is by industry achieved // And perfected by
>>the swift course of time"--Shakespeare, "Two Gentlemen of
>>Verona," Act I, Scene iii
>>
|