[Heb-NACO] 264 bracketed dates: = or that is?

Wed Jul 20 16:05:04 EDT 2016

Sorry I should not have used brackets. I should have used quotes to set it apart or italiiczed it. No brackets would be used in a catalog record.

Heidi G. Lerner

Metadata Librarian for Hebraica and Judaica

Metadata Dept.

Stanford University Libraries

Stanford, CA 94305-6004

ph: 650-725-9953

fax: 650-725-1120

e-mail: lerner at stanford.edu

________________________________
From: Shinohara, Jasmin <jshino at pobox.upenn.edu>
Sent: Wednesday, July 20, 2016 12:56 PM
To: Hebrew Name Authority Funnel
Cc: Heidi G Lerner
Subject: RE: [Heb-NACO] 264 bracketed dates: = or that is?

Heidi, if it's a date of publication, why is it in brackets?

"For example if you have a date of publication in the Hebrew calendar followed by a date in the  Gregorian calendar in the same source of information you will record it as [Hebrew calendar=Gregorian calendar]"

Jasmin

From: Heb-naco [mailto:heb-naco-bounces at lists.osu.edu] On Behalf Of Heidi G Lerner
Sent: Wednesday, July 20, 2016 3:29 PM
To: Hebrew Name Authority Funnel; rtalbott at library.berkeley.edu
Subject: Re: [Heb-NACO] 264 bracketed dates: = or that is?

Hi Bob,

I looked at the manual under the rule you cited and I do not see that we actually addressed the issue so I will go to the Toolkit.

LC-PCC PS 2.8.6.3 tells us to follow the optional addition:

If the date as it appears on the resource is represented in different calendars, record the dates in the order indicated by the sequence, layout, or typography of the dates on the source of information.

For example if you have a date of publication in the Hebrew calendar followed by a date in the  Gregorian calendar in the same source of information you will record it as [Hebrew calendar=Gregorian calendar] (or vice versa depending on the order of dates).

Also, if you have a Hebrew date of publication appearing in one source of information and a Gregorian date of publication appearing in another source of information you would follow the same practice.

However if you have a Hebrew date of publication on one source and a Gregorian date of copyright or manufacture you would not record theses as parallel dates of publication.

You would record the Hebrew date of publication witout brackets and the inferred date of publication based on the Gregorian date of copyright or manufacture in brackets.

I hope that this clarifies the situation.

Best, Heidi

Heidi G. Lerner

Metadata Librarian for Hebraica and Judaica

Metadata Dept.

Stanford University Libraries

Stanford, CA 94305-6004

ph: 650-725-9953

fax: 650-725-1120

e-mail: lerner at stanford.edu<mailto:lerner at stanford.edu>

________________________________

From: Heb-naco <heb-naco-bounces at lists.osu.edu<mailto:heb-naco-bounces at lists.osu.edu>> on behalf of Robert M. TALBOTT <rtalbott at library.berkeley.edu<mailto:rtalbott at library.berkeley.edu>>
Sent: Wednesday, July 20, 2016 11:04 AM
To: Hebrew Name Authority Funnel
Subject: [Heb-NACO] 264 bracketed dates: = or that is?

Folks:

I've been seeing an awful lot of bracketed dates utilizing the equals
(=) sign, to wit:

where only a copyright of 774 and a copyright of 2014 are present on
the t.p. verso

$c [774 = 2014]

As I read the HCM (2.8.6, pp. 47-48), it appears that the equals sign
is only used in instances where there are two firm dates that are
unbracketed.  Again, as I understand it, inside brackets, the phrase
"that is" is used.

where only a copyright of 774 and a copyright of 2014 are present on
the publication

$c [774, that is, 2014]

Am I wrong? Have things changed?

Thanks

Bob
--
Bob Talbott

Principal cataloger/Hebraica cataloger

UC Berkeley

250 Moffitt

Berkeley, CA 94720

I'm just mad about Saffron
_______________________________________________
Heb-naco mailing list
Heb-naco at lists.osu.edu<mailto:Heb-naco at lists.osu.edu>
https://lists.osu.edu/mailman/listinfo/heb-naco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/heb-naco/attachments/20160720/90e253d9/attachment-0001.html>