2A CATALOGING IN RDA

2A CATALOGING

This statement is in response to questions stimulated by 2A cataloging done under RDA.  2A cataloging is a cataloging technique applied to certain unnumbered (or, rarely, partially numbered) multipart sets classified as a collection and not analyzed.  Such materials are judged of significance primarily as a group; individual items are not considered significant enough to catalog separately.  Though the set is "made up" because the individual items lack numerical designation, the individual items in the set are usually closely related by subject and other strong similarities, such as title (or parts of title), issuing body, or publisher.

With respect to the inventory aspect of 2A cataloging under RDA, we want on the one hand to make it clear in the bibliographic record the state of the material as it was issued by the publisher but on the other hand to state clearly the rearrangement/repackaging that LC has done.  Thus, the extent statement (300 $a) expresses the number of volumes as issued by the publisher, and a copy-specific 500 note expresses the rearrangement done by LC.

Example illustrating complete 2A set (LCCN 2011308398):

300 ## $a 7 volumes : $b chiefly color illustrations ; $c 22 x 28 cm

500 ## $a LC copy bound together in 1 volume subsequent to publication.

          $5 DLC

Enum. area of item record: v. 1-7

Example illustrating complete 2A set (LCCN 2011311219):

300 ## 14 volumes : $b illustrations, maps ; 25 cm

500 ## LC copy bound together in 2 volumes subsequent to publication. $5 DLC

Enum. area of each item record: v. 1, no. 1-7

                                v. 2, no. 8-14

Note that in this example illustrating the LC rearrangement that is itself in more than one volume, the contents note must be done in such a way as to show the contents of each of the LC volumes.

Example illustrating a 2A incomplete multipart monograph (LCCN 2011308239):

264 #4 $a Quezon City, Philippines : $b Precious Pages Corporation, $c 2009-<2010>

300 ## $a volumes ; $c 18 cm

500 ## $a LC copy bound together in 2 volumes subsequent to publication.

          $5 DLC

Enum. area of each item record: v. 1, no. 1-3

                                v. 2, no. 4-6

Note that 264 subfield $c indicates the incomplete state of the set, only a generic extent is recorded in 300 $a while the set is still in progress; specific holdings are recorded in the holdings and item records.  However, note that the copy-specific 500 note is updated as more volumes are added to keep the information about the number of bound volumes accurate.

Example illustrating the binding together of a multipart monograph for reasons of economy          (LCCN 2011308247):

300 ## $a 6 volumes ; $c 17 cm

500 ## $a LC copy bound together in 1 volume subsequent to publication.

          $5 DLC

Enum. area of item record: v. 1-6

[Source: Library of Congress]

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

041 - Language Code (R) - MARC 21 Bibliographic - Full

• Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 041 [LC]
• 041  Language Code (R) [OCLC]

040 - Cataloging Source - MARC

Add subfield $d {MARC 21 code} when modifying NARs or SARs unless your institution's is already the last MARC subfield $d in the 040 field.

For example if LC is modifying agency, when making revisions to a NAR, we should add a $d DLC to the 040, if that is not the latest subfield present.

040 - Cataloging Source (NR)

RDA Blog posts on Cataloging Source - MARC 21 Field 040:

• 040 - Cataloging Source (NR)
• Identifying RDA Records
• 040 - Cataloging Source - MARC
• Field 040 Subfield Order

See also: 

• Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 040 [LC]
• 040  Cataloging Source (NR) [OCLC]

022 - International Standard Serial Number (ISSN) (R)

RDA Blog posts on 022  International Standard Serial Number:

• International Standard Serial Number (ISSN) - MARC to RDA Mapping
• 022 - International Standard Serial Number (ISSN) (R)

See also: 

• Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 022 [LC]
• 022  International Standard Serial Number (R) [OCLC]

RDA -- INTRODUCTION BACKGROUND AND HISTORY

Resource Description and Access (RDA) is a standard for cataloguing that provides instructions and guidelines on formulating data for resource description and discovery. Intended for use by libraries and other cultural organizations such as museums and archives, RDA is the successor to the Anglo-American Cataloguing Rules, Second Edition (AACR2), the current cataloging standard set for English language libraries. RDA was initially released in June 2010. In March 2012, the Library of Congress announced it will have fully implemented RDA cataloging by March 31, 2013. Several other national libraries including the British Library, Library and Archives Canada, National Library of Australia, and Deutsche Nationalbibliothek also planned to implement RDA in 2013.

