Re: [Heb-NACO] To see - לראות

2023-11-25 Thread Joan Biella via Heb-naco
You’re right you’re right!—Joan

On Fri, Nov 24, 2023 at 11:27 PM Galron, Joseph via Heb-naco <
heb-naco@lists.osu.edu> wrote:

> Colleagues,
>
> I believe (I hope I am not wrong) that לראות (to see)  needs to be
> romanized as Li-re’ot and not Lir’ot. Am I wrong?
>
>
>
> Yossi
>
>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] Date Status (DtSt) and Dates in the fixed field

2022-11-15 Thread Joan Biella via Heb-naco
I’d like to repeat and stress Jasmin’s endorsement of a “consistent,
standard practice.”  Certain questions like this one arise over and over
again in Hebraica cataloging, and can be settled only by adopting a
standard—there is one, generally used by the largest libraries.  Teach the
standard.  Let cataloging be a big tent, open to all who can follow
standard practices no matter how shallow or deep their backgrounds in
particular fields like Hebraica.

Joan, possibly tending toward curmudgeonhood in Northern California.


On Tue, Nov 15, 2022 at 9:19 AM Shinohara, Jasmin via Heb-naco <
heb-naco@lists.osu.edu> wrote:

> Hi, Cliff, Your thought about probability is interesting. Nevertheless,
> our documented practice has been to use the earlier of the two possible
> dates for both the call no. date and fixed field date. Please see the
> Classification and Shelflisting
>
> Hi, Cliff,
>
>
>
> Your thought about probability is interesting. Nevertheless, our
> documented practice has been to use the earlier of the two possible dates
> for both the call no. date and fixed field date. Please see the 
> *Classification
> and Shelflisting Manual*, G140 (Dates)
> ,
> where a list of examples is given:
>
>
>
> *2012*
>
> *use* *2012*
>
> *MMX*
>
> *use* *2010*
>
> *[2011]*
>
> *use* *2011*
>
> *[2008?]*
>
> *use* *2008*
>
> *[1995 or 1996]*
>
> *use* *1995*
>
> *1980-2013*
>
> *use* *1980*
>
> *MMI-MMII*
>
> *use* *2001*
>
> *MCMXCI-2010*
>
> *use* *1991*
>
> *1980-[2013]*
>
> *use* *1980*
>
> *[1965]-2005*
>
> *use* *1965*
>
> *[1965-2005]*
>
> *use* *1965*
>
> *[not before March 1, 1800]*
>
> *use* *1800*
>
> *[not after April 23, 1700]*
>
> *use* *1700*
>
> *[between May 1,1801 and May 2, 1805]*
>
> *use* *1801*
>
> *[between 1700 and 1799]*
>
> *use* *1700z [if corporate body, use 1700] *
>
> *[between 1700 and 1799?]*
>
> *use* *1700z [if corporate body, use 1700] *
>
> *[between 1990 and 1999]*
>
> *use* *1990z [if corporate body, use 1990] *
>
> *[between 1990 and 1999?]*
>
> *use* *1990z [if corporate body, use 1990] *
>
> *[between 1950 and 2012?]*
>
> *use* *1950z [if corporate body, use 1950] *
>
>
>
> For fixed field dates, per my email from yesterday, please see example in
> *BFAS* on DtSt
> .
>
>
>
>
> Probability notwithstanding, a unified, consistent practice serves our
> users better. Please let me know if there are further questions.
>
>
>
> Thanks and kol tuv, Jasmin
>
>
>
> *From:* Heb-naco  *On Behalf Of *Cliff
> Miller via Heb-naco
> *Sent:* Tuesday, November 15, 2022 10:20 AM
> *To:* Gottschalk, Haim ; Hebrew Name Authority Funnel <
> heb-naco@lists.osu.edu>; Miller, Caroline 
> *Subject:* Re: [Heb-NACO] Date Status (DtSt) and Dates in the fixed field
>
>
>
> Dear Colleagues, I’m working remotely so I cannot check any references at
> my Seminary Library desk. As I recall the single date “s” is to be used
> when the date is certain or probable. 5783 might be any of 9 months of 2023
>
> Dear Colleagues,
>
> I’m working remotely so I cannot check any references at my Seminary
> Library desk.
>
> As I recall the single date “s” is to be used when the date is certain or
> probable.
>
> 5783 might be any of 9 months of 2023 or any of 3 months of 2022.
>
> When the odds are 3 to 1 of the later date, I think we are justified in
> using the later date and not both years as questionable.
>
> Is not 9 months out of 12 a high probability?
>
> Thank you.
>
> Clifford Miller, speaking for myself and not for
>
> Library of the Jewish Theological Seminary
>
>
>
> *From:* Heb-naco  *On
> Behalf Of *Gottschalk, Haim via Heb-naco
> *Sent:* Monday, November 14, 2022 5:25 PM
> *To:* Miller, Caroline ; Hebrew Name Authority
> Funnel 
> *Subject:* Re: [Heb-NACO] Date Status (DtSt) and Dates in the fixed field
>
>
>
> *CAUTION: This email originated from outside JTSA. Do not click links or
> open attachments unless you recognize the sender and know the content is
> safe. *
>
> Hi Caroline, Haim here. What I do is use the first date as THE date with
> the DtSt: s. Granted we don’t know fully if the date is 2012 or 2013, but
> this is the practice we do. The questionable date is when there is no date
> whatsoever in
>
> Hi Caroline,
>
>
>
> Haim here.
>
>
>
> What I do is use the first date as THE date with the DtSt: s. Granted we
> don’t know fully if the date is 2012 or 2013, but this is the practice we
> do. The questionable date is when there is no date whatsoever in the book
> and we have to surmise when it was published. I do use a detailed date
> (DtSt: e) when I have the month available, such as erev Rosh Hodesh Nisan,
> plus year.
>
>
>
> I hope that 

