Hi Stephen A.
I think SH's idea of reducing the date to one year and one year only is
okay, but in all truth, I think that
1112 Pierre Bonnard : the Colour of Memory : the CC Land Exhibition ǂd
(2019-2020 : ǂc London, England ; Copenhagen, Denmark ; Vienna, Austria)
covers all the bases and conveys the idea of a range of dates and locations
effectively and concisely.
$c: $c is repeatable, so : $c London : $c Copenhagen etc., probably should
be the choice to make.
For what it's worth, MARC authorities should include an example like this
in the 111 area.
My two cents
Bob in California
On Fri, Oct 22, 2021 at 8:05 AM Stephen Hearn <
[log in to unmask]> wrote:
> Thanks, that example helps. If this is a single multiyear event like a
> traveling exhibition which eventually ends. I'd group the dates as in the
> "Pierre Bonnard" example to show a single date span and a list of locations
> for a single event. Grouping each location with a year tilts toward seeing
> these as separate events rather than a single event. Clarifying the
> specific dates for each location could be done in a note, but not in the
> AAP. (I think.)
>
> Stephen
>
> On Fri, Oct 22, 2021 at 9:23 AM Stephen Arnold <
> [log in to unmask]> wrote:
>
>> Hi Stephen,
>>
>>
>>
>> The Real Ale conference is a fictitious example because my real one is
>> exceptionally long and bristling with diacritics. My real conference is
>> clear that it is a single conference reconvened at different locations and
>> times.
>>
>> The principle I wish to be clear about is whether dates should be grouped
>> together and locations together, as in this example below (though perhaps
>> with repeated subfields $c)
>>
>>
>>
>> 010 no2019111889
>>
>> 040 UPB ǂb eng ǂe rda ǂc UPB
>>
>> 1112 Pierre Bonnard : the Colour of Memory : the CC Land Exhibition ǂd
>> (2019-2020 : ǂc London, England ; Copenhagen, Denmark ; Vienna, Austria)
>>
>>
>>
>> or whether, if each date relates to a specific location, they should be
>> paired as we do in 264s with multiple publishers and places of publication.
>> Making subfields $d and $c repeatable
>>
>> seems to suggest the latter.
>>
>>
>>
>> Best,
>>
>> Stephen
>>
>>
>>
>> *From:* Program for Cooperative Cataloging <[log in to unmask]> *On
>> Behalf Of *Stephen Hearn
>> *Sent:* 22 October 2021 15:04
>> *To:* [log in to unmask]
>> *Subject:* Re: [PCCLIST] multiple locations and dates of a conference
>>
>>
>>
>> Why would this be considered a single conference instance and not three
>> instances of a conference?
>>
>>
>>
>> In the examples, one is a conference that lasted a few days over the end
>> of December and the beginning of January, and the other is a numbered
>> conference ("19") with each instance's separate gatherings taking place
>> within a year. Other numbers for the conference show the same pattern. So
>> one is bound as an instance by time and the other by its number. What binds
>> the Conference on Real Ale meetings together as a single conference
>> instance?
>>
>>
>>
>> If the proceedings are being cataloged as a serial or set, the 111 would
>> be just "Conference on Real Ale" without a qualifier (unless there's a
>> conflict).
>>
>>
>>
>> I'm not sure I understand the question.
>>
>>
>>
>> Stephen
>>
>>
>>
>> On Fri, Oct 22, 2021 at 4:22 AM Stephen Arnold <
>> [log in to unmask]> wrote:
>>
>> Dear gurus and mages,
>>
>>
>>
>> I can’t find good examples for a single conference which takes place in
>> multiple locations and over several years (admittedly, an unusual
>> situation).
>>
>> Is the correct format to pair each date with its corresponding location
>> something like this
>>
>> Conference on Real Ale ǂd (2015 :ǂc Paris, France :ǂd 2016 :ǂc London,
>> England :ǂd 2017 :ǂc Boston, Mass.)
>>
>> ?
>>
>> Examples like n 2021010322 & no2020124510 seem wrong to me.
>>
>> Thanks for any advice.
>>
>>
>>
>> Best wishes,
>>
>> Stephen
>>
>> *********************************
>>
>> Stephen Arnold
>>
>> Bibliographic Maintenance & Authority Control
>>
>> Bodleian Libraries, Oxford
>>
>> tel. 01865-277026
>>
>> *********************************
>>
>>
>>
>>
>>
>>
>> --
>>
>> Stephen Hearn, Metadata Strategist
>>
>> Cataloging, Metadata, & Digitization Services
>>
>> University of Minnesota Libraries
>>
>> 170A Wilson Library (office)
>>
>> 160 Wilson Library (mail)
>>
>> 309 19th Avenue South
>>
>> Minneapolis, MN 55455
>>
>> Ph: 612-625-2328
>>
>> Fx: 612-625-3428
>>
>> ORCID: 0000-0002-3590-1242
>>
>
>
> --
> Stephen Hearn, Metadata Strategist
> Cataloging, Metadata, & Digitization Services
> University of Minnesota Libraries
> 170A Wilson Library (office)
> 160 Wilson Library (mail)
> 309 19th Avenue South
> Minneapolis, MN 55455
> Ph: 612-625-2328
> Fx: 612-625-3428
> ORCID: 0000-0002-3590-1242
>
--
Bob Talbott
Hebraica cataloger/Curatorial Assistant to the Judaica Collection
UC Berkeley
250 Moffitt
Berkeley, CA 94720
Lue musaraba shu biburueada Bilgameshe nam habadabkure.