Background

RDA emerged from the International Conference on the Principles & Future Development of AACR held in Toronto in 1997. It was quickly realised that substantial revision of AACR2 was required, which encouraged the adoption of a new title for what had been envisaged as a third edition of AACR.

The primary distinction between RDA and AACR is structural. RDA is organised based on the Functional Requirements for Bibliographic Records (FRBR). These principles identify both the 'user tasks' which a library catalog should make possible and a hierarchy of relationships in bibliographic data. Descriptions produced using the instructions of RDA are intended to be compatible with any coding schema, including the data environments used for existing records created under the AACR2 rules.

RDA is published jointly by the American Library Association, the Canadian Library Association, and the Chartered Institute of Library and Information Professionals (CILIP) in the UK. RDA instructions and guidelines are available through RDA Toolkit, an online subscription site, and in a print format. Maintenance of RDA is the responsibility of the Joint Steering Committee for the Development of RDA (JSC). The JSC is composed of representatives from the American Library Association, the Australian Committee on Cataloguing, the British Library, the Canadian Committee on Cataloguing, CILIP, Deutsche Nationalbibliothek, and the Library of Congress.

[Source: Wikipedia]

Designed for the digital world and an expanding universe of metadata users, RDA: Resource Description and Access is the new, unified cataloging standard.

Built on the foundations established by AACR2, RDA provides a comprehensive set of guidelines and instructions on resource description and access covering all types of content and media.

[Source: RDA Toolkit]

RDA -- INTRODUCTION BACKGROUND AND HISTORY

Background

RDA: Resource Description and Access was developed by JSC as part of its strategic plan (2005-2009) to replace the Anglo-American Cataloguing Rules, 2nd Edition Revised, which were first published in 1978.

RDA provides a set of guidelines and instructions on formulating data to support resource discovery.  RDA provides a comprehensive set of guidelines and instructions covering all types of content and media.

Details of how to subscribe to the RDA Toolkit can be found on the publisher’s website.

For a brief summary of RDA see the RDA Brochure (PDF format). The text of the brochure is also available in the following languages: Arabic; Catalan; Chinese; German; French (Canada); French (France); Persian [Word format]; Polish; Portuguese; Russian; Spanish; Swedish; Turkish. JSC also welcomes translations of RDA Supporting Documentation.

Work on the new standard began in 2004, and in the same year the Committee of Principals for AACR (CoP) appointed Tom Delsey as the Editor. In December 2004 a draft of part I of AACR3 was made available to the constituencies for review. In 2005 a new approach was agreed on, and the decision made to adopt the title: “RDA: Resource Description and Access”. In December 2005, the draft of RDA part I was made available for review. Further drafts of RDA chapters were issued in 2006 and 2007. At the October 2007 meeting, the JSC agreed on a new organization for RDA, see A New Organization for RDA. A full draft of RDA was issued in November 2008. JSC discussed the responses to the full draft at its meeting in April 2009 and the revised text was delivered to the publishers in June 2009.  RDA was published in the RDA Toolkit in June 2010.

RDA: Resource Description and Access is developed in a collaborative process led by the Joint Steering Committee for Development of RDA.  JSC gratefully acknowledges the contributions of the many institutions and individuals who have generously given their time and energies to the creation of RDA.

[Source: JSC RDA]

<<<<<---------->>>>>

RDA Blog : RDA Blog is a blog on Resource Description and Access (RDA), a new library cataloging standard that provides instructions and guidelines on formulating data for resource description and discovery, organized based on the Functional Requirements for Bibliographic Records (FRBR), intended for use by libraries and other cultural organizations replacing Anglo-American Cataloging Rules (AACR2). This blog lists description and links to resources on Resource Description & Access (RDA). It is an attempt to bring together at one place all the useful and important information, rules, references, news, and links on Resource Description and Access, FRBR, FRAD, FRSAD, MARC standards, AACR2, BIBFRAME, and other items related to current developments and trends in library cataloging practice.