Re: [Heb-NACO] ALA/LC romanization(?) for Aramic as used in Babylonian Talmud, Talmud Yerushalmi, midrashitc texts

2022-11-14 Thread Joan Biella via Heb-naco
In my time at LC we never tackled this, mostly because we almost never
needed it.  Personally, I always turned to Jastrow first, but this practice
was not codified.

Joan Biella

On Mon, Nov 14, 2022 at 9:17 AM Heidi G Lerner via Heb-naco <
heb-naco@lists.osu.edu> wrote:

> Dear safranim, Is it possible that in our years of developing romanization
> schemata for several Jewish languages written in Hebrew script we have not
> codified any guidelines for Aramaic used in talmudic and
> midrashic/aggadic/cabalistic texts?
> Dear safranim,
>
> Is it possible that in our years of developing romanization schemata for
> several Jewish languages written in Hebrew script we have not codified any
> guidelines for Aramaic used in talmudic and midrashic/aggadic/cabalistic
> texts?
>
> Up until now my practice has been to follow the ALA/LC table for Hebrew.
> If I don't find a particular Aramaic word in  Even-Shoshan or Alkalay, i
> turn to Jastrow,  Sefaria, Comprehensive Aramaic Lexicon (covers all
> dialects).
>
> What have the rest of you been doing? Should a preferred  method be
> codified?
>
> I look forward to learning your practices have been.
>
> Best, Heidi
>
>
>
> Heidi G. Lerner
>
> Metadata Librarian for Hebraica and Judaica Emerita, Stanford University
> Libraries
>
>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] Romanization question (מתווה)

2022-07-28 Thread Joan Biella via Heb-naco
Chiming in late, I agree that we should follow Even-Shoshan, but adding
this to the Miss Romanization page is a good idea.  —Joan

On Thu, Jul 28, 2022 at 11:32 AM Rachel Simon via Heb-naco <
heb-naco@lists.osu.edu> wrote:

> I asked mainly because LC had both forms. So, maybe enter it the
> romanization wiki From: Heb-naco  princeton@lists.osu.edu> On Behalf Of Barry Dov Walfish via Heb-naco
> Sent: ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
>
> I asked mainly because LC had both forms. So, maybe enter it the
> romanization wiki
>
>
>
> *From:* Heb-naco  *On
> Behalf Of *Barry Dov Walfish via Heb-naco
> *Sent:* Thursday, July 28, 2022 1:58 PM
> *To:* Galron, Joseph ; Hebrew Name Authority Funnel <
> heb-naco@lists.osu.edu>
> *Subject:* Re: [Heb-NACO] Romanization question (מתווה)
>
>
>
> Rav-milim (and Morfix) have mitveh. There are other examples of -eh words
> (mikreh, mikveh, mikhreh), so that's neither here nor there. My old ES also
> has mitvah. As already mentioned, mitveh seems to be more common in spoken
> Hebrew, but
>
> Rav-milim (and Morfix) have mitveh. There are other examples of -eh words
> (mikreh, mikveh, mikhreh),
>
> so that's neither here nor there.
>
> My old ES also has mitvah.
>
> As already mentioned, mitveh seems to be more common in spoken Hebrew,
> but we need to follow our designated authorities.
>
> Barry
>
>
>
> On Thu, Jul 28, 2022 at 12:55 PM Galron, Joseph via Heb-naco <
> heb-naco@lists.osu.edu> wrote:
>
> As Roger wrote, I also know about Mitveh, but it might be wrong, and
> should be Mitvah, the same has Mehvah מחווה
>
>
>
> Milon Ariel ha-makif, has it as Mitvah
>
>
>
> Yossi
>
>
>
>
>
>
>
> *From:* Heb-naco *On Behalf Of *Kohn, Roger via Heb-naco
> *Sent:* Thursday, July 28, 2022 11:58 AM
> *To:* 'Rachel Simon' ; 'Hebrew Name Authority
> Funnel' 
> *Subject:* [Heb-NACO] To Rachel S. (PUL) re.: Romanization question (מתווה
> )
>
>
>
> --- Hi Rachel, Yes, ES2000 has “mitvah”, but all what I hear on Israeli
> radio is “mitveh” … All the best, .-r. From: Heb-naco <
> heb-naco-boun...@lists.osu.edu> ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
> ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
> ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
>
> ---
>
>
>
> Hi Rachel,
>
>
>
> Yes, ES2000 has “mitvah”, but all what I hear on Israeli radio is “mitveh”
> …
>
>
>
> All the best,
>
>
>
> .-r.
>
>
>
> *From:* Heb-naco  *On Behalf Of *Rachel
> Simon via Heb-naco
> *Sent:* Thursday, July 28, 2022 9:26 AM
> *To:* Hebrew Name Authority Funnel 
> *Subject:* [Heb-NACO] Romanization question
>
>
>
> For מתווה : is it “mitvah” or “mitveh” ?? My ES has “mitvah”, but LC has
> both. Thanks, Rachel ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
> ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
> ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
> ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
> ‍ ‍ ‍ ‍
>
> For  מתווה  : is it “mitvah” or “mitveh” ?? My ES has “mitvah”, but LC
> has both.
>
>
>
> Thanks,
>
>
>
> Rachel
>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
> 
>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] romanization question

2022-02-05 Thread Joan Biella via Heb-naco
My birthday is December 21st.  That gives us some time to plan
International Romanization Day.

Joan, still suffering from broken wrist and, probably, impaired judgment
from medications.


On Sat, Feb 5, 2022 at 4:44 PM Shinohara, Jasmin 
wrote:

> I second the motion! 
>
>
>
> *From:* Heb-naco  *On Behalf Of *Joan
> Biella via Heb-naco
> *Sent:* Thursday, February 3, 2022 10:04 PM
> *To:* Hebrew Name Authority Funnel ; Nancy <
> s...@hawaii.edu>
> *Subject:* Re: [Heb-NACO] romanization question
>
>
>
> Maybe we should declare a holiday to celebrate romanization!
>
>
>
> Joan
>
>
>
>
>
>
>
> On Thu, Feb 3, 2022 at 12:45 PM Nancy via Heb-naco 
> wrote:
>
> Hi, Rachel!
> Are you still romanizing? How are you?
>
>
> Nancy
>
> On 2/3/2022 5:33 AM, Rachel Simon via Heb-naco wrote:
>
> How is  כאילו   romanized? I saw several ways.
>
>
>
> Thanks,
>
>
>
> Rachel
>
>
>
> ___
>
> Heb-naco mailing list
>
> Heb-naco@lists.osu.edu
>
> https://lists.osu.edu/mailman/listinfo/heb-naco 
> <https://urldefense.com/v3/__https:/lists.osu.edu/mailman/listinfo/heb-naco__;!!IBzWLUs!DChdj-ceRT0w1O31_-QvN-EUyNHExIruxIeCDhCuXl4VaL5o622oNoM3OR90q6QWmbvz$>
>
>
>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
> <https://urldefense.com/v3/__https:/lists.osu.edu/mailman/listinfo/heb-naco__;!!IBzWLUs!DChdj-ceRT0w1O31_-QvN-EUyNHExIruxIeCDhCuXl4VaL5o622oNoM3OR90q6QWmbvz$>
>
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] romanization question

