Print

Print


The second example under 2.5.2.3. is a corporate name with words spelled 
out in romanization but abbreviated in the Hebrew-script parallel 
field.  (Also Sokhatshov may be spelled wrong in Hebrew?)  To keep 
things simple I would replace it with an example where the Hebrew and 
the romanization correspond exactly.  I've found another example in the 
authority file that illustrates the same point (attached).

Robert.

Fletcher, Peter wrote:
>
> All, please find attached a close to final draft of our document for 
> PCC non-Latin guidelines in bib. records (good news, it is only 16 
> pages). Also, will send by tomorrow as attachment the report that goes 
> with it, also in a hopefully nearly final form. [I am enclosing this 
> also as an attachment since some of my formatting may not survive in 
> your emails; hopefully a .doc will preserve the bullets and underlines 
> to make this easier to read]
>
>  
>
> Please check/keep in mind:
>
> ·         _Check your language examples:_ (I can only check the 
> Cyrillic); *especially check the right to left scripts*, since I gave 
> up trying to replicate the OCLC right to left (starting from the right 
> hand side of the screen) and some of the letters/words have become 
> reversed, etc. (someone please check the example of the different 
> filing indicators in the Arabic/French title example on p. 4). I added 
> the example  in 2.5.1. of “730 0# ǂa Ali Baba (Folk tale)” as one of 
> the examples of headings in conventional form and not normally 
> provided with parallel non-Latin data. I also added a few examples in 
> the 2.5.1 section (a 130 videorecording example; and a 240 
> non-translation example for the Persian work)
>
> ·         _Google docs comments_: I incorporated most (96.5%?) of your 
> comments/examples into the text, or a compromise if more than one 
> commented on the same thing, so if you wish and you have time, please 
> check to see if you are satisfied that I incorporated them correctly 
> (you will have to do a comparison with the document at the Google site 
> (it would have been too unwieldy, and probably unintelligible, if I 
> attempted to do track changes with this attachment)
>
> ·         _Descriptive fields section 2.3 slightly reorganized_: I 
> numbered the sub-section of 2.3. Descriptive fields, 2.3.1, for mixed 
> script fields, which includes also the guidelines on characters 
> outside MARC-8, which itself is numbered 2.3.1.1. (this illustrates 
> that these fields fall within the parent rules).
>
> ·         _Headings section renumbered_: I renumbered the 2.5 heading 
> section along Robert’s recommendations/revisions.    
>
> ·         _MARC tag order_: each logical section of examples all are 
> in MARC tag order where practical.
>
> ·         _Terminology_: the terms non-Latin, romanization (romanized, 
> etc.) are used throughout. There may be some instances where speaking 
> of “transliteration” were appropriate.
>
> ·         _Fonts/spacing_: I have made the document consistent with 
> fonts, spacing, etc.
>
> 1.    the word “Example(s)” is in italics with a colon introducing an 
> example or examples sections
>
> 2.    numbered section headings are in bold (except for sub-sections 
> in 3. Special language or script guidelines)
>
> 3.    some special paragraphs have an underlined introductory phrase 
> (such as “Macros and automatic transliteration)
>
> 4.    Examples, typically showing a paired field combination, are 
> single line spaced, with bracketed explanations (in normal font) 
> mostly directly beneath the example without an extra line space. 
>
> ·         _NACO variants_: I added a recommendation in 2.5 (1^st 
> paragraph) to add variants to Name authority records as part of NACO.
>
> ·         _Cataloger-Created_: I changed the phrase 
> “cataloger-supplied” to “cataloger-created” to distinguish 
> cataloger-created parts of notes and qualifiers from the personal name 
> qualifiers that are not cataloger created, but rather added based on 
> usage of the name, and the term “supplied” could also apply.
>
> ·         _Linking entries_: I changed the instruction for linking 
> entries (removed reference to the 580 note, since the principles are 
> the same as in 2.4.: “2.5.1.2. Linking entries  (optional) (76X-78X), 
> Give parallel non-Latin script linking entry fields when the entry for 
> the linked record has been systematically romanized. I do not know why 
> the CEG requires that the linked record also have non-Latin data (or 
> that you would have to go to that record to add it). I also think we 
> should NOT worry about providing an optional approach for these fields 
> in 2.5.2. (these linking fields may be based on a descriptive 245 or 
> they may be based on a 130 U.T., or 110/245, etc., whatever the main 
> entry is for the particular serial) 
>
> ·         _Translations_: On the issue with translations that came up 
> when discussing the optional heading practice section, 2.5., I think I 
> need to apologize for creating a false problem (I must have been 
> overworked or something). If some libraries are creating parallel U.T. 
> (or any heading for that matter) in the language of the piece in hand, 
> which is not the original language of the person, work, or body, then 
> it is simply incorrect practice. I added/amended the phrasing in both 
> 2.5.2.2 and 2.5.2.1: “The headings [qualifiers] must be in the 
> language/script of the body, person, or title, and the form entered 
> can be derived from the resource itself  or if necessary from a 
> standard reference source in the language/script of the heading.”
>
> ·         _Unpaired fields_: I added in parentheses in Record 
> characteristics, right after discussion of MARC Model A: “(There are a 
> few exceptions where an unpaired non-Latin field is an appropriate 
> option, depending upon the language/script)”, just to mention this 
> early in the document, since later on there is one or two recommended 
> options of adding unpaired fields, such as 246 (a Hebrew special 
> language rule comes to mind); this is in addition to the added text in 
> 2. General guidelines that Robert/Keiko suggested and some of you 
> agreed to: “Other optional fields may be entered in Latin only, in 
> non-Latin only, or in parallel Latin and non-Latin fields.” I think 
> this all firmly establishes that required fields and headings are 
> paired whenever providing the non-Latin data for them, but outside of 
> these, pairing is optional.
>
> ·         _BIBCO standard record_: I added the text to the first intro 
> section, 2^nd paragraph: “The guidelines may be applied regardless of 
> MARC formats, however the BIBCO standard record for print monographs 
> has been applied to some examples.”
>
> ·         _Hebrew contents note example_ from Sharon I incorporated 
> into the general notes section 2.4.
>
>  
>
> Please send me your final comments ASAP either in an email or in the 
> document via email attachment using track changes on that attachment 
> and just inform me in the email where/what in the document your 
> changes/comments are (e.g., which corrected examples). 
>
>  
>
> I would like to submit this by next Thursday (Mar. 25) at the latest. 
> Sorry about the short notice, but you all have been submitting 
> excellent improvements for a while at this point, it is in a nearly 
> finished state (as far as anything ever is) so we need to wrap it up, 
> and, we are a little late submitting it. And, remember, this is meant 
> to be a regularly amended document, so if PCC accepts the document and 
> agrees to an amendment process, then revision proposals can be 
> submitted via the approved venue (I am hoping coordinated by Standing 
> Committee on Standards (who will perhaps farm it out to PCC and LC 
> experts for advise, etc., when necessary)).
>
>  
>
>  
>
>  
>
> Many thanks,
>
>  
>
> Peter
>
>  
>
>   .
>
>  
>
> Peter Fletcher
>
> Cyrillic Catalog Librarian and Metadata Specialist
>
> [log in to unmask]
>
> Office: (310) 206-3927
>
> Fax: (310) 794-9357
>
> UCLA Cataloging & Metadata Center
>
> 11020 Kinross Avenue
>
> Box 957230
>
> Los Angeles, CA 90095-7230
>
>  
>