RDA Blog History: RDA Blog was created by Salman Haider, a Cataloging & Metadata Librarian Blogger & Online Social Media Expert from India. RDA Blog embarked on its journey to provide useful information to Resource Description and Access (RDA) in August 2011. It received good response from librarians, catalogers, and library professionals from all around the world. It is interesting to note that the first hundred thousand pageviews to RDA Blog came in 3 years, but it took just 8 months to reach another hundred thousand pageviews. At present it is viewed at a rate of fifteen to twenty thousand times per month. RDA Blog is widely followed in social media.

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

RDA in OCLC WorldCat

For some months now, OCLC's WorldCat Quality Management Division has been planning and implementing a project to incorporate Resource Description and Access (RDA) practices, references, and examples into OCLC's Bibliographic Formats and Standards (BFAS) http://www.oclc.org/bibformats/en.html. We have thus far incorporated the changes to BFAS that were part of OCLC-MARC Update 2012 & 2013 (as documented in Technical Bulletin 261 & 262 http://oc.lc/zcWZjW).

We have now begun the larger job of reviewing BFAS in its entirety. Policies will be updated, links to Searching WorldCat Indexes http://oc.lc/5SfZ7D will be added, occasional references to RDA and the LC-PCC PSs will be incorporated, and some examples will be updated and others added to reflect RDA practices. This is a huge undertaking and will be happening gradually over time. Meanwhile, we have

brought together on the OCLC About RDA page http://www.oclc.org/rda/about.en.html links to LC, OCLC, other documentation about RDA, a new policy statement, and a webinar about it: http://oc.lc/2PC2UO. You will be seeing changes regularly as the BFAS Update Project progresses. Questions? AskQC@oclc.org.

[Source: OCLC message of the day through OCLC Connexion, August 23, 2013]

Inaccuracies

RDA Rule 1.7.9 is for "Inaccuracies". It instructs that When instructed to transcribe an element as it appears on the source, transcribe an inaccuracy or a misspelled word unless the instructions for a specific element indicate otherwise.

There are some exceptions to this rule, for example rule 2.3.1.4 of RDA.

It also instructs to make a note correcting the inaccuracy if considered important for identification or access (based on 2.17).

Also if the inaccuracy appears in a title and a corrected form of the title is considered important for identification or access, this RDA rule prescribes to record a corrected form of the title as a variant title.

[Source: Based on instructions from RDA Toolkit]

<<<<<---------->>>>>

See also:

• Transcription in Resource Description & Access (RDA) Cataloging
• Corrected Titles Proper & Variant Titles : RDA vs AACR2 : Questions and Answers & Best Practices
• Titles of Serials : LC-PCC Best Practices Guidelines

<<<<<---------->>>>>

Question: In a book the name of the author is "inaccurately" printed on title page, and correct name is given on pages inside the book. How to transcribe it?

Answer: Based on guidelines mentioned above transcribe "as it is" found on the title page in the subfield "c" of MARC tag 245. Then make a "Note" of it in MARC21 500 tag.

From above description we get "... ... make a note correcting the inaccuracy if considered important for identification or access (based on 2.17)".

[2.17.3--Note on Statement of Responsibility>>2.17.3.4--Variant Forms of Names-->Make notes on variant forms of names if: the names of persons, families, or corporate bodies appear in the resource in forms that are different from those recorded in the statement of responsibility and the different forms are considered important for identification.]

See lccn: 2014348021 in Library of Congress Catalog in MARC21 view. Also check the established Name Authority Record for the name printed inaccurately on title page.

Please provide your comments on this interpretations of RDA Rules

[RDA Blog post revised with Question & Answer on 2015-07-28]

<<<<<---------->>>>>

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

020 - International Standard Book Number (R)

RDA Blog posts on 020 - International Standard Book Number (R)

• Correct Coding of ISBN in MARC21 field 020 in RDA & AACR2 Cataloging with Examples
• International Standard Book Number (ISBN) - MARC to RDA Mapping
• Multiple ISBNs : LC-PCC Best Practices Guidelines

See also:

• Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 020 [LC]
• 020  International Standard Book Number (R) [OCLC]

RDA Purpose and Scope

RDA provides a set of guidelines and instructions on recording data to support resource discovery.

The data created using RDA to describe a resource are designed to assist users performing the following tasks:(1)

