Sorry, but I look at the names of DC elements and they clearly are
privileging the event of publication. I'm not sayting we couldn't revise
the whole thing, but giving DC.Type a value of event seems preferable to
starting over. Unless you are proposing in place of a cludge that we
redefine everything from scratch and deliver a new data model.
David
At 05:13 PM 9/10/98 -0400, Diane I. Hillmann wrote:
>David Bearman said:
>
>>The problem we are currently having with event is one that is built into
>>the worldview of the bibliographic community which privileges the position
>>of one event in the life cycle of a resource - its publication - above all
>>other events. Other communities consider events such as changes in
>>ownership, uses, performances, etc. to be equally significant to the event
>>of creation or authorship. DC has adopted the bibliographic community's
>>view of the world and is now trying to figure out how to position other
>>events if someone wants to document them. Its a cludge to have it as a
>>DC.Type but its probably the only cludge we can use.
>>David
>
>I couldn't resist taking this one on, because I'm not sure it's really
>true, at least not anymore. It's certainly true that AACR2 emphasizes the
>act of publication as the point in time for the capture of bibliographic
>information, but MARC has long since passed that by. Several people have
>pointed out that MARC authority records can be useful in at least providing
>a standard link to an event *name* that can be used to effectively bring
>together various resources associated with an event, if not to "catalog"
>the event itself.
>
>The Community Information Format actually has been used to "catalog" an
>event itself, in a way that integrates fairly well with other kinds of
>MARCish data, and might illuminate for our purposes how this could work for
>DC. Below is an example I've had hanging around for teaching purposes (it
>might even be from the MARC documentation, I don't remember). I think the
>trick is not to think that we have to have some kind of "complete" element
>set for an event, as we might for a resource that actually has some sort of
>"permanent" presence--say, a recording of this particular performance. The
>event record could record the specifics of the performance itself, and link
>to the record recording, which would then not necessarily have the same
>metadata (it might have an interview added, for instance, or specially
>created graphics, scrolling credits, or whatever). The idea of "authority
>files" which can carry information needed to create meaningful
>relationships in other metadata, is one that we should embrace with some
>relief.
>
>
>Leader/06 q (Community information)
>Leader/07 q (event)
>
>001 [Control number]
>003 [control number identifier]
>004 199310021993100119931001
>005 [Date and time of latest transaction]
>008 930816anannneng
>040 $a<USMARC code>$c<USMARC code>
>245 0$aContemporary Music and Inter-Disciplinary Music Theatre.
>275 $aRadcliffe Dance Center, Agazziz House$k437-2247
>301 $aOct. 1, 1992, 2 p.m.
>440 0$aLearning through performers program
>511 $aA lecture/demonstration by Paul Dresher and Rinde Eckert,
> composers and members, Paul Dresher Ensemble.
>520 8$a"About 'Pioneer,' which examines the burden of the American
>frontier past and the uncertainty of the future through Dresher's
>innovative electronic score and Ekert's arrangement."
>531 $bGeneral admission, $6.00; free for Harvard and Northeastern
>faculty, staff, and students; half-price discount for seniors, students,
>and advance sales buyers.
>650 0$aTheater.
>
>I am working on a piece on names and these sorts of links in general, but
>it's slower going than I'd like. I disagree with David's suggestion of
>event as a DC:type kludge, if it wasn't already obvious.
>
>I'm not going to touch the more ephemeral types of events Simon Pockley
>seems to be excited by--lord knows we're having enough trouble with these!
>
>Diane
>
>/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>Diane I. Hillmann
>Head, Technical Services Support Unit
>Cornell University Library E-mail: [log in to unmask]
>107B Olin Library Voice: (607) 254-5290
>Ithaca, New York 14853 Fax: (607) 255-6110
>WebGoddess: http://www.library.cornell.edu/tsmanual
>/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>
>
>
>
>
David Bearman
President
Archives & Museum Informatics
5501 Walnut St., Suite 203
Pittsburgh, PA 15232
tel. +1-412-683-9775; fax +1-412-683-7366
http://www.archimuse.com
|