Re: Cataloging Workshop-Save the date, February 9, 2011
Joan and I have submitted a proposal to present this topic at the conference. I believe that we are on the draft schedule. Best, Heidi - Original Message - From: Jasmin Nof j...@umd.edu To: heb-naco@lists.acs.ohio-state.edu Sent: Monday, January 10, 2011 11:41:52 AM Subject: Re: Cataloging Workshop-Save the date, February 9, 2011 Oh, how I wish I could come! Too bad the timing isn't great and the funding isn't there for me to do so... But here's hoping that we'll hear more from these speakers at AJL Annual! (For those of us who are lucky enough to at least be able to make it there...) Jasmin Jasmin Nof Judaica and Hebraica Cataloger 2200 McKeldin Library University of Maryland College Park, MD 20742 301-405-9337 j...@umd.edu On 1/10/2011 12:45 PM, Rita Lifton wrote: Save the date, Wednesday, February 9, 2011, in the PM, for the 2011 Cataloging Workshop of the New York Metropolitan Area Chapter of the Association of Jewish Libraries, which will be held at Temple Emanu-El, 5 th Avenue at 65th Street, NYC. Program: RDA and the RDA Test: Hebraica Perspectives – Dr. Joan Biella, Senior Bibliographic Specialist and Acting Section Head of the Israel/Judaica Cataloging Section, Library of Congress Religion Genre/Form Revision Project – Barbara Kemmis, Director of Member Services, and Erica Treesh, Database Manager for Authority Control, American Theological Library Association Full details about the 2011 Cataloging Workshop will be available soon – make sure to save the date and plan to join us. -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [Fwd: [PCCLIST] Timeline for new LCGFT coding]
- Forwarded Message - From: Joanna Dyla jd...@stanford.edu To: Emma ekoro...@stanford.edu, Greta gdegr...@stanford.edu, Heidi Lerner ler...@stanford.edu, Inna iguda...@stanford.edu, Jane z...@stanford.edu, Kay kt...@stanford.edu, Margaret H margaret.hug...@stanford.edu, Casey cmul...@stanford.edu, Robert rrohr...@stanford.edu Cc: Ai-Lin Yang aya...@stanford.edu, Margaret L m...@stanford.edu Sent: Tuesday, January 4, 2011 2:49:07 PM Subject: [Fwd: [PCCLIST] Timeline for new LCGFT coding] Catalogers, Please see the announcement of the forthcoming revision of the genre/form authority records. --Joanna [From the LC web page] The new genre/form authority records will have an LCCN prefix of “gf”(e.g., gf201015), and the then-deprecated “sh” LCCN (e.g., sh2010025010) will be retained in MARC 21 field 010$z. The new MARC coding in the authority records will be as follows: 008/11: z (“Other”) 040 $f lcgft After the new authority records are distributed, all LCGFT terms used in bibliographic records should be coded: 655 -7 $a [Term]. $2 lcgft Original Message Subject: [PCCLIST] Timeline for new LCGFT coding Date: Tue, 4 Jan 2011 11:15:23 -0500 From: Young, Janis j...@loc.gov Reply-To: Program for Cooperative Cataloging pccl...@listserv.loc.gov To: pccl...@listserv.loc.gov [This message is being sent to multiple discussion groups. Please excuse the duplication.] Since 2007 the Library of Congress’ Policy and Standards Division (PSD) has been developing genre/form terms, which are distinct from subject headings because they describe what something is as opposed to what it is about . To date, PSD has approved genre/form terms in four areas: moving images, sound recordings, cartographic resources, and law. Terms in three other disciplines, music, literature, and religion, are also in development. As a first step toward formally separating the genre/form terms from LC subject headings list, PSD titled the new thesaurus the Library of Congress Genre/Form Terms for Library and Archival Materials ( LCGFT ) in June 2010. No earlier than March 1, 2011 , PSD will revise the LCCNs and MARC 21 coding of the genre/form authority records to indicate that they are LCGFT terms, not LCSH headings. To accomplish this, all existing genre/form authority records with an sh prefix in the LC Control Number (LCCN) will be cancelled and replacement records for them will be issued simultaneously. For the full announcement of these plans, including a description of the new coding, please see http://www.loc.gov/catdir/cpso/gf_lccn.html . The firm date for the reissuing of the records will be announced when it has been determined. Questions or comments on these plans or on the genre/form projects in general may be addressed to Janis L. Young, LC’s genre/form coordinator, at j...@loc.gov . Further information on LC's genre/form projects can be found at http://www.loc.gov/catdir/cpso/genreformgeneral.html . Janis L. Young Policy and Standards Division Library of Congress -- Joanna K. Dyla Head, Metadata Development Unit Metadata Department Stanford University Libraries 650-723-2529 jd...@stanford.edu -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] End of US RDA Test: LC policy during interim period
FYI - Forwarded Message - From: Judith Kuhagen j...@loc.gov To: pccl...@listserv.loc.gov Sent: Wednesday, December 22, 2010 9:12:56 AM Subject: [PCCLIST] End of US RDA Test: LC policy during interim period [Sending to multiple lists; please excuse duplication] End of US RDA Test: LC policy during interim period The Library of Congress will not create original RDA bibliographic records and generally will not create RDA authority records during the interim period after the US RDA Test ends on December 31, 2010 through the announcement of any implementation decision. Some US RDA Test participants who are PCC NACO participants will continue to create RDA bibliographic records after Dec. 31, 2010. Other non-US RDA Test participants are creating RDA records now and may/will continue to create RDA records. RDA records will be used by LC during this interim period in the following categories: -- CIP verification; -- Records created by other libraries, vendors, etc., for materials being added to LC’s collections. In both categories, the authorized access points may be all RDA forms, all AACR2 forms, or a combination of AACR2 and RDA forms; name authority records may or may not exist in the LC/NACO Authority File. LC’s internal procedures are posted at http://www.loc.gov/catdir/cpso/existing_RDA_records.pdf Send questions to lchelp4...@loc.gov. -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] Dept. to Department -- Library of Congress decision
- Forwarded Message - From: Judith Kuhagen j...@loc.gov To: pccl...@listserv.loc.gov Sent: Tuesday, December 21, 2010 10:38:13 AM Subject: [PCCLIST] Dept. to Department -- Library of Congress decision [Forwarding to multiple lists; please excuse duplication] The Library of Congress will not undertake changing headings with the abbreviation “Dept.” to the fuller form at this time. Between August 20-October 1, 2010, the Library requested comments from the library community on changing “Dept.” to “Department” to follow the longstanding AACR2 provision (which is also incorporated into RDA: Resource Description and Access ) of not abbreviating department in headings unless it is abbreviated by the body on the resource from which the name has been taken. The few comments received by the Policy and Standards Division, Library of Congress, via email showed a clear preference for making this change but the limited response did not constitute a mandate. In addition those opposed to the change had solid reasons for not undertaking the change at this time. Consequently, the Library’s Policy and Standards Division will NOT proceed with implementing the change now. The issue will be reviewed again, following a decision regarding implementation of RDA. Questions may be sent to: Policy and Standards Division Email: pol...@loc.gov -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
question re cutter
Dear group, I am working on a catalog of children's art from East and West Jerusalem. I will class it in N352.2 and then cutter it for region or country. My question is if I may cutter J4 for Jerusalem? Thanks, Heidi -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: Source for Sephardi/Mizrahi names
Dear Rachel, In my opinion this is a very reasonable and valid request. I think that it would be a very worthwhile suggestion to be brought to the attention of the AJL RS Cataloging Committee. As you may be aware, the guidelines for establishing Hebrew names in RDA have been modified a little. During the test period a number Library of Congress Policy Statements (LCPSs), i.e, policy decisions for the Library's participants in the RDA Test, have been posted for use, if desired, in the library community. There is an LCPS for RDA 9.2.2.5.3 which includes guidelines very similar to the current LCRI for establishing the preferred form for persons with Hebrew and Yiddish names. However the current LCPS is not identical to the LCRI and the list of approved resources has been expanded to include Wikipedia, Linkedin and Facebook. These LCPSs may be modified during and after the test period. As official testers Joan and I have been in contact and consulting with the LC RDA coordinators as we work through the application of RDA to the idiosyncrasies and issues unique to Hebraica cataloging. If other colleagues and the AJL Cataloging Committee are in favor of adopting the Encyclopedia of Jews in the Islamic World as an additional valid resource we could share that recommendation with the LCPS staff. Sincerely, Heidi - Original Message - From: Rachel Simon rsi...@princeton.edu To: heb-naco@lists.acs.ohio-state.edu Sent: Monday, November 29, 2010 12:27:06 PM Subject: Source for Sephardi/Mizrahi names Since many Sephardi/Mizrahi names are not included in Enc. Jud., can the authoritative source for them be the new Encyclopedia of Jews in the Islamic World (Brill, 2010)? Rachel -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCTRNG] FW: New NACO Node: SkyRiver Technology Solutions
- Forwarded Message - From: Carolyn Sturtevant c...@loc.gov To: pcct...@listserv.loc.gov Sent: Tuesday, November 16, 2010 2:02:30 PM Subject: [PCCTRNG] FW: New NACO Node: SkyRiver Technology Solutions Forwarded on behalf of PCC Chair. Please excuse multiple postings. The PCC welcomes a new NACO Node* member, SkyRiver Technology Solutions. Name authority records contributed through SkyRiver will carry the prefix “ns.” The Library of Congress has been working with all NACO nodes to prepare for the new prefix in LC NACO Authority File (LCNAF) records. The first NACO records from SkyRiver will enter the shared database on November 17, 2010. SkyRiver will use MARC organization codes as identifiers for PCC partners who contribute through their service. SkyRiver’s own records will appear under the MARC code CaEvSKY. Please direct questions about this new node to SkyRiver Technology Solutions . For information on NACO, please email: n...@loc.gov . *The Program for Cooperative Cataloging (PCC) uses a File Transfer Protocol (FTP) process to enable record exchanges among NACO partner institutions. The Library of Congress and its “NACO Nodes” do direct FTP exchanges. NACO libraries, numbering in the hundreds, contribute records to the LC NACO Authority File via the NACO nodes. John Riemer Chair, Program for Cooperative Cataloging Head, UCLA Library Cataloging Metadata Center Kinross South 11020 Kinross Avenue Box 957230 (campus mail code 723011) Los Angeles, CA 90095-7230 +1 310.825.2901 voice +1 310.794.9357 fax jrie...@library.ucla.edu Leslie Straus President, SkyRiver Technology Solutions PO Box 8217 Emeryville, CA 94662 510-520-8084 voice 510-450-6352 fax les...@theskyriver.com -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: Moving on from LC
Dear Lenore, May you have much success and derive great satisfaction from your new position. I am very happy for you. Warmly, Heidi - Original Message - From: Lenore Bell l...@loc.gov To: heb-naco@lists.acs.ohio-state.edu heb-naco@lists.acs.ohio-state.edu Sent: Friday, November 5, 2010 3:37:31 PM Subject: Moving on from LC Dear Colleagues, This note is to let you know that as of Nov. 8, I will be starting work in my new position at the US Holocaust Memorial Museum. I look forward to our continued collaboration and consultation. I will resubscribe to the list when I get my new email account, and will let you all know how to contact me directly. I'm pleased to report that Aaron Taub will be the Acting Section Head of LC's Israel and Judaica Section through November and December 2010. Best wishes to you all! Lenore -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Funnel work during RDA Test Period (Oct. 1-Dec. 31 2010
Dear Hebraica NACO Funnel amd Judaica SACO Funnel members, We (Joan Biella and Heidi Lerner) are among the group of staff who will participate in RDA testing Oct. 1-Dec. 31. Both LC and Stanford are official test partners. Although the details of the testing are still not completely known, we are certain that we will be extremely busy during this period creating and evaluating RDA records. Even now, we are heavily invested in learning to work with the RDA toolkit and and the accompanying LC policy statements. Without doubt, our time for NACO/SACO revision and consultation will be very limited. In the most extreme case we may be forced to announce that we will stop reviewing for the remainder of the test period. We will keep you apprised of any new developments or changes in work-flow. Thank you, Heidi and Joan Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Jewish police or Jewish police officers
Dear group, I am sending this query a second time in hopes to get some help in formulating a subject heading for Jewish police/Jewish police officers. I have seen in LCSH the following: African American police Christian police officers Gay police officers Lesbian police officers Police officers exists as a cross-reference to Police I think that I should propose Jewish police officers since we already have Christian police officers but I would like some help understanding why we have Afican American police but Christian police officers. Thank you, Heidi -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Jewish police offers or Jewish police
Dear group, I would like to propose a subject heading: Jewish police officers There is an extant subject heading for Christian police officers but under Police officers exist as a cross reference to Police Is Jewish police officers correct or should it be Jewish police Thanks, Heidi -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Model of Jerusalem - possible subject heading?
Dear Group, I am cataloging a work on Degem Yerushalayim (Model of Jerusalem, currently located at the Israel Musuem, formerly at the Holyland Hotel). I am looking at SHM H1334 to see if it includes an entity such as this in its guidelines for establishing and assigning names of buildings and other structures as subject headings and there does not seem to be any. I have found at least two other books that talk about the model: Pictorial guide to the model of ancient Jerusalem at the time of the Second Temple in the grounds of the Holyland Hotel, Jerusalem Israel / Michael Avi-Yonah (2001) A short guide to the model of ancient Jerusalem. Is there any warrant for establishing the model in the subject heading file? Thanks, Heidi -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: meeting time revision?
3:00 Sunday works for me. I think that meeting at 10:00 PM on Tuesday after a full day of programming and a long final banquet at the end of a full convention is not a good idea. I know that I will be exhausted and not eager to doo something so late, especially work-related. Also no other committees are scheduled at that time so I dont think that we should be an exception. Thanks, Heidi - Original Message - From: Jasmin Nof j...@umd.edu To: heb-naco@lists.acs.ohio-state.edu Sent: Tuesday, June 29, 2010 12:57:44 PM Subject: meeting time revision? A request has been made to start the Sunday meeting time at 3 instead of 3:30 in order to minimize the need for us to meet a second time Tuesday night. Does that work for all of you? Please let me know asap. Thanks, Jasmin -- Jasmin Nof Judaica and Hebraica Cataloger 2200 McKeldin Library University of Maryland College Park, MD 20742 301-405-9337 j...@umd.edu -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [Fwd: [PCCLIST] Changes to Subject Headings for Cooking and Cookbooks]
fyi Original Message Subject: [PCCLIST] Changes to Subject Headings for Cooking and Cookbooks Date: Tue, 22 Jun 2010 14:11:11 -0400 From: Policy and Standards Division pol...@loc.gov Reply-To: Program for Cooperative Cataloging pccl...@listserv.loc.gov To: pccl...@listserv.loc.gov *Subject Headings for Cooking and Cookbooks* June 22, 2010 The Library of Congress issued the list of the new and revised subject headings for materials on cooking and cookbooks on June 22, 2010 (http://www.loc.gov/aba/cataloging/subject/weeklylists/). These new and revised headings will be distributed beginning with the CDS distribution file vol. 25, issue 24 dated June 14 and will continue until completed. The revision of /Subject Headings Manual/ (/SHM/) H 1475, “Cooking and Cookbooks,” is forthcoming and will be posted as a PDF file on the public Cataloging and Acquisitions Web site ( http://www.loc.gov/aba/* *). It will also be included in /SHM/ Update Number 2 of 2010, which will be distributed in the fall. The word “cookery” has been changed to “cooking” in approximately 800 subject headings (e.g., *Cooking*, *Cooking (Butter)*, *Cooking for the sick*, *Aztec cooking*, *Cooking, American--Southwestern style).* A topical subject heading for *Cookbooks* and a genre/form heading for *Cookbooks* have also been approved, and are available for use. Most of the Children’s Subject Headings in the form *Cookery--[Ingredient] *have been cancelled in favor of the adult heading *Cooking ([Ingredient]*). However, three of those headings have been retained and revised: *Cooking (Buffets)*, *Cooking (Garnishes)*, and *Cooking (Natural foods)*. In cases where reference structure for a heading has been changed but the heading itself has not, the heading was omitted from the list. For example, the headings *Brunches*, *Comfort food*, and *Tortillas *had the broader term *Cookery*, which has been changed to *Cooking*. None of these three headings appear on the Weekly List. The references on approximately 500 headings have been changed. Every effort will be taken to expeditiously change the old form of subject headings in bibliographic records to the new form during the next few months. Questions or concerns may be directed to: Libby Dechman Senior Cataloging Policy Specialist Email: e...@loc.gov -- Joanna K. Dyla Head, Metadata Development Unit Metadata Department Stanford University Libraries 650-723-2529 jd...@stanford.edu -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Chage of address for NACO Hebraica Funnel Page
Please note that the adderss of the NACO Hebraica Funnel website has changed. The new address is: http://lib.stanford.edu/naco-hebraica-funnel/naco-hebraica-funnel-home-page Thank you, Heidi Lerner (Coordinator, NACO Hebraica Funnel) -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: RDA Testing
im a tester too but we dont begin training until july how come you guys are so far ahead of us - Original Message - From: Joan Biella j...@loc.gov To: heb-naco@lists.acs.ohio-state.edu Sent: Wednesday, May 26, 2010 2:08:44 PM Subject: RE: RDA Testing I'm an RDA tester at LC--will begin training (at least introduction to RDA Toolkit) tomorrow, with lots more to come. Of course I'll report anything that seems useful and/or pertinent to us to the group, but truly useful things may not come up till after the three months of training which precede the three months of actual testing, which are to begin in October. (And don't forget that the official position is that LC may not adopt RDA in the end ... the future is shrouded in mystery, as always.) Joan From: owner-heb-n...@lists.acs.ohio-state.edu [owner-heb-n...@lists.acs.ohio-state.edu] On Behalf Of Caroline Miller [crmil...@library.ucla.edu] Sent: Tuesday, May 25, 2010 5:37 PM To: Biella, Joan; heb-naco@lists.acs.ohio-state.edu Subject: RDA Testing Heb-NACOers, I know that some of your institutions are doing RDA testing. Are any of you going to be personally involved? It will be interesting to hear how it works with Hebrew script. I’m sure that those of us who are not testing would love to hear reports (very unofficial, of course!). Caroline Caroline R. Miller Mellon Rare Book Project Director Head, Authority/Database Maintenance Section UCLA Library Cataloging Metadata Center BOX 957230 11020 Kinross Ave. Los Angeles, CA 90095-7230 E-mail: crmil...@library.ucla.edumailto:crmil...@library.ucla.edu Phone: (310) 825-4446 Fax: (310) 794-9357 -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: RDA Testing
Stanford will be testing officially and all origiinal catalogers will be working with materials of the same type as their regular workflow. So I assume that I will be using Hebrew materials as part of my assignmen. As of now I have no real details. Heidi - Original Message - From: Caroline Miller crmil...@library.ucla.edu To: heb-naco@lists.acs.ohio-state.edu heb-naco@lists.acs.ohio-state.edu Sent: Tuesday, May 25, 2010 2:37:34 PM Subject: RDA Testing Heb-NACOers, I know that some of your institutions are doing RDA testing. Are any of you going to be personally involved? It will be interesting to hear how it works with Hebrew script. I’m sure that those of us who are not testing would love to hear reports (very unofficial, of course!). Caroline Caroline R. Miller Mellon Rare Book Project Director Head, Authority/Database Maintenance Section UCLA Library Cataloging Metadata Center BOX 957230 11020 Kinross Ave. Los Angeles, CA 90095-7230 E-mail: crmil...@library.ucla.edu Phone: (310) 825-4446 Fax: (310) 794-9357 -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] Clarification: LCRIs and LCPSs
- Forwarded Message - From: Regina S. Koo r...@gpo.gov To: pccl...@listserv.loc.gov Sent: Friday, May 7, 2010 6:09:55 AM Subject: [PCCLIST] Clarification: LCRIs and LCPSs [This clarification is being cross-posted to multiple lists. Please excuse the duplication.] Apologies if the original wording caused confusion. All the policy decisions/documents we've been sharing with others have been developed just for the RDA Test later this year. If the results of the Test determine that LC should not implement RDA, the documents will be rescinded/revised/reinstated as appropriate. - Judy Kuhagen = = = = Library of Congress Policy Statements (LCPSs) are being developed by the Policy and Standards Division (PSD) to offer LC test participants guidance on LC policy in the use of the new cataloging code, Resource Description and Access (RDA). The LCPSs are also being made available for the information of other testers and interested parties. Official launch of this new publication will coincide with the release of RDA by the American Library Association (ALA) scheduled for June 2010. The intention is to place links within the online RDA Toolkit from the RDA instruction to the specific LCPS that applies and from one LCPS to another as appropriate. Following the official launch, a period of instruction and testing will begin. LCPSs also will be widely available beyond the RDA Toolkit. LCPSs will be fully integrated into Cataloger's Desktop. Free PDF versions will be available in May via links on the PSD website to the Cataloging Distribution Service's (CDS) free PDF download site. If there is sufficient demand, CDS will review appropriate print options. Just as the Library of Congress Rule Interpretations (LCRI) offered library catalogers advice for AACR2, LCPSs will provide information for RDA instructions to explain LC practice for the US RDA Test. LCPSs will be more focused, covering fewer topics and leaving more to cataloger's judgment than the LCRIs. LCRIs will remain available for institutions that continue to catalog following the Anglo-American Cataloguing Rules, Second Edition (AACR2). LCRIs will continue to be updated through December 2010 and the free PDF versions will remain on the CDS free download site as needed by CDS customers. CDS will continue to sell printed LCRIs until the supply is exhausted. For information on CDS products, contact Peter Seligman, p...@loc.gov For information on LCPSs, contact the Policy and Standards Division, lchelp4...@loc.gov = = = = Judith A. Kuhagen Senior Descriptive Cataloging Policy Specialist Policy and Standards Division Library of Congress Washington, D.C. 20540-4262 202-707-4381 202-707-6629 (fax) Regina S. Koo x31119 -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: [SACOLIST] Moving image genre/form hierarchies
- Original Message - From: Janis Young j...@loc.gov To: sacol...@listserv.loc.gov Sent: Wednesday, April 28, 2010 7:21:41 AM GMT -08:00 US/Canada Pacific Subject: [SACOLIST] Moving image genre/form hierarchies [This message is being cross-posted to multiple lists. Please excuse the duplication.] On January 8, 2010 the Policy and Standards Division (PSD) of the Library of Congress issued a discussion paper entitled “Proposed Revision to the Hierarchies of Moving Image Genre/Form Headings,” which broached the idea of explicitly placing many of the LC moving image genre/form headings into either a fiction or a nonfiction hierarchy. PSD would like to thank everyone who provided comments on this issue. PSD has decided not to move forward on its proposal at this time. An explanation of the rationale for this decision is available on the Library of Congress’ web site at http://www.loc.gov/catdir/cpso/movingimagehierarchiesdecision.pdf. Additional information on the genre/form projects at the Library of Congress can be found on PSD’s genre/form web page, http://www.loc.gov/catdir/cpso/genreformgeneral.html. The web page includes a timeline, an extensive FAQ, reports, discussion papers, and announcements. Questions and comments on the projects may be addressed to Janis L. Young, LC’s genre/form coordinator, at j...@loc.gov. ~~ Janis L. Young Policy and Standards Division Library of Congress ~~ -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: Benn
Dear Barry, As a NACO cataloger you may go ahead and correct a NAR that has been incorrectly established. In this case you would invoke LCRI 22.1B Persons Treated in the Same Manner as Authors In determining the name by which a person is commonly known, the rule distinguishes between authors and others. For purposes of simplification, generally use the approach applied to authors also to 1) persons who work in a context other than that of writing text, e.g., a painter, a sculptor, a performer whose name appears in a formal statement found in the item (e.g., statement of responsibility) 2) composers, regardless of whether their names appear in a statement of responsibility or not. So you would establish the heading based on the form of the heading that appears in the chief source of information. Because his catalogs appear in two or more languages you would need to look at A2 and LCRI 22.3b1 and make your decision on the form based on those. I would be happy to take a look at it when you are done. Best, Heidi 010 n 50007194 040 DLC ǂb eng ǂc DLC ǂd DLC ǂd OCoLC 1001 Benn, Bencjon, ǂd 1905- 4001 Rabinovitch, Bencjon, ǂd 1905- 4000 Benn, ǂd 1905- 4001 בען, בנציון, ǂd ־1905 667 Machine-derived non-Latin script reference project. 667 Non-Latin script reference not evaluated. 670 His Ben, 1948. - Original Message - From: Barry Walfish barry.walf...@utoronto.ca To: mail=heb-n...@lists.acs.ohio-state.edu heb-naco@lists.acs.ohio-state.edu Sent: Friday, April 23, 2010 10:20:29 AM GMT -08:00 US/Canada Pacific Subject: Benn Dear Safranim, This is for Joan or someone else at LC who deals with Name headings. Would it be possible to get the heading Benn, Bencjon, 1905- changed to Benn, 1905-1989. The Jewish artist in question, Benn, originally from Poland, used the name Benn throughout his career. I don't believe there is a single publication or work of art by him that has the name Bencjon on it. The EJ2 simply lists him as Benn. Since he's an artist, other reference works may be called into play, but it should be obvious that the LC form is not the commonly used form of the name, and its use is perpetuating this distortion of the artist's public persona. Thanks, Barry Barry Dov Walfish, Ph.D. Judaica Specialist University of Toronto Libraries Toronto, ON M5S 1A5 Canada -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [SACOLIST] New feature on SACO website
- Forwarded Message - From: Paul Edwin Frank pfr...@loc.gov To: sacol...@listserv.loc.gov Sent: Wednesday, April 21, 2010 1:08:18 PM GMT -08:00 US/Canada Pacific Subject: [SACOLIST] New feature on SACO website SACO website users: The Coop Section has added a new feature to the SACO website. It is a link to the most recent Approved Marked-Up Subject List. At the weekly subject editorial meeting, all changes to proposals on the tentative weekly list are recorded by PSD staff. An annotated marked-up list is made after the meeting, showing the changes that were made to the tentative list. PSD recently made the marked-up lists available to LC catalogers, and now Coop is making them available to SACO members as well. More information is available by clicking on the What's This? button following the caption Most Recent Approved Marked-Up List on the SACO website: With the posting of the Approved “Marked-Up” Lists on the SACO website, PSD and Coop are beginning a new service to SACO members who submit LCSH proposals and perform subject analysis. The Approved “Marked-Up” List is a PDF copy of the tentative weekly list that has been amended in red to include the changes to subject proposals that were made at the editorial meeting for that list. PSD and Coop hope that this amended list will clearly illustrate the kinds of changes that are necessary to subject proposals, and will assist individuals in doing subject analysis and in making subject proposals in the future. The “Marked-Up” Lists will be posted weekly. Please direct any questions or feedback to s...@loc.gov Paul Frank Paul Frank Cooperative Programs Section Cooperative and Instructional Programs Division Library of Congress 202-707-1570 pfr...@loc.gov -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] Punctuation used with $3 and $x in 260, 490, 8XX Fields: PCC guidelines
- Forwarded Message - From: Les Hawkins l...@loc.gov To: pccl...@listserv.loc.gov Sent: Monday, March 29, 2010 7:41:47 AM GMT -08:00 US/Canada Pacific Subject: [PCCLIST] Punctuation used with $3 and $x in 260, 490, 8XX Fields: PCC guidelines PCC guidelines for punctuation associated with newly implemented subfields have been posted: http://www.loc.gov/catdir/cpso/punctuation.pdf. The guidelines were developed in cooperation with the PCC Standing Committee on Standards, OCLC staff, and LC's Policy and Standards Division. There are links to the document from LC's Cataloging and Acquisitions web page: http://www.loc.gov/aba/cataloging/policy/#marc and the PCC home page: http://www.loc.gov/catdir/pcc/ Les Hawkins CONSER Coordinator Library of Congress v. 202 707-5185 l...@loc.gov -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: [ha-Safran]: Cataloguing Judaeo-German
p.s. The guidlines for romanization of words of Hebrew-Aramaic origin that appear in Ladino works and retain their originai spellign in the ALA/LC romaniztion table for Ladino is: Words of Hebrew-Aramaic origin usually retain their traditional spellings in Ladino. Such words are romanized according to the ALA/LC Hebrew romanization table. I would think that it is useful to follow this practice for German in Hebrew characters unless you have vocalization present. - Original Message - From: Heidi G Lerner ler...@stanford.edu To: v freedman v.freed...@ucl.ac.uk Cc: heb-naco heb-naco@lists.acs.ohio-state.edu Sent: Friday, March 5, 2010 7:47:22 AM GMT -08:00 US/Canada Pacific Subject: Re: [ha-Safran]: Cataloguing Judaeo-German Dear Vanessa, I will attempt to respond to the best of my knowledge to your query below. I am cc'ing the Heb-NACO list because that list includes the most active community in the U.S/Canada of Hebraica catalogers who adhere to AACR2rev., ALA/LC romanization tables ... [et al.]. The answer to your first question is that we would use the MARC language code for German [ger] and include a 546 note that something like In German [in Hebrew characters]. That being said, there has been no official statement on how to handle the vocalization but I am including the text of some guielines that were sent in an e-mail to the Heb-NACO group by Joan Biella (LC) in 1998 for romanizing languages other than Hebrew that are written in Hebrwew script. This was written as a response to a query re Ladino (before the establishment of an ALA/LC romaniztaion table) but I think that they would apply to works writteh in German in Hebrew characters as well. 1998: In romanizing languages other than Hebrew which are written in the Hebrew script, LC practice is always to romanize the consonants as Hebrew and represent the vowels as much as possible (given the limitations of the Hebrew script) like those of the language being romanized. Thus, we romanize the surname tet-vav-lamed-yod-dalet-alef-nun-vav as Toledano, not Tolidano. A convenient way of defining a consonant is as a character that appears when the text is unvocalized, and he meets this criterion. So in LC romanization of Ladino, he is romanized as h. The CSB is a pretty good guide to LC practice :-). Joan I am sure that other Hebraica catalogers have thoughts as well on this issue. Sincerely, Heidi Lerner p.s. In case you have not seen it, there is a document at the Hebrew Naco Funnel website that offers suggestions on how to distinguish Yiddish texts from those in Hebrew characters. - Original Message - From: Vanessa Freedman v.freed...@ucl.ac.uk To: hasaf...@lists.acs.ohio-state.edu Sent: Thursday, March 4, 2010 8:54:51 PM GMT -08:00 US/Canada Pacific Subject: [ha-Safran]: Cataloguing Judaeo-German Dear Safranim Are there any guidelines for cataloguing materials in Judaeo-German (ie German in Hebrew characters)? In particular, which MARC language code do you use? Do you Romanize as if it were Yiddish? What about Hebrew words? The particular work I'm cataloguing at the moment is Frenk's Mahaneh Yisra'el (National Library of Israel catalogue system no 2157265). I tried a search of Cataloger's Desktop and came up with various discussion from the AJL RS Cataloging Committee, but nothing definitive. Many thanks Vanessa Freedman Hebrew Jewish Studies Librarian UCL Library Services University College London Gower Street London WC1E 6BT Tel (Mon, Thurs, Fri): +44 (0) 20 7679 2598 (Internal ext. 32598) Tel (Tues and Weds): +44 (0) 20 7679 5163 (Internal ext. 25163) Fax: +44 (0) 20 7679 7373 E-mail: v.freed...@ucl.ac.uk Website: www.ucl.ac.uk/library **Please remember the environment and only print this if necessary** --- Messages and opinions expressed on Hasafran are those of the individual author and are not necessarily endorsed by the Association of Jewish Libraries (AJL) === Submissions for Ha-Safran, send to: hasaf...@osu.edu SUBscribing, SIGNOFF commands send to: Listproc @ lists.acs.ohio-state.edu Questions, problems, complaints, compliments;-) send to: galron.1 @ osu.edu Ha-Safran Archives: Current: http://www.mail-archive.com/hasafran%40lists.acs.ohio-state.edu/maillist.html History: http://www.mail-archive.com/hasafran%40lists.acs.ohio-state.edu/history.html AJL HomePage http://www.JewishLibraries.org -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120 -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: Hebrew equivalent for et al.
I think that the best to use would be [.va-a.herim] Heidi - Original Message - From: Sharon Benamou bena...@library.ucla.edu To: heb-naco@lists.acs.ohio-state.edu Sent: Tuesday, January 26, 2010 4:21:44 PM GMT -08:00 US/Canada Pacific Subject: Hebrew equivalent for et al. I am having a hard time finding Hebrew abbreviations. If I have a work of mixed responsibility and need to use an [et al.] in the 245, what is the equivalent to be used in the Hebrew script field? AACR2 has the abbreviation for un andere, but not for the Hebrew. Thanks, Sharon Sharon Benamou Hebraica/Judaica and Music Catalog Librarian Email: bena...@library.ucla.edu Phone: (310) 825-8642 Fax: (310) 794-9357 -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] 034 $2 codes can now be used
- Forwarded Message - From: Adam L. Schiff asch...@u.washington.edu To: pccl...@listserv.loc.gov Sent: Monday, December 14, 2009 1:09:45 PM GMT -08:00 US/Canada Pacific Subject: [PCCLIST] 034 $2 codes can now be used PCC folks, I sent this announcement out to our catalogers at UW, but thought it might also be helpful to other NACO folks out there, so I am sharing it with you too: For those of you who create name headings for geographic places (jurisdictions such as cities, towns, neighborhoods, provinces, etc.), since August we have been able to include coded geographic coordinates in MARC authority field 034. LC has now defined a number of source codes that can be used in 034 $2, and as of November 30, we can now use these codes in authority records. The list of codes can be found in the MARC Code List: PART VII: Other Sources under field 034: aadcg Australian Antarctic Data Centre Antarctic Gazetteer (Australian Antarctic Data Centre) acgms Atlas of Canada Gazetteer Map Service (Natural Resources Canada) ahcb Atlas of Historical County Boundaries (Newberry Library) bcgnis BC Geographical Names Information System (BCGNIS) (Government of British Columbia) cbf Cartographic Boundary Files (U.S. Census Bureau) ccga Cadre de classement geographique actuel (Paris: Bibliotheque Nationale) cga Composite Gazetteer of Antarctica (Scientific Committee on Antarctic Research (SCAR)) cgndb Canadian Geographical Names Database (Natural Resources Canada) cgotw Columbia Gazetteer of the World (Columbia University Press) esriarc ESRI ArcView gbos Ordnance Survey (Great Britain Ordnance Survey) geoapn GeoScience Australia Place Names (Geoscience Australia) geonames GeoNames geonet NGA GEOnet Names Server (GNS) (National Geospatial-Intelligence Agency) gettytgn Getty Thesaurus of Geographic Names Online (J. Paul Getty Trust) gnis Geographic Names Information System (GNIS) (United States Geological Survey, Board on Geographic Names) gnrnsw Geographical Names Register of NSW (New South Wales Government) goj Gazetteer of Japan (Geographical Survey Institute, and the Hydrographic and Oceanographic Department of the Japan Coast Guard) gooearth Google Earth gufn GEBCO Gazetteer of Undersea Feature Names (General Bathymetric Chart of the Oceans (GEBCO)) knab Kohanimeandmebaas (KNAB) (Eesti Keele Instituut) lwip Ramsar List of Wetlands of International Importance (Ramsar) mwgd Merriam-Webster's Geographical Dictionary (Springfield, MA: Merriam-Webster, Inc.) natmap The National Map-Boundaries (USGS) (U.S. Geological Survey) nsgn Nova Scotia Geographical Names (Province of Nova Scotia) nzggn New Zealand gazetteer of official geographic names (New Zealand Geographic Board Nga- Pou Taunaha o Aotearoa (NZGB)) peakbag Peakbagger.com pnosa PlaceNames Online: South Australian State Gazetteer (Government of South Australia, Department for Transport, Energy and Infrastructure) pwme Peakware World Mountain Encyclopedia (Peakware) rsd Ramsar Sites Database (Ramsar) sagns South African Geographical Names System (South African Department of Arts and Culture) volwrld Volcano World (Oregon Space Grant Consortium) vow Volcanoes of the World wdpa World Database on Protected Areas (World Commission on Protected Areas) whl World Heritage List (UNESCO) wld World Lakes Database (International Lake Environment Committee) other Other (A source other than one for which a unique code has been established) If you have a need for a code for some other source, it can be requested from LC Network Development and MARC Standards Office. Please note that for the time being, we are only putting 034 fields into geographic NAME authority records. Hopefully at some point in the future we can include them also in subject authority records for geographic features. If you want to see some real life examples: no2009199881 Chatrud (Iran) no2009137030 Grayland (Wash.) no2009137029 Tokeland (Wash.) ^^ Adam L. Schiff Principal Cataloger University of Washington Libraries Box 352900 Seattle, WA 98195-2900 (206) 543-8409 (206) 685-8782 fax asch...@u.washington.edu http://faculty.washington.edu/~aschiff ~~ -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] PCC Announces Implementation of BIBCO Standard Record, January 4, 2010
- Forwarded Message - From: Carolyn Ruth Sturtevant c...@loc.gov To: pccl...@listserv.loc.gov Sent: Tuesday, November 24, 2009 8:35:58 AM GMT -08:00 US/Canada Pacific Subject: [PCCLIST] PCC Announces Implementation of BIBCO Standard Record, January 4, 2010 Announcement Distributed to Cataloging Discussion Lists, November 24, 2009: The PCC Policy Committee (PoCo) has set January 4, 2010 as the implementation date for the BIBCO Standard Record (BSR) guidelines for printed books as outlined in the Final Report of the Task Group on BIBCO Standard Record Requirements. ● The PCC has posted the BSR guidelines, Metadata Application Profile (MAP), and a BSR FAQ to support implementation. Links appear below this announcement. ● Libraries contributing BSR records for printed books (excluding rare books) using the BIBCO Standard Record requirements will use the single encoding level “blank.” This replaces the use of BIBCO Full and Core standards for printed books. ● Libraries contributing BIBCO records for rare books, electronic books, and materials in non-book formats will continue to code full records “blank” and core records “4”, until BSR guidelines can be developed. ● Encoding level “4” will remain as a valid encoding level in OCLC for earlier BIBCO core records and for records not contributed as PCC printed book records in the future. It is understood that batch loading processes by libraries that catalog in local systems may result in some BIBCO core level records entering OCLC even after January 4, 2010. ● The Standing Committee on Standards is charged with developing BSR guidelines for rare books, for electronic books, and for monographs in non-book formats, in consultation with appropriate stakeholders. ● The Standing Committee on Training is charged with developing training materials aimed primarily at libraries joining the BIBCO program. PoCo extends its thanks to the Task Group members and liaisons: Members: Magda El-Sherbini, Ohio State University, Rebecca Malek-Wiley, Tulane University, Caroline Miller, University of California, Los Angeles, Louise Ratliff, University of California, Los Angeles, Carolyn Sturtevant, Coop, Library of Congress, Iris Wolley, Columbia University (coordinator) Liaisons: Joe Kiegel, Standing Committee on Standards, University of Washington, Rebecca Lubas, Standing Committee on Automation, University of New Mexico, Bob Wolverton, Standing Committee on Training, Mississippi State University The full BSR announcement: http://www.loc.gov/catdir/pcc/bibco/BSRAnnouncement.pdf The BSR Implementation document: http://www.loc.gov/catdir/pcc/bibco/BSR_ImplementationDoc.pdf The BSR FAQ: http://www.loc.gov/catdir/pcc/bibco/BSR_FAQ.pdf The Final Report of the TG on BIBCO Standard Record Requirements: http://www.loc.gov/catdir/pcc/bibco/BSR-Final-Report.pdf Posted on behalf of: Magda El-Sherbini, PCC Chair Associate Professor Head, Cataloging Department The Ohio State University Libraries el-sherbin...@osu.edu This announcement is approved for circulation to other discussion lists without prior notification. -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] The Virtual International Authority File (VIAF) and NACO
Please see below re Virtual International Authority File - Forwarded Message - From: Policy and Standards Division pol...@loc.gov To: pccl...@listserv.loc.gov Sent: Thursday, November 12, 2009 2:09:15 PM GMT -08:00 US/Canada Pacific Subject: [PCCLIST] The Virtual International Authority File (VIAF) and NACO Dear PCC catalogers: The Virtual International Authority File (VIAF) has moved to beta phase and is available for all to search at: http://viaf.org/ NACO catalogers are encouraged to use the VIAF as a reference source for indentifying persons and for resolving conflicts and disambiguation of personal names as needed. When new and useful information is found in VIAF it may be used and should be justified in a 670 citation. Suggested forms of citations include: 1) The name or code of the institution responsible for the information that is being used as viewed in the VIAF. 2) The date of the search (remember that as with other data files, this is a dynamic file subject to change, thus the date viewed/consulted is very important). 3) The information found, including the heading as found and any identifying attributes as well as useful variants to be added: 670 $a [Name of institution in VIAF], [date of search] $b (hdg.: ([name as found in the VIAF authority record or participating library data base; variants: (if any)]) FOR EXAMPLE 670 $ BNF in VIAF, Nov. 12, 2009 $b (hdg.: Gaulle , Charles de, 1890-1970) 670 $a Nat. Lib. Israel (Cyrillic), in VIAF, viewed Nov. 12, 2009 $b (hdg.: СЕРВАНТЕС СААВЕДРА, МИГЕЛЬ ДЕ, 1547-1616) When the VIAF is consulted and no information is found to disambiguate names: 675 $a VIAF, viewed 12 Nov. 2009. All information should be used in accordance with AACR2, the Library of Congress Rule Interpretations, and current NACO policies. Examples of VIAF citations will be added to the Descriptive Cataloging Manual (DCM) Z1, 670 section in the next update. posted by: Ana Lupe Cristán Policy and Standards Division Library of Congress, LA 310 Washington, DC 20540-4305 Tel.: 202.707.7921 Fax: 202.707.6629 Email: a...@loc.gov -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [PCCLIST] News from the Joint Steering Committee for Development of RDA
- Forwarded Message - From: Antony Robert David Franks a...@loc.gov To: pccl...@listserv.loc.gov Sent: Wednesday, June 24, 2009 7:17:36 AM GMT -08:00 US/Canada Pacific Subject: [PCCLIST] News from the Joint Steering Committee for Development of RDA **Apologies for cross-posting** News from the Joint Steering Committee for Development of RDA: * Finalization of RDA text The RDA text was handed to the co-publishers on schedule on 22 June. RDA is scheduled to be released at the end of November 2009. * New Chair Alan Danskin will be the JSC Chair from 1 July 2009. Danskin is the Metadata and Bibliographic Standards Coordinator at the British Library. During July, the JSC Secretariat will move to the British Library: jscsecret...@bl.uk * Web site The JSC Web site has moved to http://www.rda-jsc.org/ There are redirections in place from the old site to pages on the new site explaining the change. Nathalie Schulz Secretary, JSC n.sch...@btopenworld.com -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [CDSNews] Implementation of Authentication Code PCC and Change in Coding Practice of 008/39 Cataloging Source Code in CONSER
- Forwarded Message - From: Peter Selig Seligman p...@loc.gov To: cdsn...@listserv.loc.gov Sent: Monday, April 6, 2009 3:44:51 AM GMT -08:00 US/Canada Pacific Subject: [CDSNews] Implementation of Authentication Code PCC and Change in Coding Practice of 008/39 Cataloging Source Code in CONSER Records Library of Congress News from CDS Implementation of Authentication Code PCC and Change in Coding Practice of 008/39 Cataloging Source Code in CONSER Records 042 code pcc Beginning May 1, 2009 all CONSER institutions will use the authentication code pcc in place of codes lcd and lc in records newly authenticated and distributed as part of the CONSER Program. The code will be used in records for both serials and integrating resources. Codes lcd and lc will remain valid in pre-existing records and will not be systematically changed to pcc at this time. Other authentication codes will remain valid and some may be used in combination with code pcc, when appropriate. 008/39 code c Beginning May 1, 2009 CONSER practice for coding the 008/39 cataloging source will also change. CONSER institutions, other than CONSER national libraries, will use code c (defined as cooperative cataloging program) in all records - original or copy - authenticated and distributed as part of the CONSER Program, unless the record began as a record from a national library, in which case the source code will remain blank. Previously, authenticated records based on existing OCLC member copy were coded d (defined as other) by default. Code d on existing authenticated records remains valid and will not be systematically changed to code c in the near future. The coding practices of national bibliographic agencies participating in CONSER, (e.g. the Library of Congress, Library and Archives Canada, National Library of Medicine, and National Agricultural Library) will not change. These agencies will continue to use code blank in the 008/39 for original and previously unauthenticated OCLC records. Questions or concerns may be directed to: Policy and Standards Division email: pol...@loc.gov Library of Congress, Cataloging Distribution Service Washington, DC 20541-4910, USA Email: cdsi...@loc.gov Phone: (202) 707-6100, Fax: (202) 707-1334 http://www.loc.gov/cds -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Fwd: [CDSNews] SUBJECT HEADINGS MANUAL * AVAILABLE NO W
- Forwarded Message - From: Peter Selig Seligman p...@loc.gov To: cdsn...@listserv.loc.gov Sent: Friday, February 6, 2009 4:34:14 AM GMT -08:00 US/Canada Pacific Subject: [CDSNews] SUBJECT HEADINGS MANUAL * AVAILABLE NO W Library of Congress News from CDS SUBJECT HEADINGS MANUAL - AVAILABLE NOW The new Subject Headings Manual replaces the Subject Cataloging Manual: Subject Headings base text and all of its updates through February 2008. This new publication incorporates all of the content of the previous edition and has been updated through August 2008. Text is printed on loose-leaf pages and shipped to you with cover slip, spine, and tabs. Four volumes. Binders not included. The first of two 2009 updates will be available spring 2009. To order, visit www.loc.gov/cds/contact.html Price of base text: $100 in North America $140 outside North America Updates Two updates will be published each year. Price of updates $40 in North America $70 outside North America Library of Congress Cataloging Distribution Service Washington DC 20541-4912 USA Email: cdsi...@loc.gov Phone: (202) 707-6100 Fax: (202) 707-1334 http://www.loc.gov/cds/ -- Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Stanford University Libraries Stanford, CA 94305-6004 e-mail: ler...@stanford.edu ph: 650-725-9953 fax: 650-725-1120
Re: help with subject analysis
Dear Lenore, This is helpful. I will look into your suggestion. Thank you very much, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Lenore Bell [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Wednesday, October 15, 2008 3:49 PM Subject: Re: help with subject analysis Hi Heidi, I'm not familar with the concept, but from the definition you provided, the heading Vows (Jewish law) would be appropriate, and could be doubled with Children (Jewish law). You might develop a more specific heading that addresses the issue of minors and the age of legal competence. I would recommend consulting Aaron Kuperman. I hope this is some help. Lenore (wearing her new hat!) Lenore Bell Section Head, Israel Judaica Section Asian and Middle Eastern Division Library of Congress (202) 707-7313 [EMAIL PROTECTED] Heidi Lerner [EMAIL PROTECTED] 10/15/2008 2:45 PM Dear Group, I am cataloging a book that deals with: Din mufla ha-samukh le-ish. I have found on the web a definition of this prinicple with is in the Talmud: dictating that an eleven-year-old girl or twelve-year-old boy can issue a binding vow so long as they have the basic understanding of the concept. Would I use Vows--Jewish law Any help that can be provided will be appreciated. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Metadata Development Unit Metadata Dept. Stanford University Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax: 650-725-1120
Fw: [SACOLIST] CPSO's genre/form report available
fyi - Heidi e-mail: [EMAIL PROTECTED] - Original Message - From: Janis Young [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 14, 2008 8:17 PM Subject: [SACOLIST] CPSO's genre/form report available [Message cross-posted to various lists. Please excuse the duplication.] In early 2007 the Cataloging Policy and Support Office (CPSO) of the Library of Congress initiated a project to create authority records for genre/form headings (MARC tag 155), which indicate what a work is, as opposed to what it is about. The first discipline undertaken was that of moving images (films, television programs, and video recordings), and was accomplished in cooperation with the Moving Image, Broadcasting, and Recorded Sound Division (MBRS). The first 70 or so moving image genre/form authority records (MARC tag 155) were approved in September 2007, and there are currently almost 400 headings available for use. The second project undertaken, also in cooperation with MBRS, was to create radio program genre/form headings. The first of these authority records was approved in May 2008. This past Tuesday members of CPSO presented a report on the moving image genre/form project to LC managers. The report — explains the function of genre/form headings, including the impact that they have on both cataloging operations and end-user searching; — reviews the history of genre/form headings in MARC format and at LC over the last decade; — explains the logic of choosing moving image headings as the experimental group and the principles and policies that CPSO developed as the project progressed; and, — recommends the expansion of genre/form headings beyond moving images and radio programs into such disciplines as law, music, literature, cartography, and religion. The report was approved by LC management and has been posted on CPSO's web site at http://www.loc.gov/catdir/cpso/movimgenre.html. Specific information on development and implementation strategies will be released as they are developed. Questions about the genre/form projects may be addressed to CPSO in care of Janis Young at [EMAIL PROTECTED]
Re: Oral torah
I think that it would be a great idea for you and daniel to work on it butcan't really say since i am on vaction. what i do for funnel submissions is to have you fill out the email form for the subject proposal, fax it to me, i review and get back to you with comments, when we have finalized the proposal you send it via the web form with a note in the comment field Route to Henry Lefkowitz, judaica SACO funnel, send me a copy and use your naco funnel marc organization code in the 040 i will be back from vacation on july20 best, heidi Quoting Dickel, Geraldine [EMAIL PROTECTED]: I am cataloging a dissertation on oral torah in the writings of R. Zadok ha-Kohen of Lublin (Torah shebe-al peh be-kitve R. Tsadoḳ Hakohen mi-Lublin / me-et Amirah Liver). I think that a subject heading specific to oral torah would be appropriate for this title. There is a subject heading: Tradition (Judaism), which has a cross reference Oral law (Judaism) but this subject heading seems overly broad to be considered a synonym for oral Torah. Should someone (e.g. Daniel Lovins?) decouple these concepts through a SACO proposal for either Oral Torah or Oral Law? Jerry Anne Dickel Yale University Library
Fw: [OCLC-NON-LATIN] Have you noticed an increased number of controlled headings in WorldCat?
Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Patton,Glenn [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 1:53 PM Subject: [OCLC-NON-LATIN] Have you noticed an increased number of controlled headings in WorldCat? Automated processing is now being used to identify, modify, and control specific types of personal name headings in WorldCat bibliographic records. This processing, based on data used to build WorldCat Identities (http://orlabs.oclc.org/Identities/) and developed by Thom Hickey, Chief Scientist in the OCLC Office of Programs and Research, is projected to control more than 26,000,000 headings over the next few weeks. In this phase of processing, personal name headings that consist of more than a single subfield and that match the established form or a reference in the authority record are being updated (if necessary); the heading is then controlled and the record is replaced. Records affected by this processing can be identified by the symbol OCLCG in field 040 $d. When a problem is encountered, the record is skipped and reported for manual intervention. Dr. Hickey has posted a description of the project on his blog, Outgoing, at http://outgoing.typepad.com/outgoing/2008/04/controlling-nam.html. Glenn E. Patton Director, WorldCat Quality Management OCLC 6565 Kilgour Place Dublin OH 43017-3395 Phone: +1.800.848.5878, ext. 6371 or +1.614.764.6371 Fax: +1.614.718.7187 Email: mailto:[EMAIL PROTECTED]
Fw: [SACOLIST] Radio program genre/form headings
FYI - - Original Message - From: CPSO [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, April 11, 2008 1:27 PM Subject: [SACOLIST] Radio program genre/form headings [Excuse the duplication; this message is being posted to multiple lists. Please feel free to forward it as appropriate.] In August 2007, the Cataloging Policy and Support Office (CPSO) announced a project to begin issuing genre/form authority records (MARC 21 tag 155) for motion pictures, television programs, and videos. As the next step in the development of genre/form headings at the Library of Congress, CPSO has begun a project to create genre/form headings for radio programs. These headings are being created by catalogers in the Motion Picture, Broadcasting, and Recorded Sound Division (MBRS) Division and will join those already being established for moving images. They are based chiefly on the concepts represented in the Radio Form/Genre Terms Guide (RADFG). Existing LCSH headings in the area of radio programming (MARC 21 tag 150) will also be considered for inclusion. To support the creation and application of these headings, CPSO and MBRS have drafted a Subject Cataloging Manual (SCM) instruction sheet, H 1969.5, which is available in PDF format on CPSO’s website at http://www.loc.gov/catdir/cpso/genre2.html. Interested parties are invited to send comments on this instruction sheet to Janis Young at [EMAIL PROTECTED] CPSO reminds SACO participants that change requests and proposals for genre/form headings are not being accepted at this time. Cataloging Policy and Support Office Library of Congress Washington, DC
Re: Materials from 2000 LC SACO Training Workshop
Thanks for looking into this! Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Marlene Schiffman To: heb-naco@lists.acs.ohio-state.edu Sent: Thursday, March 13, 2008 6:35 AM Subject: RE: Materials from 2000 LC SACO Training Workshop That's the one where we worked on the heading for the Expulsion of 1492! I remember it, but can't find the materials as yet. -- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Heidi G. Lerner Sent: Thursday, March 13, 2008 8:01 AM To: heb-naco@lists.acs.ohio-state.edu Cc: Yossi Galron Subject: Materials from 2000 LC SACO Training Workshop Dear group, I am trying to locate the content from the SACO Training Workshop held at LC at the 2000 AJL. If any of you have some or all of them could you please let me know. Thanks in advance, Heidi Lerner Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED]
Re: Materials from 2000 LC SACO Training Workshop
i see that you establisehd the heading do you know what date or year you submitted the heading? Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Marlene Schiffman To: heb-naco@lists.acs.ohio-state.edu Sent: Thursday, March 13, 2008 6:35 AM Subject: RE: Materials from 2000 LC SACO Training Workshop That's the one where we worked on the heading for the Expulsion of 1492! I remember it, but can't find the materials as yet. -- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Heidi G. Lerner Sent: Thursday, March 13, 2008 8:01 AM To: heb-naco@lists.acs.ohio-state.edu Cc: Yossi Galron Subject: Materials from 2000 LC SACO Training Workshop Dear group, I am trying to locate the content from the SACO Training Workshop held at LC at the 2000 AJL. If any of you have some or all of them could you please let me know. Thanks in advance, Heidi Lerner Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED]
PCC Ad Hoc Serices Review Task Force
Please see below: The PCC Ad Hoc Series Review Task Force seeks your comments on its Discussion Paper on PCC Series Policies and Practices available from http://www.loc.gov/acq/conser/PCC-Series-DP.pdf The paper is intended to generate comments useful in making recommendations for the future direction of PCC series practices and policies. Any individuals or organizations interested in series control policies, practices, and services are welcome to comment. The task force membership and charges are available from: http://www.loc.gov/catdir/pcc/archive/SeriesReviewTF.html Please send your comments to co-chairs Amy Turner [EMAIL PROTECTED] or Les Hawkins [EMAIL PROTECTED] by Jan. 25th 2008. Sincerely, Les Hawkins CONSER Coordinator Library of Congress v. 202 707-4852 [EMAIL PROTECTED] Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED]
Fw: [PCCLIST] PCC series task force paper available
Please see below re series practices: - Original Message - From: Les Hawkins [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 14, 2007 11:20 AM Subject: [PCCLIST] PCC series task force paper available This email is being sent to multiple emails lists with apologies for the cross posting. Please feel free to forward this to other interested parties. The PCC Ad Hoc Series Review Task Force seeks your comments on its Discussion Paper on PCC Series Policies and Practices available from http://www.loc.gov/acq/conser/PCC-Series-DP.pdf The paper is intended to generate comments useful in making recommendations for the future direction of PCC series practices and policies. Any individuals or organizations interested in series control policies, practices, and services are welcome to comment. The task force membership and charges are available from: http://www.loc.gov/catdir/pcc/archive/SeriesReviewTF.html Please send your comments to co-chairs Amy Turner [EMAIL PROTECTED] or Les Hawkins [EMAIL PROTECTED] by Jan. 25th 2008. Sincerely, Les Hawkins CONSER Coordinator Library of Congress v. 202 707-4852 [EMAIL PROTECTED]
Fw: [PCCLIST] Announcement on non-Latin characters in name authority records
Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: David W Reser To: [EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 7:02 AM Subject: [PCCLIST] Announcement on non-Latin characters in name authority records Announcement on non-Latin characters in name authority records The major authority record exchange partners (British Library, Library of Congress, National Library of Medicine, and OCLC, Inc., in consultation with Library and Archives Canada) have agreed to a basic outline that will allow for the addition of references with non-Latin characters to name authority records that make up the LC/NACO Authority File. While the romanized form will continue to be the authorized heading (authority record 1XX field), NACO contributors will be able to add references in non-Latin scripts following MARC 21’s “Model B” for multi-script records. Model B provides for unlinked non-Latin script fields with the same MARC tags used for romanized data, such as authority record 4XX fields. Using Model B for authorities is a departure from the current bibliographic record practice of many Anglo-American libraries where non-Latin characters are exported as 880 fields (Alternate Graphic Representation) using MARC 21’s “Model A” for multiscript records. For the initial implementation period, the use of non-Latin scripts will be limited to those scripts that are represented in the MARC-8 repertoire (Japanese, Arabic, Chinese, Korean, Persian, Hebrew, Yiddish, Cyrillic, and Greek). Although the exchange of authority records between the NACO nodes will be in UTF-8, LC’s Cataloging Distribution Service will continue to supply the MDS-Authorities weekly subscription product in both UTF-8 and MARC-8 for some period of time. It is expected that the use of non-Latin scripts beyond the MARC-8 repertoire will be implemented in the future. Guidelines for use by catalogers in formulating non-Latin references for authority records are still in progress. System vendors should be prepared to handle authority records with non-Latin data no earlier than April 2008. Test files will be made available prior to that time. Questions can be addressed to [EMAIL PROTECTED]
Fw: [PCCLIST] Revised edition of DIFFERENCES BETWEEN, CHANGES WITHIN
Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Kevin M. Randall To: [EMAIL PROTECTED] Sent: Monday, October 15, 2007 4:28 PM Subject: [PCCLIST] Revised edition of DIFFERENCES BETWEEN, CHANGES WITHIN (this message is cross-posted; please excuse any duplication) We are pleased to announce publication of Differences Between, Changes Within: Guidelines on When to Create a New Record (revised edition, 2007). This revised edition is now available as a free, 38-page download (.pdf) and is no longer available as a print publication. Originally intended to be an appendix to the 2002 AACR2 rule revisions, Differences Between, Changes Within evolved into a stand-alone document that supplements current descriptive cataloging rules by providing information about creating new records or updating existing records. The document helps guide the cataloger in determining whether the item in hand can be cataloged with existing copy or requires a new bibliographic record. General guidelines are followed by specific guidelines for manifestation-level records for single-part monographs, multipart monographs, integrating resources, and serials. The text describes what constitutes a major difference between manifestations, requiring the creation of an original record, as well as detailing major changes within a serial manifestation that would lead to the creation of a new record. In addition, guidance is also provided to identify minor changes that would not require a new bibliographic record, but might necessitate updating an existing record. The new edition of Differences Between, Changes Within reflects changes through the final set of amendments to AACR2, which were issued in 2005. Some guidelines have been changed and some removed. All rule references have been verified and updated wherever necessary. To download your PDF copy of Differences Between, Changes Within, direct your browser to http://www.ala.org/ala/alctscontent/alctspubsbucket/webpublications/cataloging/newrecord/differences.htm Kevin M. Randall Chair, Task Force to Maintain the CC:DA Publication Differences Between, Changes Within (ALA/ALCTS/CCS Committee on Cataloging: Description and Access) Kevin M. Randall Principal Serials Cataloger Bibliographic Services Dept. Northwestern University Library 1970 Campus Drive Evanston, IL 60208-2300 email: [EMAIL PROTECTED] phone: (847) 491-2939 fax: (847) 491-4345
Re: oclc hebrew problems: transliteration macro?
Dear Jasmin, Thanks for opening up the discussion on the implications of using the OCLC Hebrew transliteration micro. Awareness of its limitations is especially crucial to the RLIN Hebraica cataloging community that is now making the transition to OCLC. We have much to learn. Does OCLC use the macro to add Hebrew script to Hebraica records in the OCLC database that lack Hebrew script? If that is the case then we need to bring up this issue with OCLC and make sure that its quality control team reviews the Hebrew script after invoking the macro. Obviously lndividual catalogers creating and enhancing Hebraica records in the OCLC database will need to review their work even more closely if they use the transliteration macro. Best, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Jasmin Nof [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Wednesday, May 30, 2007 9:39 AM Subject: oclc hebrew problems: transliteration macro? dear hebrew OCLC catalogers, if you have been using a macro to add vernacular characters to your records -- /please/ review the work. i found this record to have good romanization, but the hebrew end letters were given as regular letters, e.g. בנ פזי, שמריהו. the abridged record (with highlighted errors) is attached. thanks!! jasmin -- Jasmin Nof Judaica and Hebraica Cataloger Non-Roman Cataloging Team Leader 2200 McKeldin Library University of Maryland College Park, MD 20742 301-405-9337 [EMAIL PROTECTED]
Fw: [PCCLIST] Reporting Authority File Maintenance
Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Antony Robert David Franks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 30, 2007 2:54 AM Subject: [PCCLIST] Reporting Authority File Maintenance PCC members should keep in mind distinctions in appropriate reporting of authority file maintenance to OCLC, and/or LC--CPSO, and/or LC--Coop Team. These confusions are resulting in this work either not getting done, or in extensive delays. PCC Members There are two types of database maintenance which must be reported by member catalogers to their institution's liaison for relaying to the LC liaison. See the NACO Participant's Manual at http://www.loc.gov/catdir/pcc/naco/npm3rd.pdf 1. Deletions of Name Authority Records (NARs) in the LC/NACO Authority File and the annotation of the 010 field with a $z field. Due to database security, this work must be done at LC. These changes are distributed on a regular basis to the other copy holders of the authority file (which includes OCLC) for further distribution or other use. Other revisions to records in the LC/NACO Authority File, such as (but not limited to) conflict resolution or typo correction are within the abilities of independent NACO member institutions. 2. Revisions to existing Library of Congress Subject Heading authority records. The master file for LCSH is a separate database to which only a specific unit within LC has access. PCC members must use the regular SACO procedures for proposing changes of any kind to subject authority records. The guidelines for revisions to subject authority headings, along with a web form for making such proposals, are at http://www.loc.gov/catdir/pcc/saco/saco.html There are three important points to make about this workflow: 1. Sending messages to the appropriate LC personnel avoids delays. Communications of this nature sent to either OCLC or CPSO by PCC members are identified and relayed by them, through me, to the appropriate LC staff. 2. Catalogers of member institutions should send these needs to their institution's NACO liaison, who will then send them to the LC liaison. The individual e-mails from the combined catalogers of 500+ PCC member institutions when condensed into the in boxes of six Cooperative Program Specialists in LC doth chaos make. 3. We trust independent members to make revisions to authority records in the LC/NACO Names Authority File. When one authority record is to be deleted and another retained, member catalogers should transfer the data needed from one record to the other. Unfortunately, there is no way to merge authority records; nor, in OCLC, should a $z subfield be added to an 010 field by a member institution. Non-PCC Members Work of the above types should be reported to CPSO at [EMAIL PROTECTED] Anthony R.D. Franks Team Leader, Cooperative Cataloging Team Library of Congress 202-707-2822 (voice) 202-252-2082 (fax)
Re: romanization q
Hi Bob, I think that Mag''ar is a possibility ([:apostrophe: after the g; ayin diacritic' before the a] and make a reference from Mig''ar. LC has taken the opposite approach however, in nar n 96112047. In situations like this, I recommend that if you dont have a romanized form of the name, choose a romanizatino, make a reference from the other possibility and then code it provisional. Heidi Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Robert Talbott [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Cc: yossi Galron [EMAIL PROTECTED] Sent: Wednesday, August 23, 2006 1:30 PM Subject: romanization q folks: i have little book of charms and spells written (sefer otsrot-malakhim) by one Yis´ra'el ben Me'ir ben m. v?e-R. Zekharyah ben m. v?e-R. Se?adyah ben m. v?e-R. Shalom Almagor (Mag'ar). that last bit, Mag'ar, is a guess. it looks arabic. anyhow, i need help romanizing this thing. it's spelt: mem-gimel apostrophe-ayin-resh sofit. thanks in advance. b
Fw: [PCCLIST] PCC Series FAQ
FYI see below: Heidi - Original Message - From: Antony Robert David Franks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 4:37 AM Subject: [PCCLIST] PCC Series FAQ The current Series FAQ has been redone in html and posted at the PCC web site: http://www.loc.gov/catdir/pcc/bibco/seriesfaq.html The recent OCLC announcements and any decisions made during ALA will require some revisions. Anthony R.D. Franks Team Leader, Cooperative Cataloging Team Library of Congress 202-707-2822 (voice) 202-252-2082 (fax)
Fw: [PCCLIST] FW: OFFICIAL: Full Implementation of OCLC-MARC Format Update 2006
Title: OFFICIAL: Full Implementation of OCLC-MARC Format Update 2006 Heidi G. LernerHebraica/Judaica CatalogerMARC UnitStanford University LibrairesStanford, CA 94305-6004ph: 650-725-9953fax: 650-725-1120e-mail: [EMAIL PROTECTED] - Original Message - From: Patton,Glenn To: [EMAIL PROTECTED] Sent: Friday, June 16, 2006 6:29 AM Subject: [PCCLIST] FW: OFFICIAL: Full Implementation of OCLC-MARC Format Update 2006 With apologies for multiple postings.___ Full Implementation of OCLC-MARC Format Update 2006 With the official release of Connexion client 1.60 announced on 2006 June 15, please begin to use all of the new capabilities, new fields and subfields, new codes, and new characters that were documented in OCLC Technical Bulletin 252 (http://www.oclc.org/support/documentation/worldcat/tb/252/) as part of the OCLC-MARC Format Update 2006. New searching and indexing capabilities: With the exceptions and Connexion interface differences noted in Technical Bulletin 252, all new searching and indexing capabilities should now be used in all Connexion interfaces. Note that, as OCLC continues to convert data, searches that include the qualifiers for Continuing Resources, Integrating Resources, and Serials may not retrieve complete results sets. New practices for Integrating Resources, including the use of BLvl i: These should be implemented in all Connexion interfaces immediately. Please use the "Guidelines for Integrating Resources" section of Technical Bulletin 252 to update the document "Cataloging Electronic Resources: OCLC-MARC Coding Guidelines" (http://www.oclc.org/support/documentation/worldcat/cataloging/electronicresources/default.htm). The document will be revised online soon. New fields, subfields, and indicators: These should be used in all Connexion interfaces immediately. New codes: These should be used in all Connexion interfaces immediately. In Connexion client 1.50, new codes will not appear in dropdown lists, but can be input manually. New characters: These should be used in all Connexion interfaces immediately, subject to the revision of Library of Congress Rule Interpretations 1.0E, 1.4F5, and 1.4F6, where appropriate. Data Conversion and Indexing Note that some data conversions and other changes are currently still in progress and will be completed over the course of the next few weeks and months. To the extent possible, these are noted in Technical Bulletin 252. OCLC will keep users informed about the progress of the major conversions. Upgrade to Connexion client 1.60 To take full advantage of the new capabilities that are now available in Connexion client 1.60 and to avoid the limitations of client 1.50, users are strongly encouraged to switch from 1.50 to 1.60 at their earliest convenience. Remember that OCLC will discontinue the Connexion client 1.50 on 2006 October 1. Jay Weitz Senior Consulting Database Specialist OCLC Online Computer Library Center MC 139 6565 Frantz Road Dublin, Ohio, USA 43017-0702 Phone: 614-764-6156 Fax: 614-718-7195 E-mail: [EMAIL PROTECTED]
Fw: [RDA-L] Draft of RDA part A, chapters 6-7 available]
Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] Original Message Subject: [RDA-L] Draft of RDA part A, chapters 6-7 available Date: Tue, 20 Jun 2006 18:36:33 +0100 From: Nathalie Schulz [EMAIL PROTECTED] Reply-To: Resource Description and Access / Resource Description and Access [EMAIL PROTECTED] To: [EMAIL PROTECTED] The Joint Steering Committee for Revision of AACR (JSC) is pleased to announce that the draft of RDA part A, chapters 6-7 has been made available for comment. Please see the following Web page for the draft and details on making comments: http://www.collectionscanada.ca/jsc/rdadraftch6-7.html Nathalie Schulz Secretary, JSC [EMAIL PROTECTED]
Fw: MARC-8 Characters Now Valid in Bibliographic and Authority Records
Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: News from RLG [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 2:16 PM Subject: MARC-8 Characters Now Valid in Bibliographic and Authority Records MARC-8 Characters Now Valid in Bibliographic and Authority Records The fifteen MARC-8 characters listed below are now valid for input in authority records and export in both bibliographic and authority records. Using the client, you can directly input only three of the characters from the keyboard: left curly bracket, right curly bracket, and script small l. To input any of the other characters, we recommend creating RLIN21 macros. See full instructions at http://www.rlg.org/en/page.php?Page_ID=20956 Since database migration, these MARC-8 characters have all been valid in the RLIN21 client for bibliographic records. However, on export of bibliographic records, surrogates were supplied for degree sign, sound recording copyright, copyright, music sharp, inverted question mark, and inverted exclamation mark. The client will now export the real value of these characters. CIRCUMFLEX ACCENT (SPACING CIRCUMFLEX) LOW LINE = SPACING UNDERSCORE GRAVE ACCENT (SPACING GRAVE) LEFT CURLY BRACKET (OPENING CURLY BRACKET) RIGHT CURLY BRACKET (CLOSING CURLY BRACKET) TILDE (SPACING TILDE) DEGREE SIGN SCRIPT SMALL L SOUND RECORDING COPYRIGHT COPYRIGHT SIGN MUSIC SHARP SIGN INVERTED QUESTION MARK INVERTED EXCLAMATION MARK EURO SIGN ESZETT (NOT YET ENABLED FOR AUTHORITIES) Note: Do not confuse the newly valid spacing characters (circumflex, underscore, tilde, and grave) with their long-valid non-spacing counterparts. Use of the spacing characters will be limited almost exclusively to URLs. Users may continue to substitute %5F for the spacing underscore and %7E for the spacing tilde. Note: None of these MARC-8 characters is searchable. If a search value includes any of these characters, the system changes it to null. 45236
Re: Fw: Africans Librarians Counceil letter sent to LC re SARs decision
Dear Daniel, This is an excellent letter. I have no comments. Thank you for your hard work on this issue. We are very, very fortunate to have you as Chair of the AJL Cataloging Committee. Warmly, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Daniel Lovins [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, June 02, 2006 7:13 AM Subject: Re: Fw: Africans Librarians Counceil letter sent to LC re SARs decision Dear colleagues, Here is a second attempt at an open letter from AJL. Very interested in your feedback. Thanks. Daniel Dear Director Wiggins, We are deeply concerned by the decision of the Library of Congress (LC) to discontinue creation of series authority records (SARs) effective June 1, 2006. While we appreciate LC's willingness to push the action date back from April 20th -in order to give affected libraries time to develop contingency plans- we urge LC to revisit the decision, and to consider whether a more nuanced approach to series authority control might be preferable. Perhaps being more selective about when to establish series title headings (e.g., prioritizing university press publications) would help reduce costs. In any event, we believe that greater consultation with other libraries -including postponing implementation until after the ALA 2006 annual meeting-would have helped avoid the current atmosphere of mistrust. AJL sympathizes with recent statements from the ALA Executive Board, the Library of Congress Professional Guild, the Africana Librarians Council, the Music Library Association, the ALCTS Board of Directors, and other concerned groups, and finds that the indiscriminate discontinuation of series authority records, combined with the lack of consultation with other stakeholders, compromises LC's professed commitment to uniform bibliographic standards and cooperative cataloging. We believe the new policy will increase costs to all libraries, including, quite possibly, the Library of Congress itself. We also know from daily experience that our users greatly appreciate being able to search by series title, and to have such titles normalized and collocated within our catalogs. We support ALCTS' request for LC to share the rationale behind its decision, including as many aspects of the decision making process as possible, in hopes that other libraries outside LC could carefully examine their own series practices in a thoughtful manner. In particular, we would be interested in any empirical data that suggest series authority control is no longer cost-effective or desired by our patrons. Deanna Marcum stated in her 2005 EBSCO forum address that, if certain other work could be moved to non-professional staff, catalogers could spend more time on authority control, subject analysis, resource identification, and evaluation, and collaboration with information technology units on automated applications and digitization projects. We are confused, therefore, as to why series authority control has been singled out for elimination. Moreover, we are concerned that this latest decision is just the beginning of a long-term retrenchment in LC's commitment to bibliographic control. [Maybe leave this out ... (?): It seems tragic that at a time when LC is at the pinnacle of influence and respectindeed its name has become a gold standard among libraries around the world -- when LC Subject Headings, LC Classification, MARC21, and other LC achievements are being translated into multiple languages, and vital initiatives such as MODS and METS are gaining traction at various types of cultural memory institutions -that LC would choose this moment to undercut confidence in its leadership and collegiality.] We are similarly concerned by LC having signed a contract with the Italian book vendor Casalini Libri to catalog thousands of titles a year, none of which is to be shared with other OCLC or RLG libraries. (OCLC, to its credit, has since made its own arrangements for wider distribution of these records). Again, there may be compelling reasons to have taken this route, but the lack of consultation with other stakeholders is disconcerting. If present trends continue, the pool of shared cataloging which has done so much to reduce costs and nourish American libraries over the past 30 years will either dry up from neglect or become brackish with inferior content. With staffing cutbacks at LC and elsewhere, the recycling of substandard records is likely to increase throughout the shared cataloging system and cause a degradation of service to all our patrons. We believe the new LC policy will have a profound effect on cataloging-on-receipt and shelf-ready initiatives across the country as costs are shifted to individual libraries. This will possibly save LC some money
Fw: Africans Librarians Counceil letter sent to LC re SARs decision
Hi Yos, I had this last Monday but I did not see this posted. Ifit has not appeared on Hasafran and Heb-NACO could you please post it. Thanks, Heidi Heidi G. LernerHebraica/Judaica CatalogerMARC UnitStanford University LibrairesStanford, CA 94305-6004ph: 650-725-9953fax: 650-725-1120e-mail: [EMAIL PROTECTED] - Original Message - From: Heidi Lerner To: [EMAIL PROTECTED] ; heb-naco@lists.acs.ohio-state.edu Sent: Monday, May 15, 2006 10:33 AM Subject: Fw: Africans Librarians Counceil letter sent to LC re SARs decision Dear safranim, This letter was sent to the Library of Congress from the Africana Librarians Council. I am certain that our membership and the institutions that we represent share similar concerns. Thanks, Heidi Lerner Heidi G. LernerHebraica/Judaica CatalogerCatalog Dept.Stanford University LibrariesStanford, CA 94305-6004ph: 650-725-9953fax: 650-725-1120e-mail: [EMAIL PROTECTED] - Original Message - From: Margaret Hughes To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Monday, May 15, 2006 10:08 AM Subject: [Fwd: ALC letter sent to LC re SARs decision] Dear ALC colleagues - You'll find below a text version of the letter from the Africana Librarians Council sent to the Library of Congress regarding the 20 April 2006 decision to cease creating series authority records. [snip] Yours, Lauris TEXT OF LETTER 12 May 2006 Beacher J.E. Wiggins Director for Acquisitions and Bibliographic Access Library of Congress Washington, DC 20540-4300 Dear Director Wiggins, The membership of the Africana Librarians Council - the organization of professional librarians working in African studies and a sponsored organization of the African Studies Association (U.S.) - has requested that I notify you regarding our concern over the Library of Congress's 20 April 2006 decision to cease creating series authority records and providing controlled series access in bibliographic records. Series control, as with all aspects of bibliographic control, is critically important in the ever-expanding world of book publishing in Africa. As with many industries in developing countries, African book publishing often seems unsystematic, with books typically printed in short runs and reprinted several years later exhibiting changes in bibliographic elements. We see any erosion in bibliographic control as harmful to the Library of Congress's mission to collect research materials from African countries and also to its Cooperative Acquisition Program partnerships with U.S. research libraries. We observe that African studies readers in the U.S. rely upon series names as brands of quality. Several major African publishers have made formal arrangements with U.S. and other publishers to co-publish, reprint, or distribute their titles outside Africa. To navigate through this confusing and duplicative literature, bibliographers, acquisitions librarians, and - most important - readers, especially scholarly readers, need controlled series names. Your annual report for FY2005 noted that the Library of Congress has moved to improve the cataloging capabilities of its overseas offices. The Library of Congress's overseas offices serve as a major acquisitions source for U.S. research libraries. Your achievement - including direct inputting into Voyager - will accelerate access to overseas acquisitions for American readers, as the bibliographic records created by the overseas offices are becoming available to Library of Congress Cooperative Acquisition Program partners even as we unpack the shipping boxes! Preserving the privileges of overseas office cataloging staff to produce authority records takes advantage of in- country headings research, which replaces costly transatlantic communication. Continuing the practice brings economic benefits by reducing State-side workloads - both at the Library of Congress and among those U.S. research libraries building African collections with one or no Africanist cataloger - with no or negligible fiscal increases. And most important, it would strengthen the professionalization of librarians in developing countries. We hope that you will lead a re-examination of the Library of Congress's series authority decision. We ask also that you avoid making similar decisions in the future without consulting your partners in the Library of Congress's Program for Cooperative Cataloging, and your professional colleagues in the Asian, African and Middle Eastern Section of the Association of College and Research Libraries and in the Cataloging Classification Section Committee on Cataloging Asian African Material of the Association for Library Collections Technical Services. Please do not hesitate to contact me directly to discuss the Africana
Re: ôåìéï, îòäøï, áòäîòï åàåðâøï
You are correct. See Encyclopedia Judaica, v.12, col. 295. Heidi Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Benjamin S Fryser [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Cc: [EMAIL PROTECTED] Sent: Tuesday, December 27, 2005 9:31 AM Subject: ôåìéï, îòäøï, áòäîòï åàåðâøï Can someone in Heb-Naco land tell me what modern country, region, or city is Mehrn as in ke-minhag ha-medinot Polin, Behmen, Mehrn, Ungarn . The book in question Seder yeme ha-selihot ... ke-minhag ha-medinot Could Mehrn be MORAVIA?? Thanks, Benjamin Fryser Senior Cataloger Specialist Library of Congress Regional Cooperative Cataloging Washington, D.C. 20540 [EMAIL PROTECTED]
Fw: [PCCLIST] 667 and 043 Documentation
Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Antony Robert David Franks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 24, 2005 4:54 AM Subject: [PCCLIST] 667 and 043 Documentation Two revisions to documentation have now been mounted on the NACO site http://www.loc.gov/catdir/pcc/naco/naco.html under the section Documentation, tools, rules, etc. DCM Z1 (667 section) contains the entire section for field 667. Under the portion headed NARs and subject usage, the subsection headed (b) Earlier/Later Linear Jurisdictional Name Changes has been revised to reflect the need to notify CPSO of such changes. LC Guidelines Supplement to the MARC 21 Format for Authority Data, 043 field has been revised to assure that only 151 NARs will have an 043 GAC added. Anthony R.D. Franks Team Leader, Cooperative Cataloging Team Library of Congress 202-707-2822 (voice) 202-252-2082 (fax)
Fw: [PCCLIST] Processing Hiatus during Unicode Implementation at LC
Heidi G. Lerner Hebraica/Judaica Cataloger MARC Unit Stanford University Libraires Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] - Original Message - From: Antony Robert David Franks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 13, 2005 4:41 AM Subject: [PCCLIST] Processing Hiatus during Unicode Implementation at LC Processing Hiatus during Unicode Implementation at LC From October 30*November 10, 2005, the Library of Congress will convert its Integrated Library System to Unicode. During that time, the LC database will be in read-only mode and will be accessible for searching by users. The LC ILS upgrade will impact some PCC activities. SACO The Cooperative Cataloging Team will be able to receive either new SACO proposals or revisions to existing LCSH. During this time, however, the Coop Team will not be able to process SACO proposals or revisions. This will create a delay in processing as a backlog develops. Classification proposals, similarly, cannot be processed during this period. NACO NACO members will be able contribute new records and revisions. These contributions will be held at LC for processing and re-distribution at the end of the implementation period. Therefore NACO participants will not see their contributions in the LC/NACO Authority File until after November 14, 2005. The Cooperative Cataloging Team will not be able to perform bibliographic file maintenance reported by members, delete or revise duplicate name authority records, or resolve conflict situations. NACO members should arrange with their LC liaison to hold such reports at the institution or to report to the LC liaison to hold until November 14, 2005. NACO members under review may continue to provide records as usual through their utility under existing arrangements with their reviewer. Keep in mind, however, that approved and contributed records will not be available in the copies of the LC/NACO Authority File at LC, OCLC, RLG, or the British Library due to the hiatus in processing and distribution. There will be increased possibility of duplication or conflict in authority records. Literary author numbers (053 requests) cannot be processed during this period. Other Members of the Coop Team will continue to be in residence at the Library of Congress during this break in activity. Team members will be available to answer inquiries and consult with members as usual. Regular non-automated activities such as training and documentation will go on. Anthony R.D. Franks Team Leader, Cooperative Cataloging Team Library of Congress 202-707-2822 (voice) 202-252-2082 (fax)
updates to Heb-NACO website
The NACO Hebraica Funnel has been recently updated. The site now has the most recent version of the list of Yiddish Personal Names of Hebrew or Aramaic Derivation. I have alsoadded Daniel Lovin's "Judeo German Checklist" to the list of Hebraica/Judaica cataloging resources.Daniel, thank you very much for taking the initiative in creating this document and also contacting the ISO 639-2 maintenance agency requesting changes to thecurrent guidelines which have "Judeo-German" as a cross reference to the preferred term "Yiddish", etc. Heiid. Heidi G. LernerHebraica/Judaica CatalogerCatalog Dept.Stanford University LibrariesStanford, CA 94305-6004ph: 650-725-9953fax: 650-725-1120e-mail: [EMAIL PROTECTED]
Fwd: [PCCLIST] New NACO Trainers Materials Available
More for NACO catalogers: X-Sieve: CMU Sieve 2.2 X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Wed, 24 Aug 2005 14:03:54 -0400 Reply-To: Program for Cooperative Cataloging [EMAIL PROTECTED] Sender: Program for Cooperative Cataloging [EMAIL PROTECTED] From: Antony Robert David Franks [EMAIL PROTECTED] Subject: [PCCLIST] New NACO Trainers Materials Available Comments: To: [EMAIL PROTECTED], [EMAIL PROTECTED] To: [EMAIL PROTECTED] Supplemental materials reflecting new NACO practices have been mounted on the NACO trainers' website. These cover the recent CPSO announcements on Implementation of New Practicew for Government-Designated Parks, Forests, Etc. and Headings for Indian tribes Recognized by the US Government Many thanks to Adam Schiff and Ana Cristan in developing and publishing this material. Anthony R.D. Franks Team Leader, Cooperative Cataloging Team Library of Congress 202-707-2822 (voice) 202-252-2082 (fax) Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: romanization of Cape of Good Hope
Dear Jasmine, I believe that it should be Kef ha-Tikvah ... [subscript dot under kuf and vov]. That is how kaf,feh sofi is vocalized in Even-Shoshan which has Kef ha-tikvah ... . And we should transcribe vowels as they appear on a vocalized or partially vocalized title page. Heidi At 10:38 AM 8/17/2005 -0400, you wrote: Hi, I'm working on the record for Azila Reisenberger's From Here to the Cape of Good Hope. Question about romanizing the country's name: I see in both RLIN and OCLC that libraries have romanized it as Kaif ha-Tikvah ha-Tovah. Why is the double-yud of Cape (ק××פ) not romanized e (as in Ke) considering the nikud under the first yud is (?) a tzere? And why is the peh not romanized as p (as in Kep), considering that the letter is given as a regular peh, not peh-sofit? In other words, why is it not Kep instead of Kaif? (That is the spelling used in Harvard's OCLC record) Thanks, Jasmin -- Jasmin Nof Judaica and Hebraica Cataloger 2200 McKeldin Library University of Maryland College Park, MD 20742 301-405-9330 [EMAIL PROTECTED] Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: romanization of Cape of Good Hope
If the peh had a dagesh in it then I would certainly think that it should be transcribed as Kep. I don't have the book in front of me, so I don't know if there is a dagesh or not. The bibliographic record for the item has a note T.p. partially vocalized. At 12:04 PM 8/17/2005 -0700, you wrote: Heidi wrote: I believe that it should be Kef ha-Tikvah ... ... That is how kaf,feh sofi is vocalized in Even-Shoshan which has Kef ha-tikvah ... But doesn't it make a difference that Jasmin's book does not have a feh sofit, but rather a normal peh? (See below.) -Stanley Nachamie [EMAIL PROTECTED] --- Jasmin had written: ... why is the peh not romanized as p (as in Kep), considering that the letter is given as a regular peh, not peh-sofit? Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: adding Hebrew to bib records
Dear Jasmine, I do not know how you will export records from OCLC into your local system and whether or not your local system currently supports non-roman scripts. I can only share with you Stanford's experiences and decisions in this matter from the standpoint of an RLIN library. Stanford was one of the first libraries to take advantage of the Hebrew script offered by RLIN. Our local does not yet support Hebrew or other non-roman scripts but we have always made our cataloging decisions based on the premise that one day our local system would do so. We made our decisions on utilizing RLIN's non-roman script after examining the implications of cost vs. access. At Stanford we provide Hebrew script for originaly cataloging for the core fields that were defined by RLIN (245, 250, 260 and 440). We also provide Hebrew script as much as possible for 1xx and 7xx fields. The Hebrew script is stripped out when the records are exported to our local system with the thought that these records will be overlayed with the RLIN records containing the non-roman fields at such time as our local system will support non-roman scirpts. For those records that have copy available but that lack Hebrew script fields, our copy cataloger supplies the title proper (subfield a of the 245 field) and a main entry in readily identifiable. Copy with Hebrew script is accepted as is. You and your administrators will have to decide whether the added costs of providing Hebrew script to your catalog records sufficiently benefit your library's patrons, whether or not you will retroactivlely recatalog your roman-script only catalog records, and also think about the future impact of shared cataloging with Israeli libraries that may provide Hebrew-script only records to the utilities. Heidi - Original Message - From: Jasmin Nof [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Tuesday, July 26, 2005 11:17 AM Subject: adding Hebrew to bib records Hello fellow catalogers, Here at Maryland we've just migrated to Connexion 1.4. Now having the ability to input Hebrew, I'm faced with the decision of whether to add Hebrew to all records that lack the vernacular, or only to original records I contribute. What are you other catalogers doing? If you're an RLIN user, when Hebrew became available, did your library start adding Hebrew to all records, or only to new records you were submitting? Thank you for your time and help, Jasmin -- Jasmin Nof Judaica and Hebraica Cataloger 2200 McKeldin Library University of Maryland College Park, MD 20742 301-405-9330 [EMAIL PROTECTED]
Re: Subject headings help...
Hi Steve - I would like to encourage you to submit 'Eglah 'arufah as a subject heading via the Judaica SACO Funnel. The funnel was established to encourage and enable catalogers at non-PCC member institutions to contribute subject headings of relevance to Jewish Studies and Hebraica. If you are interested, I suggest that you review the SACO website (http://www.loc.gov/catdir/pcc/saco/saco.html), use the e-mail form for proposing new headings, and send/fax your proposal to me for review. After I have gotten back to you with comments, etc. you can then use the web-form for proposing new headings. If you have any questions, please let me know. Heidi At 10:53 AM 7/27/2005 -0400, you wrote: You may wish to propose 'Eglah 'arufah as a subject heading. There's an article in EJ, so it would be very easy to justify it. There is also a heading Atonement (Prayer)--Judaism. And as Stanley suggested, you can assign a subject for the pesukim, if the work addresses the ritual and its biblical source. Lenore [EMAIL PROTECTED] 07/26/05 1:05 PM I have a book in hand about the meaning of the formulaic statement of innocence/request for forgiveness recited by the elders of a city during the Eglah Arufah ceremony, in which a cow that has not yet been used for labor is slaughtered to atone for the finding of a murdered body in the outskirts of the city. Any ideas as to subject headings that might apply to this book? Steven Deut. 21:1-9 If one be found slain in the land which the Lord thy God giveth thee to possess it, lying in the field, and it be not known who hath smitten him; then thy elders and thy judges shall come forth, and they shall measure unto the cities which are round about him that is slain. And it shall be, that the city which is nearest unto the slain man, even the elders of that city shall take a heifer of the herd, which hath not been wrought with, and which hath not drawn in the yoke. And the elders of that city shall bring down the heifer unto a rough valley, which may neither be plowed nor sown, and shall break the heifer's neck there in the valley. And the priests the sons of Levi shall come near--for them the Lord thy God hath chosen to minister unto Him, and to bless in the name of the Lord; and according to their word shall every controversy and every stroke be. And all the elders of that city, who are nearest unto the slain man, shall wash their hands over the heifer whose neck was broken in the valley. And they shall speak and say: 'Our hands have not shed this blood, neither have our eyes seen it. Forgive, O the Lord, Thy people Israel, whom Thou hast redeemed, and suffer not innocent blood to remain in the midst of Thy people Israel.' And the blood shall be forgiven them. So shalt thou put away the innocent blood from the midst of thee, when thou shalt do that which is right in the eyes of the Lord. (JPS, 1917) Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Prospectus for RDA
Dear catalogers, The prospectus for RDA has been posted athttp://www.collectionscanada.ca/jsc/rdaprospectus.htmlThere is also a form for comments Heidi Heidi G. LernerHebraica/Judaica CatalogerCatalog Dept.Stanford University LibrariesStanford, CA 94305-6004ph: 650-725-9953fax: 650-725-1120e-mail: [EMAIL PROTECTED]
Re: Fw: [PCCLIST] Proposed deletion of LCRI 1.0G
I got this message also.I notified CPSO that there was a problem with the link.I hope to hear from them soon. HEidi - Original Message - From: Stanley Nachamie [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Saturday, July 23, 2005 8:37 PM Subject: Re: Fw: [PCCLIST] Proposed deletion of LCRI 1.0G I tried going to the link in Heidi's message (see part of that message at the bottom of this email), and got the error message, Page Not Found. I would be interested in seeing the proposal, if I can figure out how to find it. Thanks, and Shavua` Tov. -Stanley Nachamie [EMAIL PROTECTED] CPSO has posted on its Web site at: http://www.loc.gov/catdir/cpso a call for comments on the proposed Deletion of LCRI 1.0G Accents and Other Diacritical Marks Please send comments, etc. to [EMAIL PROTECTED] before August 12, 2005.
Fw: [PCCLIST] Proposed deletion of LCRI 1.0G
- Original Message - From: Ana Lupe Cristán To: [EMAIL PROTECTED] Sent: Thursday, July 21, 2005 9:14 AM Subject: [PCCLIST] Proposed deletion of LCRI 1.0G Cross posted; apologies for the duplication *** CPSO has posted on its Web site at: http://www.loc.gov/catdir/cpso a call for comments on the proposed "Deletion of LCRI 1.0G Accents and Other Diacritical Marks" Please sendcomments, etc.to [EMAIL PROTECTED] before August 12, 2005. Ana Lupe CristánCooperative Cataloging Specialist/on detail to CPSOLibrary of Congress, LM 537Washington, DC 20540-4382tel.: 202.707.7921fax: 202.252.2082email: [EMAIL PROTECTED]
Fw: Re: [PCCLIST] Proposed deletion of LCRI 1.0G]
- Original Message - From: Joanna K. Dyla To: Inna Gudanets ; Kay Teel ; Heidi G. Lerner ; pjrolla ; Greta de Groat ; [EMAIL PROTECTED] ; Robert Rohrbacher ; Soobum Kim ; Margaret Lu Sent: Friday, July 22, 2005 7:25 AM Subject: [Fwd: Re: [PCCLIST] Proposed deletion of LCRI 1.0G] See an interesting point about French acronyms.--Joanna Original Message Subject: Re: [PCCLIST] Proposed deletion of LCRI 1.0G Date: Fri, 22 Jul 2005 09:23:04 -0400 From: Jonathan David Makepeace [EMAIL PROTECTED] Reply-To: Program for Cooperative Cataloging [EMAIL PROTECTED] To: [EMAIL PROTECTED]I support the proposed deletion of LCRI 1.0G, at least with regard to the French language. In the old days French-language typewriters could not supply accent marks for capital letters, which affected typographical conventions in general. With the switch to text-editing software that changed, which is no doubt why Libraries and Archives Canada changed its practice.My copy of the 5th ed. of «Le français au bureau» published by l'Office de la langue française (of Quebec) states on page 143 (and I translate loosely): "We should take note from the very beginning that, in conformity with all the typographical conventions and a notice of recommendation from l'Office de la langue française, capital letters take accents, the tréma and the cédille whenever small letters would take them." The only exception is for «sigles» (the English word escapes me, it might be "acronym") like «UQAM» for l'Université du Québec à Montréal. The A does not take an accent in this case because UQAM is considered a word onto itself. Jonathan David Makepeace Leddy Library University of Windsor Windsor, Ontario-- Joanna K. Dyla Head, MARC Unit Cataloging Metadata Services Stanford University Libraries 650-723-2529 [EMAIL PROTECTED]
Re: Fw: [ALA-CCDA:4881] responses to 5JSC/Chair/5, specialrules in Chapter 21
Here it is. Since I am going on vacation very early tomorrow morning, could you get any comments that you might have today? Thanks, Heiid - Original Message - From: Steven Bernstein [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Thursday, July 14, 2005 1:00 PM Subject: Re: Fw: [ALA-CCDA:4881] responses to 5JSC/Chair/5, specialrules in Chapter 21 Heidi, Would it be possible for you to resend your attachment as a Word document? Steven - Original Message - From: Heidi G. Lerner [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Thursday, July 14, 2005 2:27 PM Subject: Fw: Fw: [ALA-CCDA:4881] responses to 5JSC/Chair/5, specialrules in Chapter 21 Dear Group, Yesterday was the deadline for sending your comments to me regarding to the LC Proposal for simplication of Special Rules in chapter 21(AACR2 21.37-21.39). I am attaching a document that was put together by Lenore and is based on discussions with the LC Hebraica team and religion catalogers. If you would like to comment on this document, you may do so and send any to me by tomorrow (7/15, 1:00 PM PDT). I will share this document with the CCDA to reflect the thoughts of the AJL Cataloging community Thanks, Heidi RDAreligionajl.doc Description: MS-Word document
[no subject]
Dear Group, Attached is a draft of a response to the LC proposal regarding RDA A1.4E on publication dates that was put together by Joan and Lenore following a meeting with Dr. Barbara Tillett of CPSO. Please note that the revised proposed rule will also require the addition to the Hebrew romanization table (and to the tables of other impacted languages) of a guideline on transcribing non-Western style dates in romanized contexts.Please send me any comments that you might have as soon as possible (I am leaving for vacation tomorrow AM so prior to that). Thanks, Heidi Heidi G. LernerHebraica/Judaica CatalogerCatalog Dept.Stanford University LibrariesStanford, CA 94305-6004ph: 650-725-9953fax: 650-725-1120e-mail: [EMAIL PROTECTED] RDAA14E_071505.doc Description: MS-Word document
Fw: [PCCLIST] 2005 update of AACR2
- Original Message - From: Ana Lupe Cristán To: [EMAIL PROTECTED] Sent: Thursday, July 14, 2005 10:14 AM Subject: [PCCLIST] 2005 update of AACR2 Cross-posted, apologies for the duplication* The Library of Congress will implement the 2005 Update to the 2002 AACR2 on August 1, 2005. The 2005 AACR2 Update will be available in Cataloger's Desktop on that date.A list of the changes in the 2005 Update has been mounted on the CPSO Web site at: http://www.loc.gov/catdir/cpso/2005upd.html Please direct any questions about implementation of the changes to Bob Ewald, CPSO at: [EMAIL PROTECTED] Ana Lupe CristánCooperative Cataloging Specialist/on detail to CPSOLibrary of Congress, LM 537Washington, DC 20540-4382tel.: 202.707.7921fax: 202.252.2082email: [EMAIL PROTECTED]
Response to LC Proposalfor Simplification of Rules for RDA Area 4 (A.14), Publicatoin Area
Dear Group, The Libray of Congress has submitted a proposal for simplification of rules to the Joint Steering Committee for Revision of AACR3 (a response to part 1 of draft of AACR3 [nowRD])} :"The principle, stated in LCs response to the part I draft of AACR3, of transcribing what is presented in the resource without modification is also incorporated in this revision." In light of our recent discussion on transcription of Hebrew dates at the RS Cataloging Commiteemeeting I suggest that you look at therecommendation for A.14E. If you have comments on this, please send this tome by July 13. I willsend a responseto the Joint Steering Committee. Thanks, Heidi A.14E A1.4E. Date. a) For published resources, transcribe the date in which the resource was published as it appears on the resource, usually only as year(s). i) Date not in Western-style Arabic numerals. Add the year(s) in such numerals in square brackets as needed for comprehensibility. ii) Date not of the Gregorian or Julian calendar. Follow it with the year(s) of the Gregorian or Julian calendar in square brackets. iii) No publication date on the resource. Record a date in the following order of preference: copyright date (indicated as such; use the latest if there is more than one); date of manufacture (indicated as such); supplied date in square brackets; approximate date in square brackets. b) For unpublished resources or assembled collections, record the date of production or assembly. Heidi G. LernerHebraica/Judaica CatalogerCatalog Dept.Stanford University LibrariesStanford, CA 94305-6004ph: 650-725-9953fax: 650-725-1120e-mail: [EMAIL PROTECTED]
RS Cataloging Committee Meeting
Dear Catalogers, Below please find the minutes from the 2005 RS Cataloging Committee Meeting 1. Hebraica Cataloging Manual Joan Biella and Steve Bernstein reported that the electronic version of the Hebraica Cataloging Manual is near completion and will be mounted on the Hebraica NACO website. Catalogers should let Steve know if we want a PDF version as well. Joan will head an editorial group to provide updates and revisions to existing text. 2. Review of Forthcoming RDA Drafts Heidi will monitor draft proposals to and reports from the Joint Steering Committee for Revision of Anglo-American Cataloging Rules and will forward relevant documents to Heb-NACO for comments by Hebraica Catalogers. 3.Judeo-Arabic Romanization Table Joan presented a first draft of a proposed ALA/LC romanization table for Judeo-Arabic. This table is still a work in progress. Joan will continue to look for reliable references sources and also seek input from scholars in the field. 4.Date of Publication in Hebrew Script Daniel suggested that catalogers provide the Hebrew calendar date in the parallel 260 field in Hebrew characters. We suggested that catalogers propose several options including the transcription of chronograms, Hebrew only dates, etc. The Committee will examine the various options. LC will continue to follow its practice of transcribing Hebrew characters into numbers. 5.Use of Judeo-German in MARC Code Lists for Languages, LCSH a) Daniel will provide guidelines (to be posted on HebNACO and elsewhere) to assist catalogers in making the distinction between texts in Yiddish and those in German in Hebrew script. b) Daniel will submit a proposal to MARBI to amend the see reference from Judeo-German to Yiddish in the MARC21 Language Code List to include an explanatory note. c) Daniel will submit a SACO proposal to revise the subject authority record for Yiddish to include a scope note to advise of the distinction between Yiddish and German in Hebraic script, and 670's to justify retention of the see reference from Judeo-German, which appears to be a synonym of Yiddish in some contexts. 6. Ladino Romanization Table Heidi announced that both LC and ALA have approved the proposed romanization table for Ladino. The official version will be mounted on the Hebraica Funnel website and at LC. 6. Non-Hebrew/Aramaic Place-names in Hebrew Contexts (Leykvoud, Bilgoraya) Joan will compile a list of principles for the romanization of place names and announced that next year Aaron Taub will speak about this at AJLConvention. 7. Use of Niborskis Verterbukh fun loshn-koydesh-shtamkike verter in Yiddish as a Guide for the Romanization of Yiddish words of Hebrew Origin not found in Weinreich This was accepted by the AJL Cataloging Committee 8. Treating introductory title words Kuntres, Maamar, etc., as we currently do Sefer A formal announcement will be made that expands the list of introductory words which may be stripped off when identifying or assigning a uniform title. Currently this is done only with Sefer 9. Piyutim There is interest in following-up on last year's discussion, led by Peter Kearney (LC), of the lack of consistency in treating some piyutim (liturgical poetry) collections as uniform titles and others as form subject headings. Thank you, Heidi Lerner, Chair, AJL RS Cataloging Committee cc: Shulie Berger Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: Agenda for the RS Cataloging Commitee
Glad that you pointed it out. Now we have an extra five minutes to spend on something else. I will bring a revised agenda to the meeting. At 10:03 AM 6/17/2005 -0400, you wrote: Your 5 and 9 below seem to me to be the same item. Not so --Joan [EMAIL PROTECTED] 06/16/05 10:41 PM Here is the agenda for the upcoming 2005 meeting of the R S Cataloging Commitee of the Association of Jewish Libraries (4-5 PM, June 19).We have a very full list of items and will start as close to 4:00 as possible.Many, manyt thanks to Daniel Lovins for providing the minutes from the 2004 meeting. Heidi Lerner (Chair, RS Cataloging Commitee) Agenda - R S Cataloging Committee Meeting - June 19, 2005 1. Welcome, Introductions, Approval of Minutes of June 20, 2004 meeting, 4-5pm EST, Brooklyn Bridge Marriott, New York City (5 minutes) 2. Hebraica Cataloging Manual (Update) - Joan Biella, Steve Bernstein (10 Minutes) 3. Review of Forthcoming RDA Drafts - (Lenore Bell, Heidi Lerner (5 minutes) 4. Judeo-Arabic Romanization Table (Draft) - Joan Biella (5 Minutes) 4. Date of Publication in Hebrew Script - Daniel Lovins (5 minutes) 5. Romanization of Place-Names with Yiddish spelling in Hebrew contexts - Joan Biella (5 minutes) 6. Use of Judeo-German in MARC Code Lists for Languages, LCSH - Daniel Lovins ( 5 minutes) 7. Use of Niborski's Verterbukh fun loshn-koydesh-shtamkike verter in Yidish as a Guide for the Romanization of Yiddish words of Hebrew Origin not found in Weinreich - Aaron Taub (5 minutes) 9. Non-Hebrew/Aramaic Place-names in Hebrew Contexts (Leykvoud, Bilgoraya ) - Joan Biella (5 minutes) 10. Other Items (5 minutes) Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford University Libraries Stanford, CA 94305-6004 ph: 650-725-9953 fax: 650-725-1120 e-mail: [EMAIL PROTECTED] Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: Agenda for RS Cataloging Meeting
FYI - At the RS Cataloging Panel on Tuesday 6/21 3:45-5:15 I will be presenting a paper: Anticipating the use of Hebrew Script in the LC/NACO Name Authority File The MARC 21 Format for Authority Data permits non-Roman scripts to be used in authority records. LC/NACO Name Authority File (NAF) records are currently restricted to Latin script because not all NAF distribution recipients (who hold synchronized copies of the NAF master file) offer support for non-Roman scripts. Headings in the NAF are established according to AACR2 and LCRIs so headings from Hebrew script sources must be romanized. This paper looks ahead to when we can use Hebrew and other scripts in authority records. The options for using Hebrew script in MARC 21 authority records are examined. The prospects for cooperative authority work between American libraries and libraries in Israel are considered. Some of the issues that Daniel and others are bringing on Heb-NACO will be examined during the presentation. I hope that we will have time for discussion after the presenations at that session. I will add the issue of Hebrew dates in the parallel 260 field to the agenda for the RS Cataloging Committee. Heidi - Original Message - From: Caroline R. Miller [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Monday, June 06, 2005 9:08 AM Subject: Re: Agenda for RS Cataloging Meeting When I attended ALA in Orlando last year I was at the Authority Control in the Online Environment Interest Group (ACIG) meeting and heard Barbara Tillett speak on LC's ultimate plan to add non-roman scripts to the authority file when they came up on the Unicode version of Voyager. I believe she was referring to adding non-roman scripts in 4xx fields in authority records but I could be wrong. I had also heard Ann Della Porta of LC say the same thing at ALA Midwinter in San Diego in 2004. Maybe Barbara Tillett is now too busy with RDA (i.e. Resource Description and Access-- new name for AACR3) to be dealing with this issue right now. UCLA has been up on the Unicode version of Voyager since July 2004. We have been loading CJK and Arabic records in from OCLC and I am not aware of any formatting problems. OCLC is implementing Hebrew, Cyrillic, and Greek in September of 2005. Daniel, I'll let you know more if I see any problems once we start loading Hebrew script records from OCLC. --On Monday, June 06, 2005 11:00 AM -0400 Joan C Biella [EMAIL PROTECTED] wrote: Daniel. Do you think we might have time to talk about Unicode formatting of bi-directional fields? Or perhaps this is too systems-specific for a catalogers meeting? Jerry Anne raised the question today about whether the parallel 100 field ought to have a [nun] rather than a b. in subfield $d, wondering about the long-term display and data processing implications. I realize that the very idea of Hebrew-script controlled vocabulary access points is problematic (in a way that, say, the imprint data in the 260 isn't) since in this there's no Hebrew-script controlled vocabulary to draw on. But it reminds me of how often the question comes up about bidirectional script, Unicode formatting characters (which I think I've got a handle on), and general guidelines for producing national-level multi-script records. Joan. I think you're talking about the whole big idea of a controlled nonroman authority file, including controlled vocabulary (and I assume control would include decisions on what brand of dates, what kind of characters to write them in, etc.). As you know, LC has (up to now) stated categorically that it did not intend to sponsor a project to control nonroman headings. However, there are definitely libraries out there that do*I've never paid attention to which ones, but you can tell from the style of their nonroman headings that they do. In the new day of floating authority records, or whatever the official term is for Barbara Tillett's concept, I'm not sure the categorical refusal of the past will have any relevance*I mean, why restrict IN ANY WAY the references people want to make? Why SHOULDN'T they use non-Latin digits to record dates, and so on? (Heidi, being the researcher on the subject, maybe knows why, but I don't.) Setting this aside, though, there's no rule to forbid a library, or group of libraries, from deciding to create a controlled nonroman authority file for its own use. (LC might or might not be allowed to participate*if not, it would be on the grounds that controlling yet another file would take too much time and energy, which has always been the rationale against it.) So AJL is free to do so, as far as I can see. LC-slash-AACR2 (who knows about AACR3?) would have no way to prevent it, and wouldn't even want to (I mean, we've never told the libraries that already do it, not to do it.) Somebody*you?--would have to round up some libraries and get them to agree
Re: Agenda for RS Cataloging Meeting
Yosi, please bring that list to the RS
Cataloging Committee meeting if you are attending.
What would we do with chronograms if that is the
only form of data of publication [printing, distribution ... et al.l],
etc.
The best nodel that I have seen is the Bibliography
of the Hebrew which includes the Gregorian date andHebrew calendar
date in its various permutations in its bibliographic records.
Heidi
- Original Message -
From:
Yossi Galron
To: heb-naco@lists.acs.ohio-state.edu
Sent: Monday, June 06, 2005 10:56
AM
Subject: Re: Agenda for RS
Cataloging Meeting
I am totally in agreement that in the
Hebrew/Yiddish 260 field we should transcribe the date in Hebraic letters and
not convert the date to numerals (i.e. tav-shin-samekh-he and not 765. If
there is no regular date we should continue add in brackets [2004 o
2005] In Hebrew - alef-vav, and not "or" in
EnglishSee for example:http://library.ohio-state.edu:8081/search/o?SEARCH=19165459I
would also have a list of Hebrew abbreviations we use in cataloging for the
Hebrew fields: not "ca." but "be-erekh" in dates, Not
d. died but "met" or "nif." niftar ; Not b.
born, but no. nolad, etc.I have also my opinion on a
Hebrew Authority file ... but this we will probably discuss in
Oakland.YossiAt 12:16 PM 6/6/2005, you
wrote:Daniel: In a similar vein, I wonder if we
should discuss the possibility of entering the real Hebrew date (i.e., in
Hebrew characters) in the parallel 260, since the Gregorian date and
transliterated (trans-numerated?) Hebrew date have already been captured in
the Romanized field, and since we provide a more faithful transcription this
way, and since it would cut down on the number of bi-directional
subfields.Joan:
This idea is not likely to fly on a national scale as long as AACR2 specifies
roman expressions like "c" (for copyright date) and "or" (for complex date) in
the 260$c. Though RLIN21 makes the Unicode Western-style numerals
available from the Hebrew character set, these other things can't be provided
without left-to-right input. Hebrew "equivalents" for the problematic
strings ("o" for "or" and the like) make the departure from AACR2
obvious.Steven: I
have always been under the impression that the scope of the AACR is limited to
Roman script records for use by English speakers. Vernacular non-roman
script records--since they cannot be used by the standard English speaker--are
not of any concern to the AACR. Our general approach to cataloging,
which combines Roman script fields (which follow the AACR standard) with
parallel vernacular fields (which do not follow the AACR standard) has
neccesitated that we apply AACR standards to parallel vernacular fields so
that our records have a feeling of consistancy. In applying the AACR to
non-English fields, we have the option to "replace the [rules'] specified
preference for English by a preference for [our] working language" (AACR2
0.12). Entering the real Hebrew date (i.e., in Hebrew characters)
in the vernacular 260 would be allowed because it is the preference for our
working language.I am, of course, a relative rookie in this field and my
impressions and understandings on this matter could be completely off.
Thoughts? Comments?- Original Message - From: "Joan C Biella" [EMAIL PROTECTED]To:
heb-naco@lists.acs.ohio-state.eduSent: Monday, June 06, 2005 11:00
AMSubject: Re: Agenda for RS Cataloging MeetingDaniel. Do you
think we might have time to talk about Unicode formatting of bi-directional
fields? Or perhaps this is too systems-specific for a catalogers
meeting? Jerry Anne raised the question today about whether the parallel
100 field ought to have a [nun] rather than a "b." in subfield $d, wondering
about the long-term display and data processing implications. I realize
that the very idea of Hebrew-script controlled vocabulary access points is
problematic (in a way that, say, the imprint data in the 260 isn't) since in
this there's no Hebrew-script controlled vocabulary to draw on. But it reminds
me of how often the question comes up about bidirectional script, Unicode
formatting characters (which I think I've got a handle on), and general
guidelines for producing national-level multi-script records. Joan. I
think you're talking about the whole big idea of a "controlled nonroman
authority file," including controlled vocabulary (and I assume "control" would
include decisions on what brand of dates, what kind of characters to write
them in, etc.). As you know, LC has (up to now) stated categorically
that it did not intend to sponsor a project to control nonroman
headings. However, there are definitely libraries out there that do*I've
never paid attention to which ones, but you can tell from the style of their
nonroman headings that they do.In the new day of
Fwd: RLIN NACO Contributors - RLIN21 Client for NACO Updated Schedule
Please below regarding change of schedule for RLIN21 client for NACO Heidi X-Sieve: CMU Sieve 2.2 From: News from RLG [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RLIN NACO Contributors - RLIN21 Client for NACO Updated Schedule Date: Thu, 19 May 2005 13:05:30 -0700 X-Mailer: Microsoft CDO for Windows 2000 Thread-Index: AcVcrhtem45LLFZHTRS1FCBGmIUX8w== X-OriginalArrivalTime: 19 May 2005 20:05:30.0338 (UTC) FILETIME=[1B61B420:01C55CAE] Subject: RLIN NACO Contributors - RLIN21 Client for NACO Updated Schedule To All RLIN NACO Liaisons: The authorities service disruption announced on May 9 has been deferred by one week. The updated schedule: -- You will still need to use RLIN Terminal for Windows to contribute name authority records to the LC/NACO authority file until Wednesday, May 25, 9:00 pm Pacific Time (instead of May 18). -- The RLIN21 client for NACO will become available on Monday, May 23, 9:00 am Pacific Time. When you try to log on anytime after that, you will see a notice that you are required to download the update before you can continue working. If you are not already using an RLIN21 client, you can download the software from the RLG Web site anytime after 10 am Pacific Time. Check the Post-Migration Services Update page on the RLG Web site for a link to the new software, at: http://www.rlg.org/en/page.php?Page_ID=400 == Note: You will not be able to use the new client to create or update name authority records until May 31. -- The LC/NACO and LC/SACO authority files will be available for searching until Friday, May 27, 9:00 pm Pacific Time. == There will be no access to the LC/NACO and LC/SACO authority files from May 27, 9:00 pm Pacific Time through May 30, 11:59 pm Pacific Time. -- Full service will resume Tuesday, May 31, 12:01 am Pacific Time. You will need to use the RLIN21 client to create, update, and contribute name authority records to the LC/NACO authority file. If you have any questions, please contact the RLG Information Center at [EMAIL PROTECTED] Karen Smith-Yoshimura RLG 29563 Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Fwd: RLIN database almost current and most records can be updated
See below for latest update from RLG about their loading of records created and updated between 11/18/04 and 2/25/05. X-Sieve: CMU Sieve 2.2 Subject: [rlg-services-forum] May 1 post-migration update To: RLG Services Discussion Forum [EMAIL PROTECTED] X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 From: [EMAIL PROTECTED] Date: Sun, 1 May 2005 23:00:40 -0700 X-MIMETrack: Serialize by Router on Notes/RLG(Release 5.0.13a |April 8, 2004) at 05/01/2005 11:00:41 PM List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Subscribe: mailto:[EMAIL PROTECTED] List-Owner: mailto:[EMAIL PROTECTED] Reply-To: RLG Services Discussion Forum [EMAIL PROTECTED] X-Message-Id: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] RLG members and customers: A May 1 update was just posted to http://www.rlg.org/en/page.php?Page_ID=400 What's new: --All RLG Union Catalog users: All the records added and updated to the old catalog between November 18, 2004 and the end of February 2005 are now current in the new, migrated database, except for approximately 137,000 continuing resources (serials) additions and updates; those are being applied. --RLIN21 client users: All your records are now accessible for updating except for serials records entered prior to March 1, 2005. We expect these to be accessible to you by May 9. Thank you for bearing with us as this post- migration work has progressed. --- Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: hotem/hotam tokhnit
Zephania 3:9 has safah verurah and Even-Shoshan has ad she-hayetah mishnato berurah [Agnon); leshonah beruah [Burla]. Heidi At 11:29 AM 4/7/2005 -0400, you wrote: Paul M. points out that it DOES matter which form goes into the 245 and which goes into the 246, since some systems out there may not index the 246, and RLIN definitely uses the 245 for clustering records for the same book together. This being the case, I strongly recommend putting the biblical romanization in the 245 and the common romanization in a 246. I was a bit worried about how some libraries say Mishnah verurah instead of Mishnah berurah--that would entail quite a cleanup! But it seems Mishnah verurah is not biblical. Can anyone tell me what it does come from, and if verurah is in any powerful sense better than berurah? Joan [EMAIL PROTECTED] 04/06/05 7:12 PM Dear Group, Here's another one I came across today: Hotem tokhnit vs. Hotam tokhnit. 7 clusters in RLIN for the first, 5 for the second, some of them for the same title. Hotem tokhnit is taken from a verse in Ezekiel. In this case, it's clear which is the correct form. I guess we should still do a 246 for the variant, to aid the masses, n'est ce pas? Barry Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: yod'e binah/yod'e vinah
I have always trascribed these types of titles as they appear in a standard,vocalized Tanakh. If I find the source of such a title in a concordance, I will then go to the verse and transcribe/romanize the title for the catalog record as it appears in the Tanakh.. In this case I would have transcribed the title of the journal Yod'e vinah. Others?. Heidi - Original Message - From: Barry Dov Walfish [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Monday, April 04, 2005 4:03 PM Subject: yod'e binah/yod'e vinah Dear Group, How should one transcribe book titles that are taken from biblical verses. Do biblical grammar rules trump those of Modern Hebrew grammar? E.g., I recently came across the title of a journal entitled Yod'e vinah. The phrase is taken from the verse in I Chronicles 12:32 umi-Bene Yisakhar yod'e vinah la-itim. I found a few clusters in RLIN under Yod'e binah, none under Yod'e vinah. I am sure there are other similar examples. What to do? Barry
Re: a new romanization opportunity?
I will ultimately follow whatever decision LC staff make. I have one major concern that is not linguistic: I am unable as a cataloger to make global changes, either in my local system, or in RLIN21. If we are to change the practice or rules for transcription of these types of words, we will have ongoing maintenance to carry out in our romanized recordsin our local systems and in our institution's contributed records to the RLG Union Catalog. I cannot expect or ask Stanford's database management or systems staff to make these kind of global changes, if indeed it is possible. I do not have the time to constantly change volumes of records to reflect every policy ratification that we make regarding romanization. I am happy to manually correct romanization errors when a. they are either pointed out to me by other catalogers b. the AJL Cataloging Committee, Library of Congress, or in some cases we as a group make a careful and agreed-upon decision to introduce a change in our romanization practices Heidi - Original Message - From: Joan C Biella [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Wednesday, March 30, 2005 11:37 AM Subject: Re: a new romanization opportunity? I have carefully reread the section of HCM (p. 17-18) dealing with schwa na' which is not romanized, and I don't think either of the types discussed fits the case of mun(e)he. 1) Schwas occurring between the 2nd and 3rd consonants of the plural forms of participles, nouns, etc. and other verb forms of the pa'al/kal, pi'el, and hitpa'el binyan. Munah is a participle of the hof'al binyan, and the consonant with dagesh is the 1st of the root, not the 2nd or 3rd. Since the actual 2nd consonant of the root, vav, doesn't appear at all you might THINK nun was the 2nd and het was the 3rd, if you didn't pay close attention, though. (Let's face it, this is a weird form!) 2) Schwas occurring between the 2nd and 3rd consonants of certain plural nouns in the construct state where the schwa is also the result of vowel reduction. Well, we're dealing with a plural noun in the construct state, and the schwa is the result of vowel reduction (kamets in munah schwa in mun(e)he), but again the schwa doesn't occur between the 2nd and 3rd consonants of the root--unless you stretch a point, as I suggest above. I suppose that generations of catalogers have said munhe and musge by analogy with one or the other of these rules, though. My questions: 1) Shall we let sleeping dogs lie and go on saying munhe and musge? 2) Shall we start saying munehe and musege? 3) Shall we point out these forms in the new edition of HCM? Re 3), I'm reluctant to do so, and also reluctant to create a list of words not romanized according to our rules, which is the sort of thing that can get way out of hand. How do you all feel? Joan Stanley Nachamie [EMAIL PROTECTED] 03/29/05 10:58 PM You wrote: Can anyone give me a good argument as to why we should continue to romanize these words as munhe and musge? Aren't there many cases when LC disregards the sheva na` in romanization? -Stanley Nachamie [EMAIL PROTECTED]
Re: u-politit/ u-folitit
Sure! And you RLIN catalogers - how are things going today (3/25?). After three good days things here are back to their normal RLIN21 not working frustration. Heidi At 11:44 AM 3/25/2005 -0500, you wrote: I am loath to institute a practice REQUIRING everyone to check Even-Shoshan for treatment of doubtful words--for the simple reason that doubtfulness thresholds vary and not everyone will apply the practice to the same words. Let's say instead that if anyone NOTICES this kind of exceptional treatment of an initial labial consonant in Even-Shoshan's usages, that person will notify Heb-NACO. Words not proved by means of Even-Shoshan to be exceptions should continue to be treated as unexceptional. Heidi, can you start an online list to keep track of these exceptions? I'll work on fixing any LC u-folitik... that I can find. Joan [EMAIL PROTECTED] 03/24/05 3:43 PM Even-Shoshan has u-poli.ti.kah. RLIN has 51 clusters with u-foli.ti.kah and 78 clusters with u-poli.ti.kah Should we establish a practice whereby we look first in Even-Shoshan? If Even-Shoshan provides us with an example of one of these types of words, we transcribe it as it appears. If a foreign loan word beginning with b/v, k/kh, p/f does not appear with a prefix in Even-Shoshan,perhaps we should develop some sort of guideline governing its transcription. Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: u-politit/ u-folitit
Even-Shoshan has u-poli.ti.kah. RLIN has 51 clusters with u-foli.ti.kah and 78 clusters with u-poli.ti.kah Should we establish a practice whereby we look first in Even-Shoshan? If Even-Shoshan provides us with an example of one of these types of words, we transcribe it as it appears. If a foreign loan word beginning with b/v, k/kh, p/f does not appear with a prefix in Even-Shoshan,perhaps we should develop some sort of guideline governing its transcription. At 09:48 AM 3/24/2005 -0500, you wrote: Found these: Ravitzky, Aviezer. Title: ha-Kahanaut ke-tofaah todatit u-poli·tit / Aviezer Ravits·ki. Publication info: Yerushalayim : Sifriyat Shazar, ha-Makhon le-Yahadut zemanenu, ha-Universi·tah ha-Ivrit bi-Yerushalayim, 1985. 2 others as well. Giladi, Dan Title: ha-Yishuv bi-te·kufat ha-aliyah ha-reviit (1924-1929) : be·hinah kalkalit u-foli·tit / Dan Giladi. Publication info: Tel-Aviv : Am oved - Tarbut ve-·hinukh, 1973. I couldn't get into LC's catalogue this morning, but I assume they're both LC records. Barry Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
u-fo'etit or u-poetit
Dear group, Would vov,peh,vov,alef,tet,yud,tav be transcribed as u-po'etit or u-fo'etit. I am guessing u-po'etit but would like to hear from others. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: karel-bakhrakh
I would suggest that you transcribe it as Kar'el. I found a romanized form for her in the Weinberg catalog at http://www.aiweinberg.com/cgi-local/shop.pl/page=cat-513.html. It may not an authoritative source but it does offer support for that romanization. You can make references from Karal and Kerel and code the record as provisional. At 09:12 AM 3/21/2005 -0800, you wrote: folks: i'm establishing the author of resise hayim, one yael [Karel]-bakhrakh. as you no doubt may have guessed, the [karel] portion of the name is giving me a bit of difficulty. the name is spelt kof-resh-alef-lamed. karel seems a likely possibility, but then again, so does kerel and karal. please, help me avoid creating a provisional record. thanks in advance. b Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Hebrew Naco Funnel Revisions
To: Hebrew Naco Funnel Contributors Due to continuing problems with RLIN21, I am not be able to revise your NACO contributions at this time. Please do not send me any headings for revision until further notice. We hope that these problems are temporary and that we can continue our work as soon as possible. Thank you, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Le-hayim or Le-hayem
Dear Group, When I have lamed,het,yud,mem sofi in a Yiddish context would it be transcribed as: Le-.hayim or Le-.hayem. This would be as a toast and not giving something to a fellow named Hayem. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: Lekhaim [le-hayim]
Thanks to all the respondees (Bob, Stanley, Zachary). I think that le.haim is the way to go. Have we come to a consensus on how to handle the hypen that would appear in Hebrew transcriptions? I believe that Bob has suggested that we not include the hyphen when Weinrich enters these under their prefixes. Heidi - Original Message - From: Zachary Baker [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Monday, February 28, 2005 4:25 PM Subject: Lekhaim [le-hayim] In my copy of Weinreich's dictionary it reads: LEKHAIM, with ai constituting dieresis (i.e., no intervening consonant between the two vowels). Niborski also transcribes it (in Hebrew letters) LEKHAIM. Zachary Baker
Re: Book's title
Any chance that it might be Merupasin igari? Just a wild guess. At 01:30 PM 2/25/2005 -0500, you wrote: Once again, I have to admit my ignorance in public. How should one Romanize the following title (and what does it mean)?: Sefer mem-resh-pe-samekh-yod-nun alef-yod-gimel-resh-yod (the book includes meot kushiyot atsumot ve-terutsim niflaim me-et gedole ha-dor [al ha-Torah]) Thanks, Rachel Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Fw: RLIN NACO Contributions Post March 1, 2005
- Original Message - From: News from RLG [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 22, 2005 9:39 AM Subject: RLIN NACO Contributions Post March 1, 2005 Subject: RLIN NACO Contributions Post March 1, 2005 To All RLIN NACO Liaisons: Starting March 1, 2005 only the call rlin(aut) command will work when you log onto RLIN Terminal for Windows, allowing RLIN NACO contributors to continue to submit name authority records to the LC/NACO authority file until the RLIN21 client support for NACO is available. All cataloging functions will be supported only in the RLIN21 client. You will still use your current RLG accounts to logon. You will be looking at the same authority databases as you see now, not yet migrated. They are the same authority databases available in the RLIN21 Web and RLIN21 client interfaces. You will still be able to retrieve pending and saved authority records after March 1. You will be able to call rlin(cat) within an RLIN NAF session to generate an authority record from a bibliographic record. Those of you who generate an authority record from a bibliographic record in your local system (sel fil loc) can continue to do so. *** Note that the eight bibliographic files of the current RLG Union Catalog will be frozen as of Friday, February 25. You will not be able to generate an authority record from a bibliographic record created in the RLIN21 client starting March 1. *** We have made the catalog function available to RLIN NACO users solely for generating authority records. ALL NEW CATALOG RECORDS OR BIBLIOGRAPHIC RECORD UPDATES MUST BE DONE IN THE RLIN21 CLIENT! Bibliographic records you attempt to create or update with RLIN Terminal for Windows will not be processed We apologize for the inconvenience during this final transition period. All production NAF records you contribute using RLIN Terminal for Windows will be available to RLIN21 Web and RLIN21 client searchers of the LC/NACO authority file after distribution by LC. We will keep you abreast of RLIN21 client NACO developments in future communiqus. Karen Smith-Yoshimura RLG 20242
contribute article on cataloging to AJL Newsletter
Dear group, Would any of you like to contribute on article on some aspect of Hebraica cataloging to the AJL Newsletter? The editors are looking for material from RS members and our community was tapped. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
[Fwd: [PCCLIST] Status of the LCRIs]
X-Sieve: CMU Sieve 2.2 Date: Mon, 14 Feb 2005 13:54:04 -0800 From: Joanna K. Dyla [EMAIL PROTECTED] User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en To: Inna Gudanets [EMAIL PROTECTED], Kay Teel [EMAIL PROTECTED], Heidi G. Lerner [EMAIL PROTECTED], pjrolla [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] CC: Catherine Tierney [EMAIL PROTECTED], Vitus Tang [EMAIL PROTECTED] Subject: [Fwd: [PCCLIST] Status of the LCRIs] Original Message Subject: [PCCLIST] Status of the LCRIs Date: Fri, 11 Feb 2005 18:33:18 -0500 From: Ana Lupe Cristán [EMAIL PROTECTED] Reply-To: Program for Cooperative Cataloging [EMAIL PROTECTED] To: [EMAIL PROTECTED] Posted to multiple lists with apologies for the duplication Status of the Library of Congress Rule Interpretation (LCRIs) In response to inquiries on the current and future status of the LCRIs, the Cataloging Policy and Support Office at the Library of Congress reaffirms that, until such time as the 2nd edition of the Anglo AmericanCataloguing Rules (AACR2) ceases to be the standard used for creating bibliographic and authority records by LC and its PCC partners, the LCRIs will continue in force and this documentation will continue to be issued and maintained as necessary. There is a concerted effort underway to update and simplify all LC cataloging policy documentation, including the LCRI's, with a possibility for a different sort of cataloging policy series as AACR3 commences. The Library hopes soon to survey current subscribers to the LCRIs and other cataloging documentation regarding their suggestions on improvements to LC's cataloging tools. Announcements to the appropriate discussion lists will be issued at that time. Please direct questions or suggestions to [EMAIL PROTECTED] Barbara Tillett Chief, CPSO Library of Congress -- Joanna K. Dyla Head, MARC Unit Cataloging Metadata Services Stanford University Libraries 650-723-2529 [EMAIL PROTECTED] Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: subject question
Dear Stanley, Thank you for the information below. I am also wondering where to class this. Would this material be classed with special elements of the liturgy, i.e. BM670? There is no special cutter for Seder Korbanot. My volume does include the Seder Tashlikh which does have its own special cutter BM670.S42. Should I propose a cutter? Thanks, Heidi At 07:26 PM 2/7/2005 -0800, you wrote: I hope you get some better answers, but an important thing is to determine what is meant by Yom shelosh esreh midot. I think it might refer to a specific day of Selihot between Rosh Hashanah and Yom Kippur. (Other things imply that it might be specifically referring to Erev Yom Kippur.) If Tashlikh isn't said on the 1st or 2nd day of Rosh Hashanah, it may be recited any time before Yom Kippur. Kaparot can also be performed/recited any day between Rosh Hashanah and Yom Kippur, although Erev Yom Kippur is the best day. The minchah of Erev Yom Kippur is special in that the Vidui is recited by the congregation in the silent `Amidah. Maybe the korbanot section of the morning prayers is changed by some on Erev Yom Kippur, but that is only a conjecture. Hope this helps, or at least moves others to respond. -Stanley Nachamie [EMAIL PROTECTED] Heidi G. Lerner wrote: I have a book Seder ha-Korbanot ve-Seder Tashlikh le-Yom shelosh esreh midot : kolel Seder ha-Korbanot, Seder Tashlikh, Seder Kaparot, tefilat Minhah ... . What would be the best subject analysis? High Holidays--LIturgy--Texts Tashlikh Judaism--Liturgy--Texts Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
subject question
Dear Group, I have a book Seder ha-Korbanot ve-Seder Tashlikh le-Yom shelosh esreh midot : kolel Seder ha-Korbanot, Seder Tashlikh, Seder Kaparot, tefilat Minhah ... . What would be the best subject analysis? High Holidays--LIturgy--Texts Tashlikh Judaism--Liturgy--Texts I am not sure if the above is correct or complete. Any help will be appreciated. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: Two More Yiddish Names
Dear Bob, Urye is on the current list. Please see the following URL for the most up-to-date version: http://library.stanford.edu/hebraicafunnel/Yiddish_Forenames_20040703.htm Thanks, Heidi - Original Message - From: Robert Talbott [EMAIL PROTECTED] To: heb-naco@lists.acs.ohio-state.edu Sent: Thursday, February 03, 2005 2:25 PM Subject: Re: Two More Yiddish Names actually, since someone else has raised it, i'd like to have uryeh added as well. it is also in beider under urye. the hebrew is, of course, uriyah. may vowels always be present, b At 02:24 PM 2/3/2005 -0500, you wrote: Dear Heidi and Group, I recently came across two more Yiddish names of Hebrew or Aramaic derivation. Both are in Beider's Dictionary: Ezre (Heb.: Ezra) and Yoyer (Heb.: Yair). Heidi, can you add them to the Funnel's Yiddish personal names list? Many thanks, Aaron
Hebrew script on RLIN
Dear Safranim, I would like to know which libraries are currently contributing Hebraica records (Hebrew and other Jewish languages written in Hebrew characters) into RLIN (either cataloging directly into RLIN or uploading from a local system) utilizing the RLIN Hebrew script capability. It does not matter whether catalogers are using RLIN Terminal for Windows or the new RLIN21 client. If your institution is contributing Hebrew-script records to RLIN, could you please contact me privately, one response per institution. I would also like to have the name or contact information for the principal or head cataloger of your institution's Hebraica cataloging team. Please excuse duplication to other lists to which this query may be cross-posted. Thank you in advance for your prompt response. Heidi Lerner Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Fwd: PCC Web Site Availability
X-Sieve: CMU Sieve 2.2 X-Mailer: Novell GroupWise Internet Agent 6.5.2 Date: Tue, 25 Jan 2005 16:15:38 -0500 Reply-To: Program for Cooperative Cataloging [EMAIL PROTECTED] Sender: Program for Cooperative Cataloging [EMAIL PROTECTED] From: Antony Robert David Franks [EMAIL PROTECTED] Subject: PCC Web Site Availability Comments: To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] PCC Web Site Availability The Cooperative Cataloging staff has been receiving inquiries about the operability of links, interactive forms, and other aspects of the PCC Website. In response to becoming fully compliant with the Library of Congress' Office of Strategic Initiatives, and in response to suggestions offered by PCC participants, the PCC Website is currently undergoing extensive renovation and redesign in an effort to enhance uniformity and improve content placement. These efforts coincide with an internal project for the restructuring of the entire LC Web presence. The PCC Secretariat and the Cooperative Cataloging Team staff wish to apologize for the temporary inconvenience and remain hopeful that the new look will be representational of the forward-looking goals on which the PCC plans to embark. Anthony R.D. Franks Team Leader, Cooperative Cataloging Team Library of Congress 202-707-2822 (voice) 202-252-2082 (fax) Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
help with acronym
Dear Group, How do we transcribe the acronym gimel,alef,bet,geresh,daled. Would it be ga'avad or g. a.b.d. Thanks,Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: help with acronym
Thanks, that is what I suspected. Heidi At 02:49 PM 1/13/2005 -0500, you wrote: g.a.b.d. stands for ga'on av bet din. If you check Even-Shoshan, your will see that it is not vocalized, so it has to be: g.a.b.d. Yossi At 02:10 PM 1/13/2005, you wrote: Dear Group, How do we transcribe the acronym gimel,alef,bet,geresh,daled. Would it be ga'avad or g. a.b.d. Thanks,Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120 - Joseph (Yossi) Galron-Goldschläger Head of the Hebraica Jewish Studies Library The Ohio State University Libraries, 324 Main Library, 1858 Neil Ave. Mall, Columbus, OH 43210 USA E-Mail: mailto:[EMAIL PROTECTED] Tel.: (614) 292-3362, Fax: (614)292-1918 URL: http://www.lib.ohio-state.edu/jdc/jdc.html Check my new project at: http://library.osu.edu/sites/users/galron.1/ Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
diacritic alif and ayin in RLIN21
Dear Group, Stanford has finally started using RLIN21. I am aware that we input diacritics after the letter. Does also hold true for alif and ayin. For example, in the word be'ur, would I input the alif after the e or u. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Neenah
Dear Group, A scholar inquired about the meaning of nun,alef,nun,het which appears on the following book: Derush al aseret ha-dibrot. Bendit Akselrod ben Yosef ha-Levi. Hanau, 1616. The context is as follow: ... ne'ena.h [ha-mevi li-defus] Aharon Shemu'el ha-.k. ben ... Mosheh Shalom. I am transcribing the title information as it appears in the Biblography of the Hebrew Book. Any thoughts on what it might mean would be appreciated. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
out of the office
Dear funnel members, I will be out of the office from Dec. 17-Jan. 2. I will be back at work Jan. 3. Please do not send me any headings during that period. Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Re: Isaac Abendana
Dear Stanley, In this case I think that we should not add birth and death dates to the heading. We have two different sets of dates in the 670s provided and we would need a third source to break the conflict. We do not need to add dates to this heading because it does not conflict with any extant headings or references in the authority file. Heidi At 12:26 PM 12/1/2004 -0800, you wrote: Heidi wrote: I think that what we have here are two different people. The extant NAR I believe should be modified to 100 1 Abendana, Isaac snip 670 Ency. Judaica, c1972$b (Abendana, Isaac, c. 1640- c. 1710; snip If this record has to be modified anyway, might you not want to add the dates to the 100 line, to prevent any confusion in the future? Or is that against some rule, or would it require greater BFM work? Thanks. -Stanley Nachamie [EMAIL PROTECTED] Authority Control Librarian (currently on leave) City University of New York Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
Funnel Statistics
FYI - From John Mitchell at the Library of Congress: The PCC Statistics are now completed for each individual institutional participant and each funnel project and are available at: http://www.loc.gov/catdir/pcc/stats/total04.pdf ; the statistical overview for the PCC has been updated, reflecting all of FY04 and those statistics are available at: http://www.loc.gov/catdir/pcc/stats/totalstatsfy04.html Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
help with form of name
Dear Group, I have a book published in Casablanca in 1945 or 1946. The form that appears on the 1st page of the book (cover title) which has some publication information is Yitshak ha-Levi ben Tsefat. It appears in a form for offering the book to interested parties me-et ha-tsair Yitshak ha-Levi ben Tsefat ... . Is this location of data considered prominent? I am not sure how to establish this. I have never seen Tsefat used as a personal name. On p. 3 of the introduction, we have Yitshak ben la-a. a. Avraham ha-Levi ben Tsefat. Should it be Yitshak ben Tsefat, ha-Levi Halevi, Yitshak ben Tsefat Yitshak ben Avraham, ha-Levi Thanks, Heidi Heidi G. Lerner Hebraica/Judaica Cataloger Catalog Dept. Stanford Univ. Libraries Stanford, CA 94305-6004 e-mail: [EMAIL PROTECTED] ph: 650-725-9953 fax:650-725-1120