find—i.e., to find resources that correspond to the user’s stated search criteria

identify—i.e., to confirm that the resource described corresponds to the resource sought, or to distinguish between two or more resources with similar characteristics

select—i.e., to select a resource that is appropriate to the user’s needs

obtain—i.e., to acquire or access the resource described.

The data created using RDA to describe an entity associated with a resource (a person, family, corporate body, concept, etc.) are designed to assist users performing the following tasks:(2)

find—i.e., to find information on that entity and on resources associated with the entity

identify—i.e., to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar names, etc.

clarify—i.e., to clarify the relationship between two or more such entities, or to clarify the relationship between the entity described and a name by which that entity is known

understand—i.e., to understand why a particular name or title, or form of name or title, has been chosen as the preferred name or title for the entity.

RDA provides a comprehensive set of guidelines and instructions covering all types of content and media.

<<<<<<---------->>>>>>

LC-PCC PS for 0.0 (table of contents only--click above icon to go to complete text)

PURPOSE AND SCOPE

This Policy Statement, covering several areas of pre-cataloging decisions, represents LC practice/PCC practice except where a statement is noted only as LC practice.

Determining Mode of Issuance

Mode of Issuance: Integrating Resource?

Mode of Issuance: Monograph vs. Serial

Situations Requiring Further Consideration

Change in Cataloging Decision: Monograph/Serial

Determining Number of Records

Edition or Copy of Book

Supplementary Materials

Serial Supplements to Other Serials

Indexes to Serials

Serial Cumulations

Serials Issued in Parts

Reprinted Issues of Non-Newspaper Serials

Newspapers

Loose-Leaf Services

[Source: Based on instructions from RDA Toolkit]

New Sections Added to RDA Blog : Cataloger's Reference Directory / Testimonials

• Cataloger's Reference Directory : This section on the right-bottom of the blog lists useful links to web-resources for catalogers.

• Testimonials : Feedback received from users all over the world for Resource Description & Access (RDA) Blog, its companion Google+ Page Resource Description and Access, and Google+ Community RDA Cataloging.

• The About This Blog page is modified. Please view and post your comments / feedback / suggestions in the Guest Book. 

• Request to Cataloging Community : Please review this blog and publish in blogs/website/journals/books and kindly submit the description/url of your review  in the Guest Book.

Compilations of Independent Works : LC-PCC Best Practices Guidelines

Myth:

“In the case of compilations of independent works, I must always record an analytical authorized access point for the predominant or first work, according to LC-PCC PS 25.1.”

Reality:

Not necessarily.  Related Work is “LC core” for compilations, but there are exceptions.  Be sure you understand when to include a Contents Note (505) and Analytical Access Point (7XX X2).

<<<<<---------->>>>>

Whole-part relationships for Compilations

• LC: Give MARC 505 contents note unless contents indicated in another part of the of the description (e.g., in MARC 245 $a because no collective title present) or unless burdensome 

            •i.e., There is no limit on the number of works in the contents note unless burdensome. 

• LC: Give one MARC 7XX analytical authorized access point for the predominant or first work when it represents a substantial part of the resource; cataloger judgment if additional 7XX fields are given for other works. 

The policy for this LC core relationship generally is to give a MARC 505 contents and at least one 7XX analytical authorized access point. If the contents are already indicated elsewhere in the description (e.g., in the 245 field), a contents note is not necessary; if there are TOO MANY works in the compilation, you can omit the contents note. LC-PCC PS 25.1 indicates when an analytical authorized access point doesn’t need to be given for the first or substantial work in the compilation. 

• Don’t have to give analytical authorized access points or contents notes for some works: anthologies of poetry, conference proceedings, hymnals, journals, interviews, etc. – LC-PCC PS 25.1.

<<<<<---------->>>>>

Examples: LCCN: 2013318648]

[Source : Library of Congress]

Relationship Designators : LC-PCC Best Practices Guidelines

RDA RELATIONSHIP DESIGNATORS

Myth:

“I must include relationship designators with all access points.”

Reality:

Wrong.  You may include relationship designators in all access points.  But the only relationship designator that is required is “$e illustrator” for an illustrator of a resource intended for children.

