This conversation has gotten totally out of hand through a series of bad
examples.
DC.Type is a place where we are recording genres of online and offline
resources. Some genres take place in time. Exhibits, auctions,
performances, readings, etc. are events which defined by the time and place
they occur and which involve the world of "document-like objects" we have
decided to describe. Furniture, paintings, symphonies, poems, speeches,
etc. participate in these events just an articles may appear in a book or
journal. Just as the citation describes the book or journal in which an
article occurs, with pagination etc. specific to that location,
objects appear in exhibits, auctions, performances with specific numbers
and descriptions attached to them. These specific references locate the
item with the event. Discovery will often seek items co-located in an
event. The specific descriptors are critical to its documentation.
David
At 08:59 AM 9/9/98 -0400, James Weinheimer wrote:
>All,
>Another of my "two cents' worth."
>Isn't the Olympics the subject of the video? We catalog books, serials,
videos, etc.
>every day about such things. To link everything together, we must use a
consistent
>heading, such as:
>Olympic Games (21st : 1976 : Montreal, Quebec).
>Also, in the case of Bonnie Prince Charlie drinking tea in a certain
teapot on a
>certain date, the question for the cataloger becomes: do I want people to
be able to
>search the catalog for this information?
>If no, the information can go into a simple note.
>If yes, the cataloger must decide how to describe the event. In this case
of Prince
>Charlie, I would have to do some thinking to figure out a decent way of
describing the
>event. I should also discuss it with my colleagues.
>It would also make sense to believe that we may get other things from the
event of
>Charlie's tea drinking. If so, when someone catalog these things, they
should use the
>same words to describe this particular event. Who knows? Maybe Charlie had
many
>teaparties with many teapots. If I use different words, it could lead to
either
>confusion, or I may not be able to find all the items.
>
>Finally, something as vague as Charlie's tea drinking could legitimately
be described
>in a whole bunch of ways, all of which are "correct", but for the sake of
consistency
>of retrieval, I have decided to use only one form in the catalog. Still,
for the user's
>ease (and the cataloger's efficiency when the next item from Charlie's tea
party
>arrives) it would only make sense to add some cross-references, since not
everyone
>thinks in the same way.
>
>Should all this information be placed over and over again in the
individual records? Or
>should it be in a separate record, describing the event? Obviously, it
would be much
>more efficient to make a separate record.
>So, a separate authority record, replete with cross-references and Broader
Terms,
>Narrower Terms, Related Terms, Scope Notes, is actually a very natural
outgrowth of
>creating a catalog.
>
>That's one cataloger's thoughts.
> Jim Weinheimer
> Princeton University
> [log in to unmask]
>
>Alex Satrapa wrote:
>
>> Simon Pockley wrote:
>>
>> > On Sep 8, 1:21pm, Jul,Erik wrote:
>> >
>> > > Perhaps someone who actually wants or needs to create metadata records
>> > > for events could enlighten the list with an example and an explanation.
>> >
>> > If I could add another example: I was involved in a live cam
conversation
>> > (CuSeeMe), between New York and Australia. ...
>>
>> Umm... howabout this for an example of an event...
>>
>> In the year 2000, hundreds of athletes from around the world will be
gathering in
>> and around Homebush Olympic Center, Sydney, Australia.
>>
>> This *EVENT* (all-capitals, flashing lights, whathaveyou) will be
recorded in many
>> forms including video tape, audio tracks and photographs (both digital
and the
>> antiquated chemical paper form ;). People will be taking home souvenirs
from this
>> event, including olympic flags, gold, silver and bronze medallions, and
even blades
>> of grass from the stadium(s? stadii?).
>>
>> A video recording of the Olympics will be just that - a video recording
of the
>> Olympics. The video itself isn't the Olympics. The Olympics will be
(have been) a
>> transient event.
>>
>> To me, the recording of "metadata" about an event seems important, but
I'm not sure
>> that an event can be "indicated"
(recorded/remembered/signified/whatever) by the
>> usual DC set. Who is the publisher of the Olympics? Who is the
author/creator?
>>
>> You could stretch the model and say that the Publisher of the Olympics
is the
>> SOC/IOC, with the joint authors being every single athlete, umpire,
referee, timer,
>> water server, grounds keeper... ad nauseum.
>>
>> If we feel that an Event can be squeezed into our document-oriented
metadata model,
>> then we must have sub-elements dc.date.start, dc.date.finish (which
could otherwise
>> be the dates on which a composer started and finished a particular
composition).
>>
>> Just my two bits worth...
>> -Alex
>
>
>
>
>
>
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
|