[Heb-NACO] 264 in RDA - publisher not identified

Fri Oct 25 11:22:02 EDT 2013

It does not show up on Stanford's FirstSearch either. 
This might be a bug at OCLC's end. You might test a few other records that use 264 instead of 260 and see if it is a recurring problem. 

----- Original Message -----

From: "Uri Kolodney" <kolodney at austin.utexas.edu> 
To: "Hebrew Name Authority Funnel" <heb-naco at lists.service.ohio-state.edu> 
Sent: Friday, October 25, 2013 7:29:15 AM 
Subject: Re: [Heb-NACO] 264 in RDA - publisher not identified 

Thank you. I wonder, does it show on your end on FirstSearch? 

Uri 

From: heb-naco-bounces at lists.service.ohio-state.edu [mailto:heb-naco-bounces at lists.service.ohio-state.edu] On Behalf Of Manuel Frau-Cortes 
Sent: Friday, October 25, 2013 9:18 AM 
To: Hebrew Name Authority Funnel 
Subject: Re: [Heb-NACO] 264 in RDA - publisher not identified 

This may have to do with what your institution filters out on the public display of FirstSearch. You may want to talk with your systems persons. 

Neil M. Frau-Cortes 

Hebraica Cataloger 

McKeldin Library 

University of Maryland 
College Park, MD 20742 
Phone (301) 405-9337 

nfrau at umd.edu 

From: heb-naco-bounces at lists.service.ohio-state.edu [ mailto:heb-naco-bounces at lists.service.ohio-state.edu ] On Behalf Of Kolodney, Uri 
Sent: Friday, October 25, 2013 9:55 AM 
To: Hebrew Name Authority Funnel; Heidi G Lerner 
Subject: Re: [Heb-NACO] 264 in RDA - publisher not identified 

See for example 824522432. The Hebrew 264 does not display on the public view of OCLC (WorldCat). Once one adds an additional Hebrew 260, it does show up. So it means that the Hebrew 264 has some display compatibility issues, I think… 

From: heb-naco-bounces+kolodney=austin.utexas.edu at lists.service.ohio-state.edu [ mailto:heb-naco-bounces+kolodney=austin.utexas.edu at lists.service.ohio-state.edu ] On Behalf Of Kolodney, Uri 
Sent: Thursday, October 24, 2013 4:56 PM 
To: Heidi G Lerner 
Cc: Hebrew Name Authority Funnel 
Subject: Re: [Heb-NACO] 264 in RDA - publisher not identified 

I'm not at my desk at the moment, so will send an example tomorrow morning. 
Thanks, 
Uri 

Sent from my Windows Phone 

From: Heidi G Lerner 
Sent: ‎ 10/ ‎ 24/ ‎ 2013 4:49 PM 
To: Kolodney, Uri 
Cc: Hebrew Name Authority Funnel 
Subject: Re: [Heb-NACO] 264 in RDA - publisher not identified 

Hi, my comments were made with regard to OCLC Connnexion and not the WorldCat view. I am not sure why things would be different though. 

From: "Uri Kolodney" < kolodney at austin.utexas.edu > 
To: "Heidi G Lerner" < lerner at stanford.edu >, "Hebrew Name Authority Funnel" < heb-naco at lists.service.ohio-state.edu > 
Sent: Thursday, October 24, 2013 2:38:06 PM 
Subject: RE: [Heb-NACO] 264 in RDA - publisher not identified 

Great, thanks! 
Now, regarding the instance of records with both 264 and 260 - is this because of display issues? I noticed that the transliterated 264 does not show up on WorldCat view. Is this so? 
Thanks, 
Uri 

Sent from my Windows Phone 

From: Heidi G Lerner 
Sent: ‎ 10/ ‎ 24/ ‎ 2013 4:26 PM 
To: Hebrew Name Authority Funnel 
Cc: Kolodney, Uri 
Subject: Re: [Heb-NACO] 264 in RDA - publisher not identified 

Hi Uri, 

We use [publisher not identified] in both romanized and Hebrew script fields. RDA 1.4 tell us which following elements to record in the language and script in which they appear on the sources from which they are taken. It then goes on to tell us "Record all other elements (including notes) in a language and script, or languages and scripts, preferred by the agency creating the data.".Generally, most North American libraries and all PCC libraries use English as the preferred language. 

Best, Heidi 

From: "Uri Kolodney" < kolodney at austin.utexas.edu > 
To: "Hebrew Name Authority Funnel" < heb-naco at lists.service.ohio-state.edu > 
Sent: Thursday, October 24, 2013 12:57:35 PM 
Subject: [Heb-NACO] 264 in RDA - publisher not identified 

Could someone please help me clarify the correct form of the sub-field b in 264 in RDA when there is no publisher? 

I see different versions and managed to get confused. 

I know it should be [publisher not identified], but what do I put in the transliterated field? The same wording in English? Or maybe the good old “s.n.” or maybe “motsi la-or eno mezuheh” ? J 

Thanks, 

Uri 

________________________________________________________ 

Uri Kolodney 

Hebrew & Jewish Studies Librarian / Acting Librarian for Russian & Slavic Studies 

University of Texas Libraries 

The University of Texas at Austin 

PCL 2.300 | Mail Code S5440 | PO Box P Austin, TX 78713-8916 

Phone: 512-495-4399 | Fax: 512-495-4410 kolodney at austin.utexas.edu 

www.lib.utexas.edu/subject/judaica/index.html 

From: heb-naco-bounces+kolodney=austin.utexas.edu at lists.service.ohio-state.edu [ mailto:heb-naco-bounces+kolodney=austin.utexas.edu at lists.service.ohio-state.edu ] On Behalf Of dascheide at gmail.com 
Sent: Wednesday, August 21, 2013 7:08 PM 
To: Hebrew Name Authority Funnel 
Cc: heb-naco at lists.service.ohio-state.edu 
Subject: Re: [Heb-NACO] Keter Aram Tsoveh 

Aleppo codex 

Sent from my iPhone 

On Aug 21, 2013, at 6:38 PM, Judith Zupnick < judiezup at msn.com > wrote: 

What/who is the Keter Aram Tsoveh? And should it be capitalized (in the Romanization} as follows? : 

" 'al pi ha-mesorah Keter Aram Tsoveh" 

Thanks! 

<blockquote>

_______________________________________________ 
Heb-naco mailing list 
Heb-naco at lists.service.ohio-state.edu 
https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco 

</blockquote>

_______________________________________________ 
Heb-naco mailing list 
Heb-naco at lists.service.ohio-state.edu 
https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco 

_______________________________________________ 
Heb-naco mailing list 
Heb-naco at lists.service.ohio-state.edu 
https://lists.service.ohio-state.edu/mailman/listinfo/heb-naco 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/heb-naco/attachments/20131025/9f9eebbe/attachment.html>