Note: LC will soon implement the PCC requirement for relationship designators for all creators. 

[Source : Library of Congress]

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

Creators and Contributors : LC-PCC Best Practices Guidelines

Myth:

“Creators and contributors perform the same function, and the instructions regarding them are interchangeable and found in the same chapter of RDA”

Reality:

Absolutely not true!  Creators are involved at the work level, and are covered in Chapter 19; contributors are involved at the expression level, and are covered in Chapter 20.  Further, if you use a relationship designator, be sure to use one appropriate to the “WEMI” level.

[Source : Library of Congress]

RDA RELATIONSHIP DESIGNATORS

Preferred Title, Works, Selections: LC-PCC Best Practices Guidelines

Myth:

“If two different works have the same preferred title, there is a conflict that must be broken by adding the form, date, or place of origin of the work, or another distinguishing characteristic.”

Reality:

Not necessarily.  The authorized access point for the work is the combination of preferred title and creator (if any).  If the combination of these elements is not the same, there is no conflict. 

Myth:

“In determining whether there is a conflict, you should predict whether one is likely.”

Reality:

Wrong.  According to LC-PCC PS 6.27.1.9, you should only break actual existing conflicts.

Myth:

“In order to break a conflict in naming a work, the first preference is form of the work.  Then, if necessary, add date, place of origin, or other distinguishing characteristic -- in that order.”

Reality:

No, there is no ‘first preference’ for breaking conflicts.  Use whichever of those elements most effectively breaks the conflict, applied on a case-by-case basis.  There is no order of preference.

Myth:

“When adding the language to a Uniform Title for a part of a work or for “Selections,” the language is recorded before the part or “Selections.” (e.g., $a Poems. $l French. $k Selections.”

Reality:

No, this is a change from AACR2 practice.  “Selections” is a work element, while language is an expression element; do not ‘break-up’ these elements.  The proper subfield order is $a $k $l. 

[Source : Library of Congress]

Collaborations and Compilation: LC-PCC Best Practices Guidelines

Myth:

“When multiple entities are responsible for a resource, there is no difference between collaborations and compilations.  In both cases, the authorized access point (i.e., 1XX) is the first person, family, or corporate body named in the resource.”

Reality:

Wrong!  There is an important difference.  In the case of a compilation by different entities (i.e., you can tell who wrote what), the authorized access point is the preferred title of the compilation, which often is the title of the manifestation.  In the case of a collaboration, (i.e., you cannot tell who wrote what), the authorized access point is the entity with principal responsibility (or the first-named, if no one entity is principally responsible), regardless of the number of creators.  (There are exceptions to this, for moving image resources, some musical collaborations, treaties, and resources with both corporate bodies and persons as the responsible entities.)

[Source : Library of Congress]

According to RDA Rule 6.27.1.4 for Compilations of Works by different Persons, Families, or Corporate bodies: If the work is a compilation of works by different persons, families, or corporate bodies, construct the authorized access point representing the work by using the preferred title for the compilation.

[Source : RDA Toolikt]

Example: http://www.worldcat.org/oclc/930875923 [check in OCLC Connexion or import in local ILS].

Content Media Carrier Type : LC-PCC Best Practices Guidelines

Myth:

“If a resource includes multiple components (e.g., a volume and CD, with text, maps, and spoken word), you must describe all, using multiple 33X fields for Content, Media, and Carrier Type.”

Reality:

Not necessarily.  You must record the predominant term for each 33X field.  If you wish to record additional fields, you may.  Remember that each term is from a controlled vocabulary.

[Source : Library of Congress]

Illustrations : LC-PCC Best Practices Guidelines

Myth:

“Recording the presence of illustrations is a core element, and not a matter of judgment.”

Reality:

Not exactly.  You are required to record illustrations if the resource is intended for children.  And it is usually a good idea to record their presence, for other resources.  But you are permitted to exercise cataloger judgment, and may also ignore ‘minor’ illustrations (as you define ‘minor’).

[Source : Library of Congress]

Multiple ISBNs : LC-PCC Best Practices Guidelines

Myth:

“When I record multiple ISBNs, those for manifestations other than the manifestation I have in hand are coded ‘z’.”

Reality:

Incorrect.  LC-PCC PS 2.15.1.7 calls for this coding if the manifestation would be represented by a different record.  For example, LC does not routinely create separate records for paperback and hardback versions, so both 020 fields can be coded as “a” (the one for the manifestation in hand should be recorded first).

[Source : Library of Congress]

<<<<<<<------------------>>>>>>>

A different approach .... (Pre-RDA OCLC policy on multiple ISBN)


(Source: OCLC message of the day through OCLC Connexion, viewed on December 29, 2011)

Multiple ISBN on a single bibliographic record

Multiple ISBNs are acceptable on a single bibliographic record. Hardcopy items may have additional ISBNs for the paperback, online, and CD-ROM versions printed on the item, just to list a few possibilities. Library of Congress Rule Interpretations 1.8, 1.8B2, and related rules would have the cataloger record all ISBNs that appear on the resource, with the ISBN for the item being cataloged as the first 020, if that applies.  Any parenthetical identifier for any of the ISBNs should be included; the LCRI says:  "Prefer qualifiers found on the bibliographic resource itself when they are judged to convey a condition intelligibly. Use judgment to deal with unusual, complex situations or unusual phenomena." MARC 21 further stipulates that "Only the ISBN applicable to the entity represented by a particular record is considered valid on that record,"which means that all of the other ISBNs should be coded in field 020 subfields $z. OCLC #687665134 is one example of a record with more than one ISBN.

Series : LC-PCC Best Practices Guidelines

Myth:

“The Library of Congress has changed its series policy. Under RDA, all series are now traced.”

Reality:

Wrong!  LC continues to record all series in original cataloging as 490-0 (when performing Copy Cataloging, the 4XX and 8XX field are ‘pass-through’ elements; do not change a 440 to a 490-0).

[Source : Library of Congress]

<<<<<---------->>>>>

See Also: 

• Series at the Library of Congress: June 1, 2006
• Frequently Asked Questions about Series (LC-PCC)
• Statement on the Library of Congress Series Authority Record Decision (ALCTS, ALA)

[Updated 2014-12-21]

Publication Data in a 260 Field : LC-PCC Best Practices Guidelines

Myth:

“I can continue to record the publication data in a 260 field.”

Reality:

Incorrect.  The 260 has been replaced with the 264 field, for original cataloging using RDA.  Remember, also, to properly code the second indicator according to the function of the entity recorded in this field.

Myth:

“I am not required to transcribe the larger jurisdiction for the place of publication.”

Reality:

Wrong!  You are required to record this if it is present -- whether or not you think it is needed.

Myth:

“OK -- but I cannot add the larger jurisdiction if it is not present on the resource.”

Reality:

Again, wrong!  You are free to add -- in brackets -- the larger jurisdiction if you think it helpful.

Myth:

“Whenever you supply a place of publication, publisher, or date of publication in brackets, you must include a question mark.”

Reality:

No, the question mark simply means that you are relatively uncertain of your inference.  For example, if you are sure that the Museum of Modern Art is in New York, you don’t need a question mark; if you only ‘think’ it is the one in New York, you can add a question mark.

Myth:

“I can abridge the name of the publisher if it is lengthy.”

Reality:

Incorrect.  You must record the publisher’s name exactly and as fully as it appears (LC-PCC PS 2.8.1.4 uses the word ‘generally’, which means that -- in the case of corporate hierarchy -- rare exceptions are allowed).

Myth:

“I must always record every publisher, distributor, and manufacturer on the resource.”

Reality:

Wrong.  Only the first publisher statement is core.

Myth:

“If I decide to record two publishers, I should do so in separate 264 fields.”

Reality:

Incorrect.  The purpose of repeatable 264 fields is to record different functions (i.e., publisher, distributor, manufacturer, date of copyright), or to reflect changes over time (using the 264 first indicator).  If you wish to record a co-publisher, record both publishers and their places (if the places are different) in a single 264 field, as you did under AACR2.

Myth:

“I cannot record a copyright date if there is a ‘good’ publication date.”

Reality:

Incorrect!  Although you often use a copyright date to infer a publication data, you certainly may also record the copyright date in a separate 264 #4 field if you wish (with only a $c).  If you do so, remember to correctly code the 008 field (Type of Date “t”; Date 1; Date 2).

[Source : Library of Congress]