[Heb-NACO] $c ha-Kohen shenanigans

[Heidi G Lerner]

The addition of ha-Kohen, ha-Leṿi, Kohen, and sometimes Kohen and Kats to a name entered under surname and including a forename     was permitted in AACR2 under 22.12 (see G uidelines for Rabbinic Names entered under Forenames ( https://lib.stanford.edu/files/Rabbinic%20Forenames.pdf )).  I believe that this same rule is carried over in RDA in rule 9.19.1.2. 

Best, Heidi 

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

From: "Robert Talbott" <rtalbott at library.berkeley.edu> 
To: "Hebrew Name Authority Funnel" <heb-naco at lists.service.ohio-state.edu> 
Sent: Wednesday, August 8, 2012 9:17:22 AM 
Subject: [Heb-NACO] $c ha-Kohen shenanigans 

An open question to Joan and Heidi: 

Ladies, I'm flummoxed with yet more $c bafflement.  To wit, I have a 
book here edited by one ha-Rav Elyashiv ha-Kohen Kaplun.  I've chased 
the weasel around the $c ha-Rav mulberry bush a few times, and I'm 
pretty that $c ha-Kohen runs into the same sort of descriptive 
dissonance in that it violates RDA9.4.1.8 : the AACR2 style heading one 
would expect, Kaplun, Elyashiv, $c ha-Kohen can't be used because the 
rule cited says that religious titles can only occur with auth. access 
points beginning with forename. 

Assuming that we aren't going to go with the unstated "Hakohen" option 
(Kaplun, Elyashiv Hakohen ; xref: Hakohen Kaplun, Elyashiv) and that 
ignoring it (Kaplun, Elyashiv; 378 $q Elyashiv ha-Kohen) is out of the 
question, how should we proceed? 

Vexed, 

Bob 
_______________________________________________ 
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/20120808/77d76684/attachment.html>