2022-02-05 Thread Joan Biella via Heb-naco
Maybe we should declare a holiday to celebrate romanization!

Joan



On Thu, Feb 3, 2022 at 12:45 PM Nancy via Heb-naco 
wrote:

> Hi, Rachel!
> Are you still romanizing? How are you?
>
> Nancy
>
> On 2/3/2022 5:33 AM, Rachel Simon via Heb-naco wrote:
>
> How is  כאילו   romanized? I saw several ways.
>
>
>
> Thanks,
>
>
>
> Rachel
>
> ___
> Heb-naco mailing 
> listheb-n...@lists.osu.eduhttps://lists.osu.edu/mailman/listinfo/heb-naco
>
>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] Birth date

2019-10-29 Thread Joan Biella via Heb-naco
We used to say, if a heading is not WRONG, don’t change it, because of the
incalculable number of physical catalog cards that would have to be
manually changed to match.  Perhaps in the digital era we should forget
this?

Joan


On Tue, Oct 29, 2019 at 10:06 AM Rachel Simon via Heb-naco <
heb-naco@lists.osu.edu> wrote:

> If when creating a NAR we had only the Hebrew year (and thus had to give x
> or y Gregorian years) but later got the exact birth date, can we fix the
> NAR to give only the appropriate year?
>
>
>
> Thanks,
>
>
>
> Rachel
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] בגלל

2019-09-19 Thread Joan Biella via Heb-naco
Jasmine writes:

 בגלל has a direct entry, so I’d think it would be romanized biglal (NOT
bigelal because as a whole word, the sheva would be considered merahef,
ignored in romanization), but the entry also says “see גלל”. So which is
it: Biglal or Bi-gelal?

Doesn't HCM say, more or less, "If Even-Shoshan gives both, use THE MORE
ANALYTICAL FORM"--that is, the form with the hyphen?  This is done, in the
same way as we write "Yerushalayim," so the 2nd part of the word will be
searchable.  Not that I expect people who want to search "biglal" will
search "gelal" and expect to find it, but people wanting "Yerushalayim"
will find "bi-Yerushalayim" also.  And so that all catalogers will romanize
these things the same way, after having once looked them up in the
dictionary.

Joan


On Wed, Sep 18, 2019 at 1:29 PM Yossi Galron via Heb-naco <
heb-naco@lists.osu.edu> wrote:

> Bi-melot ...
>
> On Wed, Sep 18, 2019, 22:28 Marlene Schiffman via Heb-naco <
> heb-naco@lists.osu.edu> wrote:
>
>> We have a title that uses this word: Zeʼev Z'aboṭinsḳi, ha-ish u-mishnato
>> : \b (bi-melot meʼah shanah le-huladto)
>>
>>
>>
>> Marlene Schiffman
>>
>> Gottesman Library Technical Services
>>
>> Yeshiva University
>>
>> 500 West 185th Street
>>
>> New York, NY 10033
>>
>>
>>
>> 646 592-4276 (direct)
>>
>> 646 592-4100 (general office)
>>
>>
>>
>> *From:* Heb-naco  *On
>> Behalf Of *Abend-David,Ilana via Heb-naco
>> *Sent:* Thursday, February 07, 2019 1:07 PM
>> *To:* Galron, Joseph ; Hebrew Name Authority Funnel <
>> heb-naco@lists.osu.edu>
>> *Subject:* Re: [Heb-NACO] בגלל
>>
>>
>>
>> If so how would you transliterate במלאות 25 שנה  ? Would this be correct
>> bi-melo'ut ?
>>
>>
>>
>> *From:* Heb-naco  *On Behalf Of *Galron,
>> Joseph via Heb-naco
>> *Sent:* Thursday, February 7, 2019 12:52 PM
>> *To:* Hebrew Name Authority Funnel 
>> *Subject:* Re: [Heb-NACO] בגלל
>>
>>
>>
>> It is “dangerous” going to Biglal or Bishvil – tomorrow we will say: If
>> it is Bishvil so why not change it to Shvil
>>
>> We also Romanize בירושלים  to “Bi-Yerushalayim” and not to “Birushalayim”
>>
>>
>>
>> Yossi
>>
>>
>>
>>
>>
>>
>>
>> *From:* Heb-naco  *On Behalf Of *Shinohara,
>> Jasmin via Heb-naco
>> *Sent:* Thursday, February 7, 2019 12:31 PM
>> *To:* Gottschalk, Haim ; 'Hebrew Name Authority Funnel' <
>> heb-naco@lists.osu.edu>
>> *Subject:* Re: [Heb-NACO] בגלל
>>
>>
>>
>> Hi, Haim, bi-gelal would be correct if the ב is considered a prefix to
>> the word גלל. But since there is a direct entry for the word as a whole,
>> I’m asking if we should romanize it as a whole word instead of as a
>> compound word.
>>
>>
>>
>> Thanks, Jasmin
>>
>>
>>
>> *From:* Gottschalk, Haim [mailto:h...@loc.gov ]
>> *Sent:* Thursday, February 07, 2019 12:24 PM
>> *To:* Shinohara, Jasmin; 'Hebrew Name Authority Funnel'
>> *Subject:* RE: בגלל
>>
>>
>>
>> I think it should be “biglal” and not “bi-gelal” because of the sheva
>> being treat as a sheva nach (which is how it is in the Alcalay).  This is
>> in my humble opinion.
>>
>>
>>
>> ~Haim
>>
>>
>>
>> *From:* Heb-naco  *On Behalf Of *Shinohara,
>> Jasmin via Heb-naco
>> *Sent:* Thursday, February 07, 2019 11:00 AM
>> *To:* Hebrew Name Authority Funnel 
>> *Subject:* [Heb-NACO] בגלל
>>
>>
>>
>> Hello Collective Wisdom, please remind me: if there’s an entry in E-Sh.,
>> even if it ends with a “see also”, is that sufficient justification for
>> romanizing the word as a word as opposed to a compound? E.g. בגלל has a
>> direct entry, so I’d think it would be romanized biglal (NOT bigelal
>> because as a whole word, the sheva would be considered merahef, ignored in
>> romanization), but the entry also says “see גלל”. So which is it: Biglal
>> or Bi-gelal?
>>
>>
>>
>> Thanks, Jasmin
>>
>>
>>
>>
>>
>> ---
>>
>> Jasmin Shinohara
>>
>> Hebraica Cataloging Librarian
>>
>> University of Pennsylvania
>>
>> Van Pelt-Dietrich Library Center
>>
>> 3420 Walnut Street
>>
>> Philadelphia, PA 19104-6206
>>
>> T. 215-746-6397
>>
>> jsh...@upenn.edu
>>
>>
>> ___
>> Heb-naco mailing list
>> Heb-naco@lists.osu.edu
>> https://lists.osu.edu/mailman/listinfo/heb-naco
>>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] פלסטינים

2019-05-17 Thread Joan Biella via Heb-naco
Dear friends,

This kind of question comes up regularly--probably with all romanized
languages with a policy of following the advice of a particular,
"authoritative" dictionary.  There are two choices:  (1) advise catalogers
to follow the dictionary slavishly, adding additional access (246s and the
like) with other likely romanizations; or (2) create a list of "exceptions"
to the rule of following the dictionary.  At least when I was an active
cataloger, Hebrew followed the first option, Arabic the second.  There is a
list of approved Arabic romanizations which contradict the dictionary, and
catalogers must be aware of it and of the need to check it regularly.

The policy of following the dictionary slavishly, even when what it
suggests is ridiculous, standardizes the process of cataloging and the
process of searching--catalogers know that if they search the
dictionary-approved spelling, they will find all instances of the word they
want (in theory, anyway).  Of course the patrons don't know what the
dictionary says and why they don't find what they're looking for--hence the
need for alternative access points.  Patrons also won't know what
non-dictionary form catalogers have chosen (if they follow Option 2 above),
so they'll always be at sea unless alternative access is provided.

Neither system is foolproof or easy.  At least Option 1 makes life easier
for catalogers.  Option 2 leads to a free-for-all.

I don't see how we can please everybody, except by giving lots and lots of
246s.  So give them!

My two agorot.

Joan Biella

On Fri, May 17, 2019 at 5:26 AM Yossi Galron via Heb-naco <
heb-naco@lists.osu.edu> wrote:

> and what about פלשתינאים?
> Is it also with an F?
>
> Yossi
>
>
> On Fri, May 17, 2019, 08:22 Kuperman, Aaron via Heb-naco <
> heb-naco@lists.osu.edu> wrote:
>
>> Do users actually say that?   I don’t recall Hebrew speakers pronouncing
>> that initial letter as other than a “P”?
>>
>>
>>
>> Aaron Kuperman, LC Law Cataloging Section.
>>
>> This is not an official communication from my employer
>>
>>
>>
>>
>>
>> *From:* Heb-naco  *On Behalf Of *Shinohara,
>> Jasmin via Heb-naco
>> *Sent:* Thursday, May 16, 2019 10:44 AM
>> *To:* Gerstein, Nahid ; Taub, Jeremiah Aaron ;
>> Hebrew Name Authority Funnel 
>> *Subject:* Re: [Heb-NACO] פלסטינים
>>
>>
>>
>> Yes, I should have been more clear in my original email. Thank you for
>> asking. Per E.-Sh., all words that are פלסטינ* are Falasṭin* (where * =
>> wildcard). So it’s Falasṭini (masculine), Falasṭinit (feminine),
>> Falasṭinim (masc. plural), Falasṭiniyot (fem. plural). The name of land
>> is Falasṭin.
>>
>>
>>
>> Thanks again and kol ṭuv, Jasmin
>>
>>
>> --
>>
>> *From:* Gerstein, Nahid 
>> *Sent:* Thursday, May 16, 2019 7:26 AM
>> *To:* Taub, Jeremiah Aaron; Shinohara, Jasmin
>> *Subject:* RE: פלסטינים
>>
>>
>>
>> Jasmin,
>>
>> I am working on changing the romaniztion for this word.
>>
>> How about “Palestin?”  or “Palestini?”
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Nahid
>>
>>
>>
>> *From:* Taub, Jeremiah Aaron 
>> *Sent:* Wednesday, May 15, 2019 4:23 PM
>> *To:* Gerstein, Nahid 
>> *Subject:* FW: פלסטינים
>>
>>
>>
>> Nahid,
>>
>>
>>
>> Please see Jasmin’s correction below. Could you make these corrections in
>> the LC database? If it’s too many, I could ask Yisrael to split this with
>> you.
>>
>>
>>
>> Thanks so much,
>>
>> A
>>
>>
>>
>> *From:* Shinohara, Jasmin 
>> *Sent:* Thursday, May 09, 2019 5:15 PM
>> *To:* Hebrew Name Authority Funnel (heb-naco@lists.osu.edu) <
>> heb-naco@lists.osu.edu>
>> *Cc:* Taub, Jeremiah Aaron 
>> *Subject:* פלסטינים
>>
>>
>>
>> Hi, just a friendly notice that, per E-Sh., the above is romanized
>> Falasṭinim, not Palesṭinim. (It is in the Romanization FAQchart
>> .)
>>
>>
>>
>> I don’t know if it’s a changed romanization, but we all have clean-up to
>> do in our respective databases…
>>
>>
>>
>> Kol tuv, Jasmin
>>
>>
>>
>> ---
>>
>> Jasmin Shinohara
>>
>> Hebraica Cataloging Librarian
>>
>> University of Pennsylvania
>>
>> Van Pelt-Dietrich Library Center
>>
>> 3420 Walnut Street
>>
>> Philadelphia, PA 19104-6206
>>
>> T. 215-746-6397
>>
>> jsh...@upenn.edu
>>
>>
>> ___
>> Heb-naco mailing list
>> Heb-naco@lists.osu.edu
>> https://lists.osu.edu/mailman/listinfo/heb-naco
>>
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
>
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco


Re: [Heb-NACO] geo. subdivision for Eruv

2019-02-28 Thread Joan Biella via Heb-naco
Perhaps no one thought there was “literary warrant” before.  Make a case to the 
policy folks!

Joan

Sent from my iPad

> On Feb 28, 2019, at 2:09 PM, Shinohara, Jasmin via Heb-naco 
>  wrote:
> 
> Hi, the LCSH term Eruv is not geographically sub-dividable, while the LCSH 
> term Mikvah is. Do we know why the discrepancy? Is it possible to change the 
> designation for Eruv?
>  
> Thanks, Jasmin
>  
> ---
> Jasmin Shinohara
> Hebraica Cataloging Librarian
> University of Pennsylvania
> Van Pelt-Dietrich Library Center
> 3420 Walnut Street
> Philadelphia, PA 19104-6206
> T. 215-746-6397
> jsh...@upenn.edu
>  
> ___
> Heb-naco mailing list
> Heb-naco@lists.osu.edu
> https://lists.osu.edu/mailman/listinfo/heb-naco
___
Heb-naco mailing list
Heb-naco@lists.osu.edu
https://lists.osu.edu/mailman/listinfo/heb-naco