CEAL RDA Review Comments
1. General Comments on RDA as a whole
·
My overall impression
on RDA so far is that it is not well-organized (maybe because of my aacr2
biased mind). I think as a guideline for the whole cataloging world, RDA should
be focused on cataloging principles for all cataloging agencies to follow and
give flexibilities on how to implement the rules to cataloging agency . When I looked further down to the individual
chapters, my impressions is that it mixed up with too many not well-selected examples
(some repeated again and again), redundant explanations, which didn’t make
RDA’s fundamental ideas clearer. It’s more like an expanded version of AACR2 +
LCRI with different organizations and terms to me. I didn’t see much effort
made to address internationalization issue, one of the main improvements should
be made comparing to AACR2.
· Internationalization rules not consistently addressed throughout RDA. Some rules provide specific instruction, some refer to general instruction, and some provide no instruction or reference at all. Please see the specific comments for details on instructions that should address language issues.
· There are many errors in referencing rule numbers list in some chapters (please see attachment). Some refer to wrong instruction and some refer to a section/instruction that is not existed. Suggest RDA editor to proof-read and double check referencing in all RDA to ensure accuracy
· [General comments on chapter 1-4]
o Wording: “Considered to be important” is predominantly used in chapter 1, 2 & 4.
“Considered important” is predominantly used in chapter 3.
o Too few CJK examples are in these chapters. We provided some CJK examples under specific rules.
o Typeset: Typeset of the first sentences of paragraphs after examples is sometimes different from the rest of the paragraphs.
· [General comments on chapter 5-7]
o On FRBR: For chapter 5-7, it may be helpful to include some chart images to explain relationships between different records. I had a couple of FRBR PPT slides and looked at them when I start getting confused rules about work and expression.
o On examples: I thought that the way examples are presented in chapter 5-7 was very inconsistent and not easy to read. For example, in Chapter 6, several sections have examples with the same captions such as Different Scripts, Different Languages, Transliterations, etc. The usage of these captions was inconsistent, the way examples are grouped in the same box was also inconsistent, where the example description sentence is placed was inconsistent, etc. Also when more than one example is given to illustrate how a specific rule differentiates an individual work from another, it may be easier to contrast these examples if they are boxed together (e.g.: examples on p. 31-33). In chapter 7, the use of example boxes wasn’t consistent. Sometimes more than one example is included in one box and the other times more than one box appears to give several examples.
Chapters I reviewed included materials I rarely handle such as music, legal works, etc. Not so many examples helped me understand rules on these specific materials.
There weren’t enough CJK or other non-roman language examples except for Different Scripts, Different Languages, Transliterations, etc. sections.
o On referencing: Majority of references were incorrectly assigned. And some cases, it was difficult to guess correct rule numbers. I am less familiar with RDA than other reviewers. However, if there are more than one reviewer had difficult time finding correct numbers for some specific references, it may be good to rephrase the wording of the section or add rule captions to the item. Also so many sections in RDA were repeating things explained somewhere else and give only references to other rules. It was very confusing to go back and forth in some 200 page chapters.
·
[General
comments on chapter 8] The
general guidelines of Chapter 8 are intended for establishing personal and
corporate name headings in bibliographic records and variant names and
cross-references in authority records. This guiding principle needs to be
clearly articulated at the very beginning of the chapter so that people will
not wonder whether Chapter 8 applies to bibliographic records or to authority
records.
Libraries without NACO
trainings may not necessarily recognize that the provisions 8.8-8.13 apply to
authority records, not to bibliographic records. The instructions for bibliographic and
authority records should be laid out in separate sections, because it is not
always possible or appropriate to supply in bibliographic records the data
prescribed in 8.8-8.13 that are only provided in authority records. Lump together the provisions for
bibliographic and authority records may cause confusion.
·
[General comments on Chapter 16 and
general] I
also have some issues about place names in Mongolia but these are more the
purview of national cataloging agencies rather than RDA. The same also applies
where conventional names are used instead of systematically romanized forms
but, even though there are many examples in RDA, mostly US cataloging
agencies-centric, this is, to my mind, still more a national cataloging
agencies' concern than a RDA concern.
· [General comments on Appendix J]
o I wonder if catalog users understand and feel useful about the definitions of work, expression, manifestation, and item and distinctions between them, which are qualified in parentheses after the relationship designators.
o Most of the relationship designators have qualifications in parentheses but not all.
2. Specific comments in instruction number order (whether or not they are in response to issues raised in the cover letter)
|
Page |
Instruction # |
Text |
Questions/ Comments/ Suggestion |
|
8 |
0.4.3.7 |
Language Preference |
Summary of group comments [see individual comments below]: · Believe original language and script should be preferred in all cases where possible, with the actual implementation in a international collaborative cataloging environment. · Concerns and confused about different criteria applied for language preference in various instruction (e.g. “commonly known,” “the form corresponding to the language of most of the resources,” “in the language preferred by the agency creating the data,” etc.) · Concerns about the AACR2 legacy issue of an author who has names in more than one language and may be both commonly known to his/her peers in the country/region corresponded to each language. Using preferred name chosen based on RDA with variant form provided in authority would not address the issue thoroughly and effectively from users’ perspective in a global environment. Alternative instruction in RDA for data recording, and/or standards for data presentation and data reference structure need to be investigated to address this issue. [Comment 1] language/scripts of preferred name by the agency given
preference over original language/scripts, current practice for name
authority, not ideal but with non-Latin form as variant, it gets much
better [Comment 2] With the actual implementation In A COLLABORATIVE CATALOGING ENVIRONMENT I believe original language and script should be preferred in all cases where possible. This is certainly not possible in many cases at present but UNICODE provides the mechanism to accomplish this. At any rate this is not directly germane to the draft and needs to be addressed later. [Comment
3] The paragraph of RDA 0.4.3.7 Language Preference is not quite
clear to me. What is “the agency creating the data” referred to in this
paragraph? My
understanding is that RDA 9.2.2.3 and 9.2.2.5.2 (see also AACR22.1A. and
22.3B.) instructs catalogers to choose the personal name and the form of name
which is commonly known, or commonly used, or found from most of the
resources. However, the choice of corporate body name and the form of
name, according to RDA 11.2.2.5.2 (see also
AACR24.1A. and 24.3A.), is determined by the official language of the
corporate body or the language preferred by the agency creating the data
(“the agency” referring to the corporate body?). Shall I interpret the
rules this way? The rules: RDA 0.4.3.7 Language Preference The name or form of name designated
as the preferred name for a person, family, or corporate body should be the
name or form of name found in resources associated with that person, family,
or corporate body in the original language and script of the content.
However, if the original language and script is not the language and script
preferred by the agency creating the data, the preferred name or form
of name should be one found in resources associated with that person, family,
or corporate body, or in reference sources, in the language and script
preferred by the agency. RDA 9.2.2.3 Choosing The Preferred
Name In general, choose the name by
which the person is commonly known as the preferred name for that
person. RDA 9.2.2.5.2 Language If a person’s name has appeared in
different language forms in resources associated with the person, choose the
form corresponding to the language of most of the resources as the
preferred name. RDA 11.2.2.5.2 More than One Language
Form of the Name If the name appears in different
languages, choose the form in the official language of the body as the
preferred name. Alternative: Choose a form in the
language preferred by the agency creating the data. [Comment 4 –follow up] Thanks
for bring it up. This is a good question and a question myself often
struggling with. Although RDA tries to separate data presentation from data
recording, it’s easy to use current practice to illustrate the dilemma here.
For a Chinese person, you would prefer to transcribe it in Chinese for
both description and access point, however, we have been transliterated it into
Romanized form in Pinyin as practice for controlled access point (name
heading in authority record) in North America, but if in China, Chinese would
be preferred language for transcription and access point. This is what
my interpretation of “using the language/script preferred by the agency
creating the data” The most dilemma is for scholar who are, for
example, Chinese American, use both forms of Chinese name and English name
for his/her publication, such as Yip, Wai-lim, one UCSD professor in Chinese
literature. Wai-lim Yip is his English form of name he used here for his
publication in English and be known by his North American scholar peers,
however, 叶维廉 = Ye Weilian is his Chinese name used in his publication in Chinese
and known by his peer in Chinese literature community in China and Taiwan.
How you determine his preferred name, and choose which as preferred language,
it is set by AACR2 and later by RDA. In his case, Yip, Wai-lim is controlled
(“preferred” in RDA) access point for him, so in data presentation (in MARC
format), in 245c for his publication in Chinese, you see 叶维廉 =
Ye, Weilian, but in 100 or 700 you see Yip, Wai-lim without Chinese parallel.
And you certainly would not see his Chinese name in records of his
publications in English. I know there are catalogers
like me don’t like this way, but can we think of a better way to deal with
it? I can’t. This is my dilemma, and why I commented as “not ideal” [Comment 5–follow up] I am glad Shi Deng brought out this
issue. This is exactly my concern. Yip
Wailim is a good example. However, for Yip's case at least he has (may be)
equally amount of works published in both English and Chinese. There are
other extreme cases. For example a person's dissertation for an American
university is the very first item cataloged in U.S. His name then is
established accordingly in the authority file. Later this person published
quite number of books in his or her own native country with a different form
but never in the U.S. For the current practices and RDA we stick with the
established heading and relay on the authority record to bring out other form
of this person's name. Meanwhile in this person's own country all books are
cataloged under the later form. The beauty of RDA 0.4.3.7 is to allow
cataloging agency to determine their own preferred form for a name yet the
discrepancy form different agencies continues. RDA did not solve this
problem. Some kind of alternative may be needed in 0.4.3.7 to settle this
kind of situation. [Comment 6 – follow up] Along these same lines would be minzu authors who write in both their native language and Chinese. This gets further confused in that the form of name may be different in, for example, libraries in Beijing and Hohhot (or even within the same library in Hohhot--personal experience with the library at Neida). Especially in these cases it is important that authority records include all forms and all writing systems. This isn't really part of RDA yet but I believe it will become more important as time goes on. [Comment 7 – follow up] These provisions give a cataloging agency
the ultimate authority and freedom to determine what a preferred name should
be. Libraries in different parts of
the world all have their own preferred languages and can decide to use
different forms of name for a particular person. Such practice will have ramifications on
authority records, indexing and retrieval in the global online environment,
mostly affecting end users. Improved
referencing structures and enhanced authority control capability will be
needed to support the implementation of these RDA provisions. [Comment 8 – follow up] I
think the problem we will continue to observe with RDA rules is that by
trying to maximize the flexibility to the cataloguing agency, the set of
rules will never be entirely satisfactory for individual groups and factions
such as the CJK. Ultimately, it will be up to the hard work of
committees like the CTP to interpret the set of general rules and create more
specific guidelines to accommodate to the CJK cataloguing needs. And
hasn't it been the case with AACR2? As mentioned previously by other members,
the rules that address language preference (0.4.3.7) present some difficult
issues in trying to decide which should be the preferred form of the
name. Using the RDA rules as basis, we will have to think about
laying out standardized practices for North American institutions or aim to
find a compromising global approach. As far as we are concerned,
getting rid of romanization is not an option for North American institutions;
hence continuing to keep up with authority records that incorporate all
possible forms of the name sounds like the most effective and compromising
approach. [Comment 9– follow up] This issue has been in my mind for many years and it is indeed a dilemma that we face as non-latin language catalogers using the rules primarily designed for latin language materials. While agreeing with Fabiano that “continuing to keep up with authority records that incorporate all possible forms of the name sounds like the most effective and compromising approach”, I believe that we should and we can find a better way to treat Yip-like case in bibliographic records. One option that we can consider is to add a non-latin parallel heading (e.g. 叶维廉) all times, even if the established name heading is in original latin form (e.g. Chennault, Anna) or transliterated form by a non-standard latinization scheme (e.g. Yip, Wailim). This practice is not allowed under the current rules but implemented by some institutes, especially those in Hong Kong, where the rules applied are more flexible in favor of majority Chinese. Many catalogers, including myself, may not like this parallel name heading for its “illegal” relation with the established heading in latin form, but the “extra” form of heading does help catalog users to identify the authors and get more hits, especially with today’s OPACs which are functional in non-latin searching. Also technically, since non-latin script references have been added to NACO name records, entering the non-latin heading is no more a big deal even for a cataloger who doesn’t know the author’s name in non-latin script. By this way, all Dr. Yip’s work, including his work in English, will be searched by either 叶维廉 or Yip Wailim, depending on what language used for search key. |
|
19-20 |
0.10 |
Internationalization |
[Comment 1] it is flexible, but in a collaborative cataloging
environment see my comments above under 0.4.3 [Comment 2] Mostly, I agree to the draft. I think it is a
much anticipated improvement from AACR2, allowing the original language to be
the most favorable language to transcribe. However, since it gives you so
much flexibility and does not say specifics, I wonder some catalogers may
feel a bit confused about which way would be the best way to transcribe,
especially on the 0.10.3 Numerals and 0.10.4 Dates areas. |
|
19 11 |
0.10.2-0.10.5 0.6 |
Term 'Specified elements' Term 'Specific elements' |
[Comment 1] The term 'Specified elements' appears once in
each section above except appearing twice in 0.10.4 (Dates). I don't
think it's clear enough what it refers to. It appears first time in
0.10.2 and used in those four sections. If the term means core
elements, it was used as 'Specific elements' in 0.6 (p. 11), first line,
right below 'General', referring to Core elements. [Comment 2] I agree with Erica. I wasn’t
sure what “Specified elements” are, either. RDA contains many words
describing concepts that I probably need some time to feel
less confused. For international users, I think it is better to keep using the same phrases. |
|
19 |
0.10.3 |
Numerals |
[Will not report under
this instruction but under 2.5.2 and 3.4.5]
|
|
7, 15 |
1.4, 1.8.1 |
1.4 [Sentence before the
exception parag.]all other elements (including
notes) in the language and script, or languages and scripts, preferred by the
agency creating the data. 18.1 Alternative For early printed resources, transcribe numbers expressed
as numerals or as words appearing in numbering of serials, date of
production, date of publication, date of distribution, or date of manufacture
in the form in which they appear on the source of information. When recording numbers expressed
as numerals or as words in a transcribed element, transcribe them in the form
in which they appear on the source of information. Apply the general
guidelines on transcription (see 1.7 ), as applicable. |
Libraries in North America may need to set specific
guidelines to accommodate this rule to CJK cataloging needs. |
|
12 |
1.7.3 |
Punctuation “Transcribe
punctuation as it appears on the source…” |
[Comment 1]
Punctuation has language issue too. If following the instruction, do we
transcribe all Chinese punctuation or only these that are diff from ASCII
punctuation as our current practice? Need clarify. Internationalization
rules not consistently throughout RDA. [Comment 2] Agree!! Plus, 1.if we transcribe punctuation in script field, how to handle
punctuation in corresponding romanization field, the same or replaced by
other punctuations? 2. If we transcribe
punctuation, would it affect indexing and searching? |
|
7 |
1.4 |
[Alternative] If an element listed above cannot be recorded in the script used on the source from which it is taken, record it in a transliterated form. |
“Cannot be recorded … ” Theoretically,
we can record any script from which it is taken. If we do encounter something
cannot be recorded due to system or encoding problem, what kind of
“transliterated form” we should use?
Need clarification. |
|
|
1.8.4 |
Inclusive Numbers When recording inclusive dates
and other inclusive numbers record both the first and last number in full. |
For inclusive number, to transcribe the number as it appears on the source, followed by fuller form in bracket if necessary would be more consistent with general guidelines on transcribing information from where it is taken. It is also the current practice for the new CSR standard record. |
|
29 |
2.3.2.12.1 |
Major and Minor Changes in the
Title Proper of Serials |
[Do not report]
|
|
33 |
2.3.3.4 |
Type of Musical Composition,
Medium of Performance, Key, etc. |
Heading is inconsistent with other headings (e.g. 2.5.2.4, 2.5.4.4) that has “in more than one language or script.” Should add this phrase to this heading? |
|
|
2.5.2 |
Designation of edition 2.5.2.3 Recording Designations of Edition Record a designation of
edition applying the basic instructions on recording edition statements given
under 2.5.1 2.5.1.4 Transcribe an edition
statement as it appears on the source of information. Apply the general
guidelines on transcription given under 1.7 . |
[Comment 1] Questions on 0.10.3: By the thought of
recording designation of edition and extent in CJK languages in the
form in which they appear on the resources, like 第二版 and 百三十六 leaves (as in early printed resources) respectively, are
these statement in 0.10.3 appropriate to CJK resources? To me, it would
be easier for users to understand if they are recorded by using
arabic numerals as 第2版 and 136 leaves. Or should I think these cases can
be treated as the allowance cases? ] [Comment 2] agree. But since in 1.7, alternative instruction is provided, and reference for recording numeral express as word is referred to 1.8, I would be OK with the rule. However, it bothers me that 1.8.1 defines the elements for applying this instruction doesn’t include designation of edition. You come to a dead end. [Comment 3] Should keep current practice that is: If numeric designation expressed as word, should be changed into Arabic form preferred by agency who creating the data. Suggested solution: Either add “numeric designation of edition” to the list under 1.8.1 so it would be covered by 1.8.3 Numbers Expressed as Words Or add alternative rule under 2.5.1.4 Recording the numbers expressed as words in the form preferred by the agency creating the data as a substitute. |
|
87, 89-103 |
2.6.1.2 and 2.6.4-7 |
|
Rule c) in the 1st paragraph and rules e) and f) in the 2nd paragraph are added after 2005 draft. I wonder if they are necessary because it seems each rule in these pairs: b) & c) in 1st paragraph, c)-d) & e)-f) in the 2nd paragraph, gives almost same instruction of the others’ and we have been doing the same cataloging as required using AACR2 without these kind of rules. Accordingly, I also wonder if rules 2.6.6 and 2.6.7 are necessary because their instructions are almost same as rules 2.6.4 and 2.6.5 respectively. I guess RDA structure may require these additional rules, but it seems to me RDA would become too elaborate and complicated as a cataloging rule. |
|
110, 125, 141, 151 111, 125, 142, 155, 111, 126, 142, 156 |
2.7.2.6, 2.8.2.6, 2.9.2.6, 2.10.2.6 2.7.2.6.3, 2.8.2.6.3, 2.9.2.6.3, 2.10.2.6.3 2.7.2.6.4, 2.8.2.6.4, 2.9.2.6.4, 2.10.2.6.4 |
Place of [Production, etc.]
Not Identified in the Resource · Known Country, State, Province, etc., of Publication, etc. If the country, state, province, etc., of …
is known, supply that name. ·
Probable Country, State, Province, etc.,
of Publication, etc. If the country, state, province, etc., of … is uncertain, supply the name of the probable country, state, province, etc., of production followed by a question mark. |
Internationalization principle was not consistently applied here. Instruction for supplying name for local place and place of Known/Probable Country, State, Province, etc., in what form (in the language/script of the content vs. in the language/script preferred by the agency creating the data) was missing. Examples imply “in the language and script preferred by the agency creating the data” Rule 1.4 does includes place of production, etc. as elements to be “Record the following elements in the language and script in which they appear on the sources from which they are taken” But Rule 1.4 didn’t address place name “Not Identified in the Resource” Should it be clarified under general instruction of 2.7.2.6, 2.8.2.6, 2.9.2.6, and 2.10.2.6? if language rule would be the same for local place and Country, state, province, etc. If not, should be addressed individually under each rule number. |
|
189 |
2.14.1.3 |
Recording Frequency Record the frequency of release of issues or parts of a serial or the frequency of updates to an integrating resource, if known, using one of the following terms: … [terms listed in English] |
Internationalization principle was not consistently applied here. Frequency has language issue
too. It is not the element listed in 1.4 to be “Record the following elements in the language and
script in which they appear on the sources from which they are taken” but 1.4
instruction of “Record all other elements (including notes) in the language
and script, or languages and scripts, preferred by the agency creating the
data.” Although it is defined to use one of term in English in a list under this rule, would other non-English speaking countries follow it to use English term listed not terms in their own language or script? Language issue should be addressed. The list of term should be replaced by using terms preferred by the agency crating the data. |
|
193 |
2.15.1.7 |
Qualification |
Libraries in North America may need to set specific
guidelines on how to record the qualifications in CJK languages. |
|
194 |
2.15.2 |
Publisher’s Number for
Music |
May need to include rules and examples for the publisher
number of sound recordings and video recordings because they are not
mentioned in any other parts of RDA. |
|
2 |
3.1.4 |
Resources Consisting of
More Than One Carrier For instructions on recording
information relating to the carrier for accompanying material, see 27.1 . |
Is the way describing
accompanying material by adding it to the end of physical description no
longer valid? I could not find any
instructions and examples on this in chapter 3, 27, and other related
chapters. |
|
13 |
3.3.1.2 |
Video carries |
Suggest to add “videodisc” |
|
36 |
3.4.5.2 |
Exceptions. Early printed resources |
Libraries in North America may need to set specific guidelines to accommodate this rule to CJK cataloging needs. |
|
37 |
3.4.5.2 |
[Single Volume (Extent of
Text)] Record pages, etc., that are
numbered in words by giving the numeric equivalent. |
Should this refer to language
rules and being consistent with internationalization issue? It is not the element listed in 1.4 to be “Record the following elements in the language and
script in which they appear on the sources from which they are taken” but 1.4
instruction of “Record all other elements (including notes) in the language
and script, or languages and scripts, preferred by the agency creating the
data.” Should language rule be mentioned and referenced in this section? |
|
37, 45, 46 |
3.4.5.2, 3.4.5.10 3.4.5.14 |
[Single Volume (Extent of
Text)] Folded Leaves or Pages Single Sheet |
[Place holder for Accordion Style] it was not mentioned at all. Don’t know if JSC decided to drop it or
not have enough time to incorporate our comments after hearing our feedback.
Would you think the instruction is clear
for dealing with Accordion style, but need to provide examples?, or should it
be implementation decision after RDA published? [Comment 1] The current rule is fine with me. I always think RDA should be guideline and doesn’t have to cover all the situations. I prefer to have it in implementation decision later. |
|
40, 41, 15 |
3.4.5.4, 3.4.5.8 1.8.1, |
·
Change in Form of Numbering within a
Sequence Exception Early
printed resources. For early printed
resources, record the numbering in the form presented. ·
Complicated or
Irregular Paging, etc. Exception Early
printed resources. For early printed
resources, record the paging,etc., in the form and sequence presented. ·
Alternative For early printed resources, transcribe numbers expressed as numerals or as words appearing in numbering of serials, date of production, date of publication, date of distribution, or date of manufacture in the form in which they appear on the source of information. |
Internationalization principle was not consistently applied here. [Comment 1] According to the
exception under 3.4.5.4, it seems to me that the numbering of
CJK early printed resources should be recorded as 百三十六 leaves ... etc. [Comment 2] I think that Sachie
brought good question here regarding recording early print in CJK language.
Numbering has language issue. Language instruction should be consistently apply here
too, by using alternative rule or option rule for recording numeric
equivalent in the language preferred by agency creating the data. [Comment 3] Same here. It would be clearer to add edition in the list. [Comment 2] Also instruction listed here is not consistent with 1.8.1
which make it alternative, but here listed as exception. |
|
45 |
3.4.5.11 |
books in the traditional East Asian |
Suggest to add a term such as “binding” or “style” at the end … books in the traditional East Asian binding Or … books in the traditional East Asian style |
|
47 |
3.4.5.14 |
Single Sheet |
Suggest to add under instruction after “Exception. Early printed resources.” Exceptions: Early printed resources. “For East Asian early printed
resource consisting of a single sheet in roll form, record the extent as 1
scroll.” [need to be agreed in East Asian
cataloging community] Accordingly add instruction under 3.5.1.4.11 |
|
61 |
3.5.1.4.11 |
Sheets |
Suggest to add under instruction after “Exception” … Early printed resources. For East Asian early printed resource consisting of a single sheet in roll form, record the height of the central axis. Make a note on the height and width of the sheet if it is readily ascertainable. |
|
98 |
3.12.1.3 |
Recording Book Formats |
It may be necessary to list up terms for book formats representing East Asian early printed books. [provide examples under comments on example section] Language issue. Making a list of term that may not be applied worldwide. Should provide instruction on in the form preferred by agency who creating the data, or … |
|
98 |
3.12.1.4 |
Propose
a section on Recording Book Binding Formats |
Should
add instruction 3.12.1.4 on recording Book binding formats including address
language issue. Because CJK rare book cataloging sometimes needs binding terms but
rarely uses book format terms and they have not been standardized yet.
So we wondered if we need to add instruction and examples to RDA. If agree, here is
the list of examples. 卷子本 折本 旋風葉 粘葉装 胡蝶装（列帖装） 袋綴 大和綴 |
|
11 |
6.2.2.4 |
If the work is published
simultaneously in the same language under different titles, choose the title
proper of the first resource received as the preferred title. |
What
about different languages? Especially different languages received at the same
time? I would assume that RDA
6.2.2.4 covers the situation mentioned in 25.3.C2 and 25.3.C3. If yes, then
RDA needs to have a little bit more elaboration. However,
I learned that, indicated in Cf.: SJSC/Sec/7 16 November 2008, p. 9, RDA will
not have further guidance on this issue as AACR2 provided in AACR2 25.3.C2
and 25.3C3. [AACR2
25.3C2 -- if published in different languages and under different titles, ...
use as the uniform title the title in the language in which the name of the
corporate body is entered in the catalogue. If
no corporate heading as main entry, or does not apply, apply 25.3.C3: AACR2
25.3C3 -- If .... use as uniform title (in this order of preference) the
title in English, French, German, Spanish, Russian.... If not apply, then use
the title of the edition received first] Situations
-- 1) Increasingly more and more
publications from Asia, esp. from the
govt. organizations, issued publications in more than one languages at the
same time 2) Both versions received by the
cataloging agency AT THE SAME TIME 3) Hard to determine which title is the
preferred title to be used because it the title proper of the "edition
received first" Example - Both versions received SAME TIME, by one
cataloging agency, one in Chinese, another in English, pub. by the same one
govt. body, in 2003 Chinese
version-- 香港歷史博物館, 香港海防博物館, 李鄭屋漢墓博物館, 羅屋民俗館簡介 / ‡c [香港歷史博物館編 ; 編輯丁新豹, 吳碧儀]. English
version - Hong Kong
Museum of History, Hong Kong Museum of Coastal Defense, Lei Cheng Uk Han Tomb
Museum, Law Uk Folk Museum : brief guide. Publisher: 香港 : ‡b 香港康樂及文化事務署,
‡c 2003. Suggestion
of cataloging - the suggestion is under assumption that 25.3C2, 25.3C3 is
obsolete (a)
do not give uniform title in this case (b)
transcribe title proper from the source of
the respective version. e.g. transcribe 245 in Chinese [for Chinese version],
without 240; same as 245 in English for English version (c)
Give a 500 note to link two versions - For Chinese version - 500: Issued also in English, under
title: Hong Kong Museum of History,
Hong Kong Museum of Coastal Defense, Lei Chen Uk Han Tomb Museum, Law
Uk folk Museum : brief guide For English version - 500: Issued also in Chinese, under
title: Xianggang li she bo wu guan, Xianggang hai fang bo wu guan, Lizhengwu
Han mu bo wu guan, Luowu min su guan 500: Issued also in Chinese, under
title: 香港歷史博物館, 香港海防博物館, 李鄭屋漢墓博物館, 羅屋民俗館簡介 (d) Give additional access point for the
title linked in 500 for each respective bib record Hope
that RDA will address the situation where both language editions under
different titles received at the same time. It's hard for cataloger to decide
which edition received first. The current RDA 6.2.2.4 need further elaborate. |
|
3 |
8.2 |
Functional Objectives and Principles |
It seems that 8.2 a-d) mix
together the functions of bibliographical records and authority records. The primary function of bibliographic
records is to enable the user to identify and retrieve desired bibliographic
items. Bibliographic records cannot
fulfill the functions listed in c) and d), which are facilitated by authority
records. The caption also needs to be
made more precise to eliminate potential confusion: 8.2 Functional Objectives and Principles for Bibliographic Records and Authority Records |
|
3 |
8.2 |
Representation. The name or form of name designated as the preferred name
for a person, family, or corporate body should be the name or form of name
most commonly found in resources associated with that person, family, or
corporate body, or a well-accepted name or form of name in the language and
script preferred by the agency creating the data. Other names and
other forms of the name that are found in resources associated with the
person, family, or corporate body or in reference sources, or that the user
might be expected to use when conducting a search, should be recorded as
variant names. |
The instructions (being underlined) are not clear in terms of whether the cataloger should record the variant name(s) in a bibliographic record or in an authority record. The instructions need to be more specific or illustrated with examples. I wish to use the personal name “Yip, Wai-lim” as an example that has been previously discussed in our group. Yip, Wai-lim is the authorized form of heading and his Chinese name葉維廉is a variant name. There are numerous cases like this such as: Sun, Yat-sen / 孙中山 Chiang, Kai-shek /蒋介石 Hung, William / 洪業 Chao, Yuen Ren / 趙元任 Tsien, Hsue Shen /錢學森 Tsien, Roger Y. / 錢永健 Shakespeare, William / 莎士比亞 Einstein, Albert / 愛因斯坦 Lee, T. D. / 李政道 Lee, James Z. / 李中清 楊牧 /葉珊/ Wang, C. H. ǂq (Ching-hsien) [real name: 王靖獻] If a cataloger literally
interprets “Other names and other forms of the name that are found
in resources associated with the person, family, or corporate body or in
reference sources, or that the user might be expected to use when conducting
a search, should be recorded as variant names” and
thinks that the instruction applies to name headings in bibliographic
records, one of following approaches may be taken: Yip, Wai-lim (100/600/700/800 fields; current
cataloging practice in American libraries)
Alternative 1: 100
1 Yip, Wai-lim 700
1 Ye, Weilian 700 1 葉維廉 Alternative 2: 100 1 Yip, Wai-lim 100 1 葉維廉 Alternative 3: 100 1 Yip,
Wai-lim (葉維廉) Please see an example of
catalog record in the OPAC of the National Library of China, in which the
subject heading is: 爱因斯坦 (Einstein, Albert 1879～1955) and the author heading is: 布里安 (Brian, Denis) Although AACR2 only allows the
authorized heading “Yip, Wai-lim” to be used as a valid access point in
bibliographic records, the other forms of names being used in different parts
of the world are not necessarily wrong if we think from library users’
perspectives. However, we must deal
with the issue of split files when different forms of names are used in
bibliographic records. A “preferred
access point” will be determined by the cataloging agency to serve its
primary users and in fact, RDA recognizes the existence of split files and
made clear that it will continue to be the case, due to cataloging agency’s
choice in language preference and scripts used to describe resources. There is a need for us to rethink of the concept of so called “valid heading” in light of using RDA as an international metadata code. It is even more important for us to rethink the functions of authority records. The ideal world would be that no matter what forms of name are being searched under for a particular author, the searcher should find all the works by the same author. To accomplish this goal, a powerful authority control mechanism with enhanced reference structures must work behind the scene to support the bibliographic queries. We do not have such authority-control backed bibliographic searching currently available in OCLC, which significantly limits the database’s capability of mitigating the adverse effects of split files. However, we should be optimistic that including non-Latin scripts in authority records is a big step forward and it has actually paved way for improved authority control functions in the near future. |
|
3 |
8.2 |
Representation Preference |
For CJK personal name that appeared in
the bib entry represented by a preferred form [usually is the established
form in the name authority heading] that do not reflect the person's known
form of his/her name in the real
world, due to the reasons arising from the adoption or usage of various
transliteration scheme [so applied to the paralleled field, so the vernacular
form of the person's name lost], or other reasons as listed below, what would
we do? Suggestion/Question - Can we make an optional or additional
access point for the "known" form of the name for this person in the bib record?
[usually appear as 4xx in the name authority record]. This suggestion will
reflect more of the RDA philosophy of
globalization and user friendly Examples: 1)
Ricci, Matteo, 1552-1610 [heading of n 81005150]-- a famous missionary Reason - This situation apply to many famous
westerns that went to Asian and adopt
their Asian names which more familiar to the Asian people than their
original western names the famous Jesuit missionary in China
during 15th-16 century was/is well known to Chinese, or perhaps people in
Asian, as his Chinese adopted name: 利瑪竇 Suggestion - 利瑪竇 get an access point in bib record 2) Cheng, Long, 1954- [no 96039667] -
world known Kong fu movie star Known to the world as: Jackie Chan This situation also exists and
encountered by many catalogers when cataloging material of Asian movies/TV
shows [names appear on screen bilingual], other performing artists, etc. One form is the form in our name authority
[most either English form, or transliterated form, which alien to the Asian
communities]. The form that better known to the Asians should get an access
point in the entry Suggestion - make access as additional
point in the bib record for Jackie
Chan 3)
Chiang, Kai-shek, 1887-1975 - and other famous world politicians whose name
transliterated in various scheme by various pronunciation, became their known
English names Suggestion - make an access for its
equivalent Asian name in its vernacular form: 蔣介石 This situation can also extend to the
names that adopted as preferred form but can't be paralleled in bib entry,
due to non-Pinyin transliteration, due to various reasons [some from TW, prefer W-G form, or their own invented form
of Romanization; some became their known English name in the West], such as: Li, Yuan Tseh, 1936 [heading from n
85295494]--a Nobel laureate Known to the Chinese communities as: 李遠哲 Yang, Chung-Chun, 1942 [heading from n
82065230]-- a mathematician, whose form in slightly different W-G form,
became his English name, known to the
West on his works. His many Chinese works pub. in China, TW, HK, in Chinese
form: 楊重駿 Following names mixed with English and
Chinese, but known to Chinese communities with only Chinese names: Chang, S.K. (She Kuo), 1944 - [n
80039913] - a computer scientist in USA,, who also has written hundreds of
novels, known to Asian communities as: 張系國 Chu, Steven - famous physicist in USA,
Nobel laureate, now Obama's nominee for the Secretary of Energy, known to the Chinese communities
only with his Chinese name: 朱棣文 The main point is that the various forms
for each name cited above that is better known in other communities
[for globalization purpose] other
than their preferred form in the entry, should get an access point?? There must have been many other CJK names from
Japan, Korea, Hong Kong, Singapore, etc. having the similar situation. For Chinese
names, I checked around, it can be called as: "the vernacular form of
the name" [name in CJK script] |
|
5 |
8.4 |
Language and Script Alternative Record a transliterated form of the name either as a substitute for, or in addition to, the form that appears on the source |
i.e., the heading may be in original script only, in
transliteration only, or, in both original script and transliteration paired
in linked parallel fields). Many libraries in other parts of world do not use
transliteration in bibliographic records. |
|
5 |
8.4 |
Record other identifying
attributes of a person, family, or corporate body in the language and script
prescribed in the applicable instructions in chapters 9–11 |
requires further clarification |
|
9 |
8.7 |
Variant Access Points
Representing Persons, Families, and Corporate Bodies |
Clarifications
are needed on whether 8.7 will apply to bibliographic records. American libraries do not supply “Preferred
Access Points” and “Variant Access Points” representing the same name in the
same bibliographic record. For instance,
100 1
Yip, Wai-lim, we do not supply another 700 1 Ye, Weilian or, 700 1
葉維廉 in the same bibliographic record. However, I would not think it
is wrong when some libraries use both “Preferred Access Points” and “Variant Access
Points” representing the same name in the same bibliographic record, based on
cataloging agency’s language preference under 8.2, as illustrated in the OPAC
of the National Library of China. |
|
|
8.8-8.13 |
8.8 Scope of Usage 8.9 Date of Usage 8.10 Status
of Identification 8.11 Undifferentiated
Name Indicator 8.12 Source
Consulted 8.13 Cataloguer’s Note |
It
should be made clear that 8.8-8.13 apply to authority records, not to
bibliographic records. |
|
7 |
9.2.2.5.2 |
Language, Alternative |
I have a question on alternative rule with the bar. The well known politicians usually are established in English for CJK. If those politicians especially who become president later published books and their names were established following Romanization system from the vernacular character before their English name is known, do we change the form to English form later or leave it alone? |
|
11 |
8.9.1.3 |
Recording
Date of Usage Record information about the date of usage of the name designated as the preferred name for the person, family, or corporate body. |
An additional note will be helpful in order to state clearly that the recording date of usage is required for variant names. |
|
14 |
9.2.2.5.3 b) |
[right below 1st example, beginning of 3rd line] “This alternative instruction …” |
What does ‘this’ refer to? The one above or below? If it is the instruction below, can it be clearer like ‘Alternative instruction below …’? |
|
28-30 |
9.2.2.10 |
Compound surnames |
Suggestion: add 9.2.2.10.3 Pseudo-Compound
Surnames. See details under Appendix F.
9.2.2.10.3 Pseudo-Compound Surnames In
some languages what appears to be a compound name is not one. In Mongolian,
the hyphen only indicates that the second element begins with a vowel, an
artifact from Mongolian script where the letter "шүд" replaced
"титэм" when the second element began
with a vowel. There is no Mongolian usage specified in Names of persons:
national usages for entry in catalogues. FOR
EXAMPLE: Name
appears as: Шагдайн
Цэнд-Аюуш Цэнд-Аюуш
is an inseparable unit and references such as Аюуш,
Шагдайн
Цэнд- make no sense. |
|
33 |
9.2.2.13 |
[2nd paragraph] Record the surname as the first element. If there is
no surname, record as the first element the part of the name that is used to
identify the person in resources or in reference sources (e.g., name of the
house or dynasty, territorial title). |
This paragraph covers
the case of ‘no’ surnames, which is
covered by 9.2.2.20. It may be more
helpful to refer to 9.22.20. |
|
46 |
9.2.3.3 |
ecorded as the preferred name for that person. For persons who have established two or more identities, see the instructions on related persons in chapter 30 |
Suggestion: delete the fragment : ecorded…person. Keep the sentence that begins with: For. Alternatively, a clearer statement is needed. |
|
47 |
9.2.3.5 |
Secular name |
[Comment 1]This explanation is wrong and it does not fit with examples. The text is currently same as next one, 9.2.3.6. We may have to switch around the position of the two words – secular name and religion in 9.2.3.5. The text should say “If … person’s religious name, record … in secular as a …” [Comment 2] Examples and explanatory note (i.e. the first paragraph) contradict each other. Requires rewriting so that the header “Secular Name” can remain as is. |
|
64 |
9.3.2 |
Date of Birth. 1st example on 3rd group, ‘1936 May 5’ If
the person was born in the same year as another person with the same name,
record the date of birth in the form [year] [month] [day]. Record the month in the
language and script preferred by the agency creating the data. |
[Comment 1] Is it better to have only year part in this example? Because we don’t give month and day if this is the first John Smith. [RI: Add a person’s dates (birth, death, etc.) in the form given below as the last element of a heading if the heading is otherwise identical to another.] [Comment 2] this may be a change but it does need to be clarified. Would this mean that one enters year/month/day whenever the information is readily at hand? The instruction here does seem to indicate some authority work is involved since how would one know if the name is the same as another. |
|
66 |
9.3.4.1 |
[Scope, 2nd paragraph] Date of death may also include the month and day of the person’s death. |
[Comment 1] Should ‘Date of death’ be replaced with ‘Period of activity’ or this whole sentence may not be necessary? [Comment 2] The second sentence does not belong here. Please delete. |
|
95 |
9.19.1.1 |
Make the additions specified
under 9.19.1.2 regardless of whether they are needed to distinguish
the person from another person with the same name. |
Second paragraph
requires further clarification |
|
5, 7 |
11.2.2.5 11.2.2.5.2 |
11.2.2.5 Different Forms of the Same Name If different forms of a
corporate body’s name appear in resources associated with the body, apply the
general instructions given below. When appropriate, apply the special
instructions given under 11.2.2.5.1 –11.2.2.5.4 below as well. 11.2.2.5.2
More than One Language Form of the Name If the name appears in
different languages, choose the form in the official language of the body as
the preferred name. |
Between 11.2.2.5 and 11.2.2.5.2, which rule takes priority for a corporate body which has more than one language form? Instruction in 11.2.2.5 says “When appropriate, apply special instruction … below AS WELL”. ‘AS WELL’ bothers me. If it means use both, how do you handle this case? English name only appears on title page (Korea name appears on cover). T.p. is the preferred source of information but it’s official language is Korean, which language is preferred form? The example here is extreme. I am saying the instruction should be clearer. Can we just have instruction like ‘If a corp body use more than one language form, then follow special instruction’. |
|
16 |
11.2.21 11.2.2.6 |
If a body changes its name, a
preferred name is chosen for use with resources associated with the new name
(see 11.2.2 ). Change of Name |
Suggestion: make reference between these two rules. It may be helpful to relate these two statements on name changes in a more cohesive manner. A see also reference might help. |
|
19-20 |
11.2.2.10 |
Terms Indicating Incorporation
and Certain other Terms Omit an initial word or phrase
in an oriental language indicating the private character of a
corporate body (e.g., Shiritsu, Si li), unless the word or phrase is
an integral part of the name. |
Suggest to change “oriental language” to “East Asian language” or “Asian language” and add an example in Korean [examples added under comments on examples] |
|
84, 86 |
11.3.2.3 |
Recording Location of Conference, etc. Exceptions Record the name of an institution, etc., instead of the
local place name if it provides better identification. Record the name of the
institution, etc., in the nominative case in the language and form in which
it appears in the resource being described. If the conference is associated
with more than one institution, etc., record the names of each of the
institutions, etc. |
I know this comes from AACR2, but why
this should be different from recording place name? [16.2.2.6. Choose as the preferred name
for a place a form in the language preferred by the agency preparing the data
if there is one in general use] I feel it
is inconsistent here in terms of instruction on recording place vs.
institution as location qualifier. Examples from 19.2.1.3 Recording Creators (preferred heading in romanized form) on p. 12 & p. 19 Asia-Pacific Conference on
Communications (10th : 2004 : Tsinghua University) International Symposium on
Multi-Dimensional Mobile Communications (5th : 2004 : Tsinghua University) |
|
118 |
11.12.1.3 |
Place Associated with the Body, Optional Addition |
I have a great concern on this one. These additions are used even though there
is no conflict. I think one of the
LC’s practice for CJK record is to add a country qualifier (Korea) or (China)
for many corporate bodies which are not conflict with any other records at
all and not containing the nature of national characteristics either. I once inquired to LC Korean Team why they
provide it. Their unfinished response
(They responded once and promised to confirm with C and J but never did) was
that CJK all use Chinese characters.
Therefore to distinguish corp bodies in different countries and the
companies between China and Taiwan with the same name, LC consistently
provided the qualifiers of country names.
(Romanization field would be different among CJK but there is a
concern for searching by script. Or
are we thinking of the time when we do away with the Romanization
system?) |
|
7 |
16.2.2.8.1 |
Place Names that Include a Term Indicating Type of
Jurisdiction term indicating the type
of jurisdiction |
Incomplete instruction/sentence, requiring further clarification |
|
15 |
17.11.1.3 |
[under first example] For example: identifier for the
item |
I’m not sure that it is
accurate to use call number alone to describe an item even a user can find
the item by its call number and it can be used as the identifier of an item
in case of # of copy of a specific manifestation is 1. The identifier for one
item should be item record ID or barcode, or (call number + copy number), or
any other number assigned only to the item. If I understand correctly, the call number example is sort of misleading. |
|
|
Appendix A |
Capitalization |
Suggest to Retain special
instructions in LCRI A.33 for Mongolian Traditional Mongolian script had no upper and lower case so there was no history of capitalization. When the Cyrillic alphabet was first adopted, Mongolians usually used the capitalization rules for Russian. More recently I have seen everything from Russian capitalization rules to English capitalization rules as well as various hybrids and home-grown systems. Currently English capitalization rules are specified for Mongolian (LCRI A.33) and this should probably also be specified in RDA. |
|
|
Appendix F |
Additional instructions on names of
persons |
Needed are special instructions for
Mongolian names. Wayne will work with
his colleague to submit a proposal at later time. 1. There are no surnames. Main entry
element is given name, with patronymic used as the main qualifier. An example: name appears as Шагдайн
Цэнд-Аюуш This appears to be
forename-surname but is actually patronymic-given name. Under our current
rules the entry would be formed as Цэнд-Аюуш,
Шагдайн under the
"looks-like-a-duck" rule and AACR2 22.8B1 (which includes
a Mongolian name example). In addition
Цэнд-Аюуш appears to be a
compound name in the western sense. It is an artifact from Mongolian script
where there letter "шүд"
replaced "титэм" in
a name made up of two elements when the second element began with a
vowel. A cross-ref. from Аюуш,
Шагдайн
Цэнд- is nonsensical because the 2 parts
Цэнд-Аюуш are here
inseparable and the only reason the name is hyphenated is because the 2nd
part of the name begins with a vowel. Should there also be an additional
category under 9.2.2.10 to cover this type of name? 9.2.2.10.3 Pseudo-Compound
Surnames 2. Increasingly it appears that the
genitive case ending attached to the patronymic is being dropped (resulting
in Шагдай in the
example above). I recently cataloged a biographical reference work in which
all of the names appeared with the patronymic lacking the genitive case
ending. If the elements are reversed (as in some western
publications), this makes it extremely difficult to determine what the
given name (the primary access element) is. In light of this there should be
AR cross-refs for all direct order forms found plus all possible combinations
under which the name might be searched. In addition increasingly we find clan
names included with the names adding another layer of complexity. An
example: Name appears as Хатагин
Г. Аким (resembling a western forename-middle
initial-surname but actually clan name-patronymic initial-given name) so the
name (if this were the first occurrence) should be entered as Аким,
Г.,$cХатагин. (and certainly
there should be a cross-ref in the AR from Аким,
Хатагин Г.). Mongolian names written in Chinese, 2
examples: 1. 芒 ・牧林 (Mang. Mulin). This is the Chinese form for the Inner Mongolian
linguist/folklorist Mang. Moren [dot above "o"] (b. 1929) and
would be entered as Moren, Mang. Moren is the given name, Mang. is an
abbreviation for what is probably a patronymic. All Chinese sources I have at
hand index to 牧林. In a Chinese
catalog should this be entered as 牧林, 芒.? Should there be
an example of this type of name in RDA? 2. 道荣尕 (Daorongga). This is one of the Chinese forms for the Inner Mongolian folklorist Durungg-a [dot above final "g"] (a Mongol with a Manchu name, b. 1926). Could this possibly be interpreted as Dao Rongga. Probably not even though 道 could be interpreted as a Chinese family name. Should cross-refs be made from this form and should there be an example in RDA? In a purely Chinese catalog it probably wouldn't matter. |
|
6, 15 |
J.2.5 , J.3.5 |
Accompanying Work Relationships
Accompanying Expression Relationships |
A companion designator of illustrations for (work) in
the augmentation of (work) section may be needed for the augmented
by (work) section. augmented by (work)
An
expression that adds to the content of a predominant entity.
finding aid (work)
…
addenda (work) … illustrations (work) …
A companion designator of illustrations for (expression) in the augmentation of (expression) section may be needed
for the augmented by (expression) section. augmented by (expression) An expression that adds to the content of a predominant entity.
finding aid (expression)
…
addenda (expression) … illustrations (expression) … |
3. Comments on Examples in instruction number order. If changes to examples are proposed as part of revisions to an instruction they should remain with the specific comments in instruction number order
|
Page |
Instruction # |
Text |
Questions/ Comments/ Suggestion |
|
7 |
1.4 |
[Alternative] If an element listed above cannot be recorded in the script used on the source from which it is taken, record it in a transliterated form. |
Suggest to add an example to illustrate the instruction ForExample: 榴[lian]飘飘 |
|
14 |
1.7.9 |
Inaccuracies |
Suggest to add an example to the group: 兩晉南朝琅邪王氏傳奇 (邪 xie typo for 琊 ya) |
|
18 |
1.8.5 |
[Ordinal numbers] [Insert script] 8th in Chinese |
Chinese example is blank. Chinese example to be inserted: “第八 di 8” or “第8 di 8” |
|
22 |
1.10.3 |
[2nd example under
1.10.3] ForExample: … “A textbook for 6th
form students”—Preface” |
1.10.3 The last quotation mark should be deleted. “A textbook for 6th form students”—Preface |
|
15 |
2.3.1.4 |
[example under Exception on
inaccuracies] For
Example: Housing starts Source
of information on v. 1, no. 1 reads: Housing starts |
“starts” in the
explanatory note should be “sarts”, according to the 3rd example
of RDA 2.20.2.4 on p. 204 For
Example: Housing starts Source
of information on v. 1, no. 1 reads: Housing sarts |
|
31 |
2.3.3.3 |
Recording Parallel Titles |
Add an example to the group of
examples after the 1st paragraph For
Example: 快乐学日語 Title proper: 日本語を楽しく学ぶ |
|
44 |
2.3.6.3 |
Recording Variant Titles 2nd example: For Example: The world of television Title proper recorded as: The world of television |
The variant title is the same
as title proper in the example, a mistake for example of misspelled title? 2nd example does not illustrate recording variant titles. The last sentence, Typo: 2.20.3.3 should be 2.20.2.3 |
|
44 |
2.3.6.3 |
Recording
Variant Titles |
Add an example to the group of examples after the 1st paragraph For
Example: ブラザー [Title
on disc label] Title proper recorded as: Brother |
|
54 |
2.3.9.3 |
Recording
Key Titles |
Add an example to the group of examples after the 1st paragraph For
Example: … Nihongo bumpou … |
|
56 |
2.3.11.3 |
Recording
Devised Titles |
Add an example to the group of examples before the alternative instruction For
Example: … 滿鐵逐次刊行物. 撫順炭礦 … |
|
72-73 |
2.5.1.4 |
Recording
Edition Statements |
Add examples to the group of examples after the 1st paragraph For
Example: … 初版 초판 北京第1版 |
|
82 |
2.5.6.3 |
Recording Designations of a Named Revision of an Edition |
Add an example to the group of examples after the 1st paragraph For
Example: 修訂版 Designation of edition: 北京第2版 |
|
89 |
2.6.1.4 |
Recording
Numbering of Serials |
Add an example to the group of examples after the 1st paragraph For
Example: … 創刊号 |
|
95 |
2.6.3.3 |
Recording
Chronological Designation of First Issue or Part. Optional Addition |
Add an example to the group of examples after the 1st paragraph For
Example: 昭和51年9月 [September 1976] |
|
122 |
2.8.2.3 |
Recording
Place of Publication |
Add examples to the group of examples after the 1st paragraph For
Example: … 서을특별시 上海 東京 中華民國臺灣省臺北市 浪華 |
|
128 |
2.8.4.3 |
Recording
Publishers’ Names |
Add examples to the group of examples after the 1st paragraph For
Example: … 少年儿童出版社 大東文化大学東洋硏究所 松村九兵衛 평양 출판사 |
|
132 |
2.8.6.3 |
Recording Date of Publication. Optional
Addition |
Add examples to the group of examples after the 1st paragraph For
Example: … 民國 28 [1939] *(to be paired with Minguo 28 [1939]) 平成 9 [1997] 단기 4291 [1958] |
|
168 |
2.12.2.3 |
Recording Title Proper of Series |
Add examples to the group of examples after the 1st paragraph For
Example: … 國語國文學資料씨리즈 日本古典全書 少数民族民间文学丛书 |
|
96 |
3.12.1.3 |
Recording
Book Formats |
Add examples of book formats in Japanese … 大本 中本 横中本（大本二つ切本, 美濃二つ切本） 大本三つ切本（美濃三つ切本） 大本四つ切本（美濃四つ切本） 半紙本 小本 横小本（半紙二つ切本） 半紙三つ切本 半紙四つ切本 横本 特大本 特小本（豆本, 寸珍本, 芥子本） 方形本（枡形本） … |
|
133 |
3.21.2.3 |
Recording Item-Specific Carrier Characteristics of an
Early Printed Resource |
Add examples to the group of examples after the 1st paragraph For
Example: … LC set has "反町弘文莊納" stamped on inside case LC set has "... 天明乙巳 [1785] ..." written with brush on colophon page |
|
137 |
3.22.2.9 |
Early
Printed Resources. In the 2nd example box. |
Add an example to the group of examples after the 2nd paragraph For
Example: … Within single border (23.0 x 16.3 cm.); text in 11 vertical lines |
|
5 |
6.2.1.5 |
Numbers Expressed as Numerals or as Words |
Add an example to the group of examples on p. 5 … 二十四の瞳 [Nijūshi no hitomi] … |
|
19 |
6.2.2.10.1 |
One
Part |
Suggest to add a Japanese example on p. 19 For Example: 夕霧 Yūgiri Part of 紫式部’s Genji monogatari Part of Murasaki Shikibu’s Genji monogatari [only report the form in Japanese without transliteration.] |
|
27 |
6.2.3.4 |
[2nd
example of the 1st group] Liang
nong zu zhi jia xu sheng chan he wei sheng cong shuLoạt sách về chăn nuôi thú y của FAO English language form
recorded as preferred title: FAO animal production and health series |
Suggestion: Break line between “ShuLoat” as: Liang
nong zu zhi jia xu sheng chan he wei sheng cong shu Loạt sách về chăn nuôi thú y của FAO English language form
recorded as preferred title: FAO animal production and health series (title in Chinese pinyin and Vietnam??) |
|
27 |
6.2.3.4 |
Alternative linguistic form of title for the work: Different script |
Add Japanese example under diff
script on p. 27 [2nd group of examples: … 般若心経 Japanese transliterated form recorded as preferred title: Hannya shingyō … |
|
|
6.2.3.5 |
Other Variant Title for the Work |
Need some CJK examples |
|
32 |
6.3.1.3 |
Recording Form of Work [last two examples] For Example: Motion picture Form of work of: Ocean’s eleven. A film released in
1960. Form recorded to differentiate this work from other works with the same
title For Example: Motion picture Form of work of: Ocean’s eleven. A film released in 2001. Form recorded to
differentiate this work from other works with the same title |
I have seen some examples
(scattered in RDA Chapter 6 and 25) relating to assigning uniform titles when
cataloging motion pictures. To me, these instructions are not practical
enough for catalogers to construct uniform titles in bibliographic and
authority records. LCRI — Chapter 25 Uniform Titles — 25.5. Additions — 25.5B. Appendix I provides us
with the guidelines on PCC practice, including full instructions and a series
of examples on when to assign uniform title(s) and how to resolve the
conflict by using the additional qualifiers, year of release, director or
filmmaker, production company. Let me cite one of the examples from
25.5B Appendix I: 130 0# $a King Kong (Motion picture : 1933) 245 10 $a King Kong ... 260 ## $a Hollywood : $b RKO Radio Pictures, $c 1933. 130 0# $a King Kong (Motion picture : 1976) 245 10 $a King Kong ... 260 ## $a Hollywood : $b Paramount Pictures, $c 1976 ... Suggestion: Retain LCRI
instruction. |
|
35 |
6.4.1.3 |
Recording
Date of Work [first
two examples] For Example: 1960 Date of release of
the motion picture Ocean’s eleven. Date recorded to differentiate this work from
other works with the same title For Example: 2001 Date of release of the
motion picture Ocean’s eleven. Date recorded to differentiate this work from
other works with the same title |
See
comments and suggestion above. |
|
44 |
6.9.1.3 |
Recording
Identifiers for Works |
It may be nice to have DVD barcode example |
|
73 |
6.15.3.4 |
Recording
Alternative Linguistic Forms as Variant Titles for Musical Works |
[Reported under a separate response to 5JSC/LC/12/LC follow-up. ] |
|
126-127 |
6.23.3.4 |
Recording
Alternative Linguistic Forms as Variant Titles for Religious Works |
Reorganize examples like 6.2.3.4 will be helpful and consistent. Highlight captions in boldface. |
|
19 |
7.13.2.3 |
Recording
Scripts Record the script or scripts used to express the language content of the resource using one or more of the terms listed in ISO 15924 (http://www.unicode.org/iso15924/codelists.html). |
Given example made me feel ignorant and wasn’t very
helpful. Also I wasn’t sure why the ISO 15924 link was provided for this
chapter when I saw this example. Add another example with scripts with more
apparent contrast and easier to understand |
|
31 |
7.17.3.3 |
Recording Colour of Moving
Images |
Order of guideline and examples do not correspond |
|
35 |
7.19.1.3 |
Recording Aspect Ratio [1st group of
examples on p. 35] ForExample: widescreen (2.35:1) full screen (1.33:1) widescreen (1.85:1) full screen (1.33:1) Resource
includes both versions |
It is not clear that which lines correspond to “Resource includes both versions.” |
|
39 |
7.22.1.3 |
Playing Time, Running Time, etc. Optional Addition |
Would like to see examples that illustrate the instruction |
|
16 |
8.13.1 |
Basic Instructions on Making Cataloguer’s Notes |
It may be helpful to include an example for non-Latin script reference(s) in name authority records in this section. Suggested examples to be added: Prefers that Chinese form of name be used in bib. records for items in Chinese and that Lee, James Z. be used as heading in records for items in English. (from Lee, James Z., 1952- LCCN n 96080631) For works of this author entered under other names, search also under Ye, Shan or Wang, C.H. (Ching-hsien), 1940- ) (from Yang, Mu, 1940- LCCN n 81069280) Works by this author are entered under the name used in
the item. For a listing of other names used by this author, search also under
Yang, Mu, 1940- (from Ye, Shan LCCN n
81071768) Works by this author are entered under the name used in the item. For a listing of other names used by this author, search also under Yang, Mu, 1940- (from Wang, C.H. (Ching-hsien), 1940- LCCN n 98097575) Dōshisha Eigakkō, est. Nov. 1875 (from LCCN n 79095562) |
|
6 |
9.2.2.5.1 |
The last example on p.6 |
Assuming “I.C. Mcllwaine “ is a person, the preferred name
requires a space before “C” following RDA 8.5.6 a). |
|
12 |
9.2.2.5.3 |
Names Written in a Non-Preferred Script [2nd example] For
Example: Li
An Name appears in original script as:李安 Jamāl ʿAbd al-Nāṣir Name appears in original script as:جمال عبد الناصر |
Two examples mush together, should use line break to break them up. Change to: For Example: Li An Name
appears in original script as:李安 Jamāl
ʿAbd al-Nāṣir Name appears in original script as:جمال عبد الناصر |
|
12 14 |
9.2.2.5.3 |
Names Written in a Non-Preferred Script [2nd example] For
Example: Li
An Name appears in original
script as:李安 [2nd
example] For
Example: Ang Lee Name appears in original script as: 李安 |
p. 12 on “Li, An” under instruction of recording as preferred & p. 14 on “Ang Lee” under recording as variant Should these two be swapped? since this is an established authority, and from North American catalogers’ view, it would be confusing? Or is it matter since RDA intended to be used internationally, in this case? |
|
12, 15 |
9.2.2.5.3 |
Names written in a Non-Preferred Script [4th example (Korean)] For Example: Yi Sŭng-man Name appears in original script as:李承晚 [1st example] For Example: Syngman Rhee Name appears in original script as: 李承晚 |
Yi Sung-man is listed in p. 15 following ‘an alternative instruction’ because he is the first president of South Korea. His name is established in English, well-accepted form in USA as a Syngman Rhee. Yi Sung-man is currently a cross reference of Syngman Rhee. I think it’s better to replace Yi Sung-man example with somebody else whose heading is a preferred Access Point Representing a Person in this section. Listing Yi Sung-man here is not wrong but it’s not ideal either. Suggest to replace it with the following example: Cho
Man-sik Name appears in original script as: 조만식 |
|
12 |
9.2.2.5.3 |
Names Written
in a Non-Preferred Script Last example |
there is the following typo in the example A.N. Scriabin (the example is only partially in Cyrillic): It should be: Name appears in original script as А.Н. Скрябин This same error is repeated on p. 15. |
|
18-21 |
9.2.2.8 |
Individuals with More Than One Identity |
Suggest
to add Chinese examples using 衛斯理 (Wei Sili), 原振俠(Yuan
Zhenxia) and 倪匡 (Ni Kuang) For Example 倪匡[Ni Kuang] Real
name for most of his works For Example 衛斯理[Wei Sili] Pseudonym
used by倪匡in one of his series For Example 原振俠
[Yuan Zhenxia] Pseudonym
used by倪匡in one of his series |
|
22-23 |
9.2.2.8 |
Individuals with More Than One Identity Exception |
There
are no non-Roman examples (and in the linked 9.2.3.4 under Exception (p. 22)
there are none). Should there be? a good example under the
"Exception" (and 9.2.3.4) would be 魯迅 (周树人) Suggest
to add to the group of examples under Exception instruction … Lu Xun
not Zhou Shuren … |
|
25 |
9.2.2.9 |
[examples]: Read, Miss Strong, Harold, Mrs. |
|
|
7 |
10.2.3.4 |
[Example under Alternative Linguistic Form of Name] Different
Script [Insert
script] Chinese
transliterated form recorded as preferred name: Li |
Supply scripts Different Script [Insert script] (supply 李 黎 厉 etc. ??) Chinese
transliterated form recorded as preferred name: Li |
|
7 |
11.2.2.5.2 |
More than One Language Form of the Name If the name appears in
different languages, choose the form in the official language of the body as
the preferred name. ForExample: Comité
français de la danse not French Committee of the Dance |
Suggest to add a Mongolian example under the instruction. ForExample: Comité
français de la danse not French Committee of the Dance Mongolyn Burkhany Shashny Urlakhuĭ Ukhaany Dėėd Surguulʹ not Mongolian Institute of Buddhist Art not 몽골불교미술대학 |
|
18-19 |
11.2.2.10 |
[2rd] ForExample: Automobiltechnische
Gesellschaft not Automobiltechnische Gesellschaft [3rd] ForExample: Daiwa Ginkō not Daiwa Ginkō Kabushiki Kaisha |
2nd Examples: The second example (German): [Comments 1] Preferred and non-preferred headings are same. [Comments 2] the second line lacks the term indicating incorporation in German. The third example (Japanese): the second line includes a typo. The Japanese word for bank should end with “o” with a macron as shown in the first line. Daiwa Ginkō not Daiwa Ginkō Kabushiki Kaisha Add example after the 3rd?: Samsŏng Chŏnja
(LCCN n 85022222) not Samsŏng Chŏnja Chusik
Hoesa |
|
20 |
11.2.2.10 |
[1st group examples] ForExample: Stockholms
handelsbank, Aktiebolaget not Aktiebolaget Stockholms handelsbank Forstprojektierung
Potsdam, VEB not VEB Forstprojektierung Potsdam |
Suggestion: add a Korean example in the 1st group? Kʻoria Pʻikchʻyŏsŭ (Chu) not (Chu) Kʻoria Pʻikchʻyŏsŭ ‘(Chu)’ here means Ltd.
|
|
20 |
11.2.2.10 |
Omit an initial word or phrase in an oriental language
indicating the private character of a corporate body (e.g., Shiritsu, Si
li), unless the word or phrase is an integral part of the name. ForExample: Dong hai da xue not Si li Dong hai da xue but Shiritsu Daigaku
Toshokan Kyōkai |
Suggestion: add Korean example
[Hisami
prefers 2-3 over 1] ForExample: Dong hai da xue not Si li Dong hai da xue Kōchi Gakugei Kōtō
Gakkō (LCCN nr 93026096) [2] not Shiritsu Kōchi Gakugei Kōtō
Gakkō Hakusai
Byōin
(LCCN n
2004123900) [3] not Shiritsu Hakusai
Byōin Taehan Pulgyo Chinhŭngwŏn not Chaedan Pŏbin Taehan Pulgyo
Chinhŭngwŏn (OCLC# 39256723) but Shiritsu Daigaku Toshokan Kyōkai but Sarip Hakkyo
Kyowŏn Yŏnʼgŭm
Kwalli Kongdan (Korea) |
|
22 |
11.2.2.12 |
Transliteration |
Suggestion: add Korean entry as a 4th example just to show Korean alphabet, Hangul before instruction “alternative” paragraph. ForExample: Hanʼgukhak Chungang Yŏnʼguwŏn Name appears in original script as: 한국학 중앙 연구원 |
|
22 |
11.2.2.12 |
Transliteration [group of examples under Alternative] ForExample: Zhongshan daxue not Zhongshan da xue |
Delete space to bring “xue” in line with “Zhongshan da” ForExample: Zhongshan daxue not Zhongshan da xue |
|
37 |
11.2.2.19 |
[1st]ForExample: United States.
National Labor Relations Board. Library Name: Library Niger. [2nd] ForExample: Commissariat général au développement. Centre de
documentation Name: Centre de documentation |
Type 3 Examples. Delete “Niger” from the first example; add “Niger” and a full stop at the beginning of the second example. [1st]ForExample: United States.
National Labor Relations Board. Library Name: Library [2nd] ForExample: Niger.
Commissariat
général au
développement. Centre de documentation Name: Centre de documentation |
|
45 |
11.2.2.21.2 |
Heads of Governments 2nd group of examples ForExample: Swaziland. Prime
Minister Managua
(Nicaragua). Alcaldía King County
(Wash.). Executive Japan. Naikaku
Sōri Daijin Thailand. Nāyok Ratthamontrī |
Suggestion: add Korean example Korea (South). Kungmu Chʻongnisil |
|
50 |
11.2.2.22.1 |
Legislative Bodies 1st group of examples ForExample: Iceland. Alþingi Idaho. Legislature |
Suggestion: add a Korean example? Korea (South). Kukhoe |
|
58 |
11.2.2.25.1 |
[examples] Germany. Heer. Panzerdivision, 11. Germany. Heer. Armeekorps, XIII. Germany. Luftwaffe. Fallschirmjägerdivision, 9. Germany. Kriegsmarine. Unterseebootsflottille, 7. Soviet
Union. Raboche-Krestʹi͡anskai͡aKrasnai͡aArmii͡a. Vozdushnai͡aarmii͡a, 5. |
All five examples from the bottom have a period at the end. Does it necessary unless it means something together with the numbers. [inconsistent with the rest of examples] |
|
58 |
11.2.2.25.1 |
Armed forces |
Suggestion: If CJK also follows this rule without exception, shall we add a CJK example? There is a little pecuriarity so it’s better to show an example. Korea (South). Yukkun. Sadan, Che 1. Yŏndae, 11 |
|
61 |
11.2.2.26 |
Embassies, Consulates, etc ForExample: Canada. Embassy
(Belgium) Germany.
Gesandtschaft (Chile) India. High
Commission (Trinidad and Tobago) Serbia. Poslanstvo
(Romania) United States. Legation (Sweden) |
Suggestion: add a Korean example in the 2nd group since there is no CJK example? Korea (South). Taesagwan (U.S.) |
|
64 |
11.2.2.28 |
Councils, etc. 2nd example ForExample:’ Catholic Church.
Concilium Plenarium Americae Latinae not Catholic Church. Concilio Plenario de la América Latina not Catholic Church. Concilio Plenario de América Latina not Catholic Church. Concílio Plenário da América
Latina not Catholic Church. Concilio Plenario dell’America
Latina Form of name presented in
first resource received: Concilii
Plenarii Americae Latinae. Forms presented in resources received later: Concilio
Plenario de la América Latina; Concilio Plenario de América Latina; Concílio
Plenário da América Latina; Concilio Plenario dell’America Latina |
The heading and the name in the source to support do not match. |
|
64 |
11.2.2.28 |
[1st example in 3rd group] Catholic Church. Province of Baltimore (Md.). Provincial Council |
The subordinate body’s name broke off, put it together, ‘Provincial Council.’ Catholic Church. Province of Baltimore (Md.). Provincial Council |
|
76 |
11.2.3.6 |
Alternative
Linguistic Form of Name |
Can we add a Korean example here? Korea (South). Embassy (U.S.) Korea language from recorded in preferred name: Korea (South). Taesagwan (U.S.) Can we add a Korean transliterated form for United Nations for the 3rd example in the 1st group? … Kukche Yŏnhap … English language form recorded as preferred name: United Nations |
|
78 |
11.2.2.6 |
For Example: 27 Knygos
mėgėjųdraugija Dvidešimt septynių Knygos mėgėjų draugija Form beginning with a number expressed as a numeral recorded as preferred name: XXVII Knygos mėgėjų draugija |
An extraneous line in the example that begins with “27 Knygos” should be deleted. |
|
96 |
11.4.2.3 |
Recording Date of Conference, etc. 1st and 2nd examples ForExample: 1978 February 13–15 Preferred name recorded as: Federal Provincial
Conference of First Ministers ForExample: 1978 November 27–29 Preferred name recorded as: Federal Provincial Conference of First Ministers |
|
|
97 |
11.4.3.3 |
[2nd example from the bottom] 1940 Preferred name recorded as: France. Access point represents the territory under German occupation from 1940 to 1944 |
Make the text bold beginning with ‘Access ….’ Consistent with the rest of examples 1940 Preferred
name recorded as: France. Access point
represents the territory under German occupation from 1940 to 1944 |
|
117 |
11.12.1.3 |
[in the middle of 2nd group of examples, the
caption] Local Place |
Should be bold |
|
118 |
11.12.1.3 |
Place Associated with the Body, Optional Addition |
[see comments listed under section 2] if this is the current practice in CJK community, can we add some CJK examples containing the country qualifiers with a brief explanation?
Hyŏndae Sahoe Yŏnʼguso (Korea) Di zhi kuang chan bu di zhi li xue yan jiu suo (China) [shi add chi example] [Shi]Suggest to retain LCRI regarding adding country qualifier for conflict and non-conflict The following submitted on the web form in addition to Erica’s comments: Add CJK examples with instruction that is retained or revised from related LCRI instruction: Hyŏndae Sahoe Yŏnʼguso (Korea) Di zhi kuang chan bu di zhi li xue yan jiu suo (China) |
|
127-128 |
11.12.2.1 |
General guidelines [3rd group of examples of 11.12.2.1] ForExample: Concours Eurovision
de la chanson English language form recorded as preferred name: Eurovision
Song Contest Eurovisie
Songfestival Festival de la Canción de Eurovisión Festival Eurovisão da Canção Gran premio Eurovisione della canzone europea Grand Prix Eurovision de la chanson Söngvakeppni evrópskra sjónvarpsstöõva |
I
noticed that all the variant entries are listed together before the preferred
heading quite consistently in the RDA, except this one. Please see 16.2.3.6 and other parts of RDA. Suggest to list all 7 variant forms together before the preferred form as the following: ForExample: Concours Eurovision
de la chanson Eurovisie
Songfestival Festival de la Canción de Eurovisión Festival Eurovisão da Canção Gran premio Eurovisione della canzone europea Grand Prix Eurovision de la chanson Söngvakeppni
evrópskra sjónvarpsstöõva English language form recorded as preferred name: Eurovision
Song Contest |
|
|
16.2.2.7 |
Change of Name |
Suggest to add an Mongolian example Ih Ju Meng Name changed to : Ordos Shi [E’erduosi
Shi] Not added into Web form of the
following: 鄂尓多斯市 (Ordos Shi)--old
伊克昭盟 (Ih Ju Meng) |
|
15 |
16.2.3.6 |
Alternative Linguistic Form of Name For Example: Different script [1st
example on p.16] [Insert script] English language form
recorded as preferred name: Japan |
Suggest to insert script for Japanese: 日本 Nihon Nippon English Language form recorded as preferred name:
Japan Suggest
to add Korean and Mongolian examples 서울 (Korea) Sŏul (Korea) Korean language form recorded as preferred name: Seoul (Korea) 呼和浩特 Huhehaote English
language form recorded as preferred name: Hohhot 伊克昭盟 Yikezhao
Meng English
language form recorded as preferred name: Ih Ju Meng Scripts
for other languages also need to be fix. |
|
18 |
16.2.3.7 |
Other variant name |
The entries in 2nd group are repeated. Delete the whole 2nd group. |
|
4 |
25.1.1.3 |
Referencing Related Works [3rd example in
the group of examples under Preferred Access Point Representing the Related Work]Remake of: Psycho (Motion
picture : 1960) Resource described: Psycho / Universal Pictures and Imagine Entertainment ; screenplay, Joseph Stefano ; produced by Brian Grazer, Gus Van Sant ; directed by Gus Van Sant. Ashot-for-shot 1998 remake of the 1960 Alfred Hitchcock film |
I have seen some examples
(scattered in RDA Chapter 6 and 25) relating to assigning uniform titles when
cataloging motion pictures. To me, these instructions are not practical
enough for catalogers to construct uniform titles in bibliographic and authority
records. LCRI — Chapter 25 Uniform Titles — 25.5. Additions — 25.5B. Appendix I provides us
with the guidelines on PCC practice, including full instructions and a series
of examples on when to assign uniform title(s) and how to resolve the
conflict by using the additional qualifiers, year of release, director or
filmmaker, production company. Let me cite one of the examples from
25.5B Appendix I: 130 0# $a King Kong (Motion picture : 1933) 245 10 $a King Kong ... 260 ## $a Hollywood : $b RKO Radio Pictures, $c 1933. 130 0# $a King Kong (Motion picture : 1976) 245 10 $a King Kong ... 260 ## $a Hollywood : $b Paramount Pictures, $c 1976 ... Suggestion: Retain LCRI instruction. |
4. Typographical errors (other than in examples) in instruction number order
|
Page |
Instruction # |
Text |
Questions/ Comments/ Suggestion |
|
3 |
0.3.1 |
General |
When FRBR and FRAD appear for the first time, it is preferable to spell out the full titles instead of just the acronyms, although they are annotated in the footnotes 13 &14. |
|
12 |
0.6.2 |
Manufacturer's name (if neither publisher nor distributor i;
....) |
The 'i' at the end should be 'identified'? |
|
4 |
1.2 |
[The last sentence]… differentiating one resource fromanother. |
typo “fromanother”
should be two words, need to insert a space. |
|
8 |
1.5.2 |
a) a resource issued as a
single unit (e.g., a single audio disc, or a PDF document) |
Typo: 3.1.3 should be 3.1.4 |
|
9 |
1.5.4 |
[The last sentence] … in the form of a hierarchical description, see appendix
D (D.1.3 ). |
Typo: D.1.3 should be D.2. |
|
10 |
1.6.1.1, 1.6.2.1, 1.6.3.1 |
Create a new description if
there is a change in the mode of issuance (see 2.14 ) of a ... |
Typo: 2.14 should be 2.13 |
|
12 |
1.7.3 |
[3rd paragraph] For
instructions on the use of prescribed punctuation for the display of
descriptive data in ISBD form, see appendix D (D.1.2 ). |
Typo: D.1.2 should be D.2.2 |
|
18 |
1.9.1 |
When recording dates appearing
on the source of information, apply the guidelines given under 1.8 . Apply the instructions given
under 1.10.3 when recording a supplied date … |
Typo: 1.8 should be 1.9 [should be ok to follow numeral rules]
Typo: 1.10.3 should be 1.9.2 |
|
22 |
1.10.2 |
Apply the instructions on the
capitalization of notes given in A (A.7 |
Typo: A.7 should be A.8 |
|
1 |
2.0 |
[3rd paragraph] … designated as core elements (see 1.3)RDA … and/or 4 Providing
Acquisition and Access Information), as necessary. |
Typo: (see 1.3) RDA should be (see 1.3 RDA)
Typo: “(“ should be inserted between RDA and Providing …. … and/or 4 (Providing Acquisition and Access Information), as
necessary. |
|
3 |
2.1.2.3 |
[3rd paragraph last
sentence] … see 2.7.6.2 , 2.8.6.2 , 2.9.6.2 , and 2.9.6.2
, respectively |
2nd “2.9.6.2“ should be 2.10.6.2 |
|
3 |
2.1.2.4 |
[last sentence of the page]… see 2.7.6.2 ,
2.8.6.2 , 2.9.6.2 , and 2.9.6.2 , respectively. |
The last sentence, Typo: Should be see 2.7.6.2 , 2.8.6.2 , 2.9.6.2 ,
2.9.6.2 and 2.10.6.2
respectively. |
|
11 |
2.3.1.1 |
a) title proper (see 2.3.3 RDA) d) parallel other title information (see 2.3.4 RDA) should be 2.3.5 g) later variant title (see 2.3.7 RDA) should be 2.3.8 h) key title (see 2.3.8 RDA) should be 2.3.9 i) abbreviated title (see 2.3.9 RDA) should
be 2.3.10 |
2.3.11 Typo: a) title proper (see 2.3.3 RDA) should be 2.3.2 d) parallel other title information (see 2.3.4 RDA) should be 2.3.5 g) later variant title (see 2.3.7 RDA) should be 2.3.8 h) key title (see 2.3.8 RDA) should be 2.3.9 i) abbreviated title (see 2.3.9 RDA) should
be 2.3.10 |
|
27 |
2.3.2.9 |
[2nd paragraph] ... in the order in which they appear in the resource. [1.1G3 ] |
[1.1G3 RDA] does not exist. |
|
45 |
2.3.6.3 |
[last
sentence] Make a note on the source or basis for the variant title (see 2.20.3.3 ) |
Typo: 2.20.3.3 should be 2.20.2.3 |
|
51 |
2.3.8.3 |
[1st paragraph on p. 51] Make a note on the numbering or publication dates to
which the change in title applies (see 2.20.2.4 |
3rd paragraph, 2.20.2.4
RDA may be a wrong number |
|
59 |
2.4.1.1 |
[5th paragraph] For
statements identifying performers, narrators, and/or presenters in a motion
picture or video recording, see the instructions given under 7.20 [6th paragraph] For statements identifying persons who have contributed
to the artistic and/or technical production of a motion picture or video
recording, see the instructions given under 7.21 |
2.4.1.1 5th paragraph, Typo: 7.20 should be 7.23. 6th paragraph, Typo: 7.21 should be 7.24. |
|
63 |
2.4.1.5 |
[last paragraph on p. 63] … a
statement identifying performers, narrators, and/or presenters (see 7.20 ). |
Typo: 7.20 should be 7.23. |
|
107 |
2.7.1.5.1 |
[ 3rd paragraph] If
the changes have been numerous, make a general note (see 2.20.6.4.1 ). |
Typo: 2.20.6.4.2 should be 2.20.6.4.1 |
|
112, 114 |
2.7.2.7, 2.7.4.8 |
For instructions on recording a
change in place of production, see 2.7.2.5
. For instructions on recording
a change in producer’s name, see 2.7.2.5
. |
Typo: 2.7.2.5 should be 2.7.1.5 |
|
117 |
2.7.6.6 |
Apply the instructions on
supplied dates given under 1.10.3 . |
Typo: 1.10.3 should be 1.9.2 |
|
126, 130 |
2.8.2.7, 2.8.4.8 |
For instructions on recording
a change in place of publication, see 2.8.2.5 For instructions on recording
a change in publisher’s name, see 2.8.2.5 |
Typo: 2.8.2.5 should be 2.8.1.5 Typo: 2.8.2.5 should be 2.8.1.5 |
|
136 |
2.8.6.6 |
[Optional addition] Apply the
instructions on supplied dates given under 1.10.3
. |
Typo: 1.10.3 should be 1.9.3 |
|
|
|
|
2.9.2.7 Typo: 2.9.2.5 should be 2.9.1.5 2.9.6.3 3rd paragraph, Typo: 2.20.8 should be 2.20.8.3 2.9.6.6 Typo: 1.10.3 should be 1.9.3 2.10.1.2 a), Typo: 2.3.3 should be 2.2.2 2.10.2.2 b), Typo: 2.2.3 should be 2.2.2 2.10.3.2 a), (see ) should be (see 2.10.2.2) b), Typo: 2.2.3 should be 2.2.2 2.10.4.2 a), Typo: 2.3.3.2 should be 2.3.2.2 b), Typo: 2.2.3 should be 2.2.2 2.10.5.2 b), Typo: 2.2.3 should be 2.2.2 2.10.6.6 Typo: 1.10.3 should be 1.9.3 2.12.5.3 Typo: 2.3.3.3 should be 2.3.5.3 2.12.13.3 Typo: 2.3.3.3 should be 2.3.5.3 2.13.1.2 Typo: “the mode o issuance” should be “the mode of issuance“ 2.15.1.1 The last sentence, Typo: 4.5 should be 4.6 2.19.1.3 Typo: 2.16 should be 2.15 2.20.6.4.2 Alternative, “f the changes” should be “If the changes” 2.20.8.4.2 Typo: 2.9.1.5.2 should be 2.9.1.5.2 RDA 2.20.12.3.1
Typo: 2.6 should be 2.6 RDA |
|
2 |
8.1.2 |
Person, Family, and Corporate Body The term corporate body refers to an organization or group of persons and/or organizations that is identified by a particular name and that acts, or may act, as a unit. |
The term corporate body refers to an organization or
group of persons |
|
4 |
8.3 |
[Core elements] Field of activity of the person (for a person who[se]) |
Missing character |
|
5 |
8.3 |
End of first sentence on p.5 |
8.1.3 RDA should be 8.11.RDA |
|
5 |
8.5.1 |
[General guidelines] … given under 8.5.3–8.5.7 |
8.5.3 should be 8.5.2 |
|
9 |
8.6 |
Preferred Access Points Representing
Persons, Families, and Corporate Bodies If two or more persons, families, or corporate bodies have the same or similar names, add to the preferred name an element or elements such as a date, a place name, or other distinguishing term, following the instructions on additions to names of persons (see 9.1.1.1) additions to names of families (see 10.10.1), and additions to names of corporate bodies (see 11.12.1.1), as applicable. |
there is no 9.1.1.1 in RDA chapter 9 |
|
10 |
8.7 |
Variant Access Points Representing
Persons, Families, and Corporate Bodies Make additions to the name, if considered important for identification, applying the instructions on additions to names of persons (see 9.1.1.1 ) additions to names of families (see 10.10.1), and additions to names of corporate bodies (see 11.12.1.1 ), as applicable. |
there is no 9.1.1.1 in RDA
chapter 9 |
|
2 |
9.2.1.1 |
[end of second line] isknown |
Need to insert space |
|
3 |
9.2.2.2 |
a) the preferred sources of information (see 2.2.3 ) in resources associated with the person |
(see 2.2.3 ) should
be (see 9.2.2.3) |
|
3 |
9.2.2.2 |
For additional instructions on names of persons that appear in more than one language form and names written in a script that differs from the preferred script of the agency creating the data, see 9.1 –9.2 . |
“see 9.1-9.2” should be 8.2? |
|
4 |
9.2.2.3 |
For additional instructions on choosing the preferred name for a person known by more than one form of the same name or by more than one name, see 9.2.2 –9.2.2.8 |
see 9.2.2 - 9.2.2.8 Is it better to change to 9.2.2.5 - 9.2.2.8? more specific number? |
|
|
9.2.3.3 |
[3rd paragraph] ‘orfound’, ‘name,that’ |
Need to insert space |
|
|
9.3.1.2 |
‘anysource’ |
Need to insert space |
|
|
|
|
Need to insert
space |
|
7 |
9.2.2.5.2 |
If the name chosen is written in a script that differs from the preferred script of the agency creating the data, apply the instructions given under 9.2 |
Specify/clarify the instruction given under 9.2. Is 9.2.2.2 more helpful? |
|
13 |
9.2.2.5.3 b) |
[last sentence of the last paragraph] for the original language of most of the works . |
Need to delete
space |
|
28, 30, 32 |
9.2.2.10, 9.2.2.11, 9.2.2.12 |
Rule referencing: Record a name … applying the general guidelines on recording surnames given under 9.2.1.9 |
Rule 9.2.19 is not in this draft, requiring adjustment, replace
it by 9.2.2.9? |
|
43 |
9.2.2.23 |
Record the forename as the first element. Record words or phrases denoting place of origin, domicile, occupation, or other characteristics that are commonly associated with the name applying the instructions given under 9.2.14.1 |
Rule 9.2.14.1 is not in this draft! Could this be
9.2.2.14? |
|
71 |
9.4.1.6. |
[end of the first sentence] Record Pope as the title of a pope . |
Need to delete
space |
|
73 |
9.4.1.8 |
For Thai names in religion,
see also F.10.1.4 |
There
is no F.10.1.4; F.10 is for Romanian names.
This is a Typo. F.11.1.4 RDA is
on Tahi Buddhist monastics, Ecclesiastics and Patriarchs.
|
|
|
9.2.2.2 |
[Sources of Information] a) (see 2.2.3) |
should be 9.2.2.3? |
|
|
|
end of the section, see 9.1-9.2 |
should be 8.2? |
|
|
9.2.2.3 |
[Choosing The Preferred Name, 3rd line] |
|
|
98 |
9.19.1.4 |
… distinguish one access point
from another (see9.19.1.3) |
Need to insert space |
|
100 |
9.19.1.6 |
If none of the elements specified under 9.19.1.3 –9.19.1.6 is available to distinguish … |
“ 9.19.1.6” should be “9.19.15” |
|
4 |
10.2.2.5 |
Apply the instructions given under 9.2.1 , as applicable, for family names that vary in fullness (see 9.2.1.1 ), language (see 9.2.1.2 ), script (see 9.2.1.3 ), or spelling (see 9.2.1.4 ). |
The paragraph requires major revision since RDA 9.2.1.1, 9.2.1.2, and 9.2.13 are not on ‘fullness’, ‘language’ and ‘script’. Moreover this draft lacks RDA 9.2.1.4. |
|
4 |
10.2.2.6 |
|
Typo: “10.6’ should be “10.7”?? |
|
3 |
11.2.1.3 |
[2nd line]
‘generalguidelines’ |
Need to insert space |
|
3 |
11.2.2.1 |
If a body changes its name, a preferred name is chosen for use with resources associated with the new name (see 11.2.2 ). |
Typo in the 2nd sentence: “see 11.2.2 RDA” should be “see 11.2.2.3” |
|
4 |
11.2.2.4 |
In applying this general guideline, apply the instructions given under 11.2.1.7 –11.2.1.12 . |
The last sentence. Typo: “11.2.1.18-11.2.1.27” should be “11.2.2.18-11.2.2.27” |
|
23 |
11.2.2.13 |
Exceptions For instructions on recording the names of subordinate
government bodies, see . For instructions on recording the names of subordinate religious bodies, see . |
The first two sentences under “Exceptions” are incomplete. Supply “11.2.2.19-11.2.227.” to complete the first sentence. Add “11.2.2.30-11.2.2.31” to complete the second sentence. |
|
4-5 |
11.2.2.4 |
[end of 2nd paragraph] apply the instructions given under 11.2.1.7 –11.2.1.12. [end of 3rd parag. P. 5] For instructions on recording the names of subordinate and related bodies, see 11.2.1.13 –11.2.1.17 |
11.2.1.7 – 11.2.1.12 - not exist 11.2.1.13 – 11.2.1.17 - not exist |
|
5 |
11.2.2.5 |
[within 3rd paragraph, 3 places] ‘information,choose’, ‘ispresented’, ‘commonlyfound’ |
Need to insert space |
|
32 |
11.2.2.16 |
Record the name of a body … applying the basic instructions given under 11.2.0 |
This draft lacks “11.2.0 RDA” |
|
33 |
11.2.2.16 |
If …, record the name of the joint unit as a subordinate body applying the instructions given under 11.2.3 |
This draft lacks “11.2.3 RDA” |
|
34 |
11.2.2.18 |
Record the name of a body created or controlled by a government applying the basic instructions given under 11.2.1.4, unless … |
This draft lacks “11.2.1.4” |
|
35 |
11.2.2.18 |
… applying the instructions given under 11.2.3 –11.2.2.16 |
“11.2.3” should be “11.2.2.3” |
|
44 |
11.2.2.21.1 |
[the last line of the page] ‘ofincumbency’ |
Need to insert space |
|
45 |
11.2.2.21.2 |
If the official language
identified is a specific incumbent of the office, add, in parentheses,
the inclusive years of the incumbency and the name of the person in a brief
form and in the language of the preferred name for that person. |
[Comment 1] first line of last parag. ‘language’ should be ‘being’ If the official being
identified is a specific incumbent of the office or [Comment 2] should begin with: "If the official identified is a ....." |
|
|
11.2.2.21.4 |
[3rd line in the 1st parag.] If …, apply the instructions given under 11.2.1.1c |
11.2.1.1c – not exist |
|
48 |
11.2.2.21.5 |
For any official not covered under 11.2.7.2 –11.2.7.5 , use … |
This draft lacks “11.2.7.2-11.2.7.5RDA” |
|
53 |
11.2.2.24 |
[1st parag. ] Record the
names of courts as instructed under 11.2.2.14.1 |
11.2.2.14.1 should be 11.2.2.24.1 |
|
66 |
11.2.2.29.2 |
…, and the pontifical name recorded in the form prescribed under 9.2.12 |
Typo in the paragraph following the example: “9.2.12” should be “9.2.2.18” |
|
67 |
11.2.2.30 |
… record the names of
subordinate religious bodies according to the instructions given under 11.2.113 For religious orders and societies, see 11.2.1.1.5.2 |
This draft lacks “11.2.113 RDA” in the first paragraph and “11.2.1.5.2” in the second paragraph. |
|
84 |
11.3.1.2 |
[2nd line]
‘bodyfrom’ |
Need to insert space |
|
102 |
11.6.1.3 |
Record other designations associated with the corporate body applying the instructions given under 11.7.1.4 –11.4.1.8 , as applicable. |
This draft lacks “11.7.1.4” and “11.4.1.8 “ |
|
106 |
11.6.1.5 |
[in the parag.] ‘satisfactorydistinction’ |
Need to insert space |
|
1-2 |
16.0 16.2.2.1 |
[2nd line in
the 2nd parag.] The names of places
are commonly used as the names of governments (see 11.2.2.5.4d [3rd lind] The preferred
name for the place is the name or form of name chosen to represent a
place when a place name is used as the name of a government, etc. (see 11.2.2.5.4d) |
11.2.2.5.4d - not exist |
|
2 |
16.2.1.3 |
Record the name of a place in the form found in the source from which the name is taken, unless the instructions given under 16.2.1.8-16.2.1.13 |
This draft lacks “16.2.18-16.2.1.13RDA” |
|
3 |
16.2.2.3 |
For additional instructions on choosing between different
language forms of the name, see 16.2.1.6 . For instructions on change of name, see 16.2.1.7 . |
This draft lacks “16.2.1.6RDA” and “16.2.1.7RDA” 16.2.1.6 should be 16.2.2.6 16.2.1.7 should be 16.2.2.7 |
|
3 |
16.2.2.4 |
… unless the instructions
given under 16.2.1.8–16.2.1.13 indicate otherwise … listed in 16.2.1.9.1 or 16.2.1.10.1 … applying the instructions
given under 16.2.1.9– 16.2.1.13. If the place name is being used as the conventional name for a government (see 11.2.2.10.5d ), … |
This draft lacks “16.2.1.8-16.2.13RDA” and “11.2.2.10.5d RDA”
16.2.1.8-16.2.13 should be 16.2.2.8 – 16.2.2.13 16.2.1.9.1 should be 16.2.2.9.1 16.2.1.10.1 should be 16.2.2.10.1 16.2.1.9– 16.2.1.13 should be 16.2.2.9-16.2.2.13 |
|
6 |
16.2.2.7 |
a) the instructions on
government names (see 11.2.2.10.5d ) (e.g., use Nyasaland or Malawi, as appropriate)
or b) the instructions on
additions to corporate names (see 11.2.2.10.3 ) and conference names (see 11.2.1.8 ) or c) other relevant instructions in chapter chapter 11 |
“11.2.2.10.5d RDA”, “11.2.2.10.3RDA”, “11.2.1.8” not in this draft. c) The word, chapter is repeated, delete one or replace by specific rule no. |
|
8, 9, |
16.2.2.9.2, 16.2.2.10.2 |
applying the instructions given under 16.2.1.4 |
This draft lacks “16.2.1.4” |
|
10 |
16.2.2.11, 16.2.2.12, |
Record as part of the name of
a place not covered by 16.2.1.9–16.2.2.10 … If recording the name of the
larger place or jurisdiction as part of the name as instructed in 16.2.1.9–16.2.2.11 |
16.2.1.9-should be 16.2.2.9 |
|
11 |
16.2.2.13 |
… in the instructions given
under 16.2.1.8–16.2.2.12 |
16.2.1.8 should be 16.2.2.8 |
|
12 |
16.2.3.3 |
Apply the additional specific instructions given under 16.2.2.4-16.2.2.7 |
Typo: “16.2.2.4-16.2.2.7” should be “16.2.3.4-16.2.3.7” |
|
18 |
16.2.3.7 |
Record other variants and variant forms of the name recorded as the preferred name not covered under 16.2.2.4–16.2.2.6 as required. |
Typo: “16.2.2.4-16.2.2.6” should be “16.2.3.4-16.2.3.6” |
|
1 |
Appendix J J.2.2 |
|
May need indentation after adaptation of (work). adaptation of (work) … dramatization of (work) … motion picture
adaptation of (work) … novelization
of (work) … radio adaptation (work)… May need indentation after imitated as (work). imitated
as (work) … parodied as (work) … |
|
7 16 |
Appendix J J.3.6, J.2.6 |
Relationship designators: relationship between works, expressions, manifestations, and items J.3.6 Sequential work relationships J.2.6. Sequential expression relationships (should be J.3.6) |
Rule # typo that should be swapped for these two sections. J.3.6 Sequential work relationships (should be J.2.6) J.2.6. Sequential expression relationships (should be J.3.6) |