111 - Main Entry-Meeting Name (NR) - MARC 21

111 - Main Entry-Meeting Name (NR)

---

First Indicator	Second Indicator
Type of meeting name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order	Undefined # - Undefined

---

Subfield Codes
$a - Meeting name or jurisdiction name as entry element (NR) $c - Location of meeting (R) $d - Date of meeting (NR) $e - Subordinate unit (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $j - Relator term (R) $k - Form subheading (R) $l - Language of a work (NR)	$n - Number of part/section/meeting (R) $p - Name of part/section of a work (R) $q - Name of meeting following jurisdiction name entry element (NR) $t - Title of a work (NR) $u - Affiliation (NR) $0 - Authority record control number or standard number (R) $4 - Relator code (R) $6 - Linkage (NR) $8 - Field link and sequence number (R)

---

FIELD DEFINITION AND SCOPE

Meeting or conference name used as a main entry in a bibliographic record.

According to various cataloging rules, main entry under a meeting name is assigned to works that contain proceedings, reports, etc.

Meetings entered subordinately to a corporate body that are used as main entries are recorded in field 110.

---

GUIDELINES FOR APPLYING CONTENT DESIGNATORS

Descriptions of the first indicator position and all subfield codes, as well as input conventions for the 111 field, are given in the X11 Meeting Names-General Information section. Because the second indicator is different for various X11 fields, it is not described in the general information section, but is described below.

■ INDICATORS

Second Indicator - Undefined

Undefined and contains a blank (#).

See also:

• Library of Congress >> MARC >> Bibliographic >> 1XX >> 111 [LC]
• 111  Main Entry–Meeting Name (NR) [OCLC]

RDA: What it is --

A Content Standard

RDA provides instructions on recording the content of records.

• It does not provide instruction on how a given library system (e.g.) should display the bibliographic information (although there is information about displaying RDA content).
• Nor does it provide instruction on encoding the information. RDA is schema-neutral. You can use it with any schema, including MARC, or Dublin Core.

More International

RDA is less Anglo-centric than AACR2.  It focuses on user needs, as stressed in the International Cataloguing Principles.

In addition, the agency preparing the description can make choices regarding the:

• language of additions to access points
• language of supplied data
• script and transliteration
• calendar
• numeric system

Wider Scope of Resources

RDA also covers the wider scope of resources being acquired in libraries today. It provides for more elements for:

• non-printed text resources
• non-text resources
• unpublished resources

But RDA defers appropriately to the specialist manuals of collaborative communities in situations where more detailed description is wanted than the general view provided by RDA (e.g., music, sound recordings, moving images, electronic resources, cartographic materials).

Authority Data

RDA includes instructions on authority data, based on attributes and relationships in the FRAD model. There were no AACR2 rules for authority data and authority records. RDA doesn’t indicate how authority data should be encoded; but for now, that information will continue to be documented by most libraries in authority records.

Controlled Vocabularies

RDA has many controlled vocabularies. Only a few of the vocabularies are closed (e.g., content type; media type; carrier type; mode of issuance). Most of the vocabularies are open; you can either supply your own term as needed, or suggest a term be added to the vocabulary (or do both).

Libraries may decide to include some of these controlled vocabulary terms in templates; ILS vendors could provide them in drop-down lists.  And so on. 

The RDA vocabularies are now registered on the Web. The existence of those machine-readable controlled vocabularies will allow more machine manipulation of data than is now possible, including the mapping of RDA to other metadata schemes.

[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):

RDA BLOG REACHES 100000 PAGEVIEWS

              RDA BLOG HIGHLIGHTS IN 1-MINUTE VIDEO PRESENTATION              

Thanks all for your love, support and suggestions. Please post your feedback and comments on RDA Blog Guest Book. Select remarks will be posted on RDA Blog Testimonials page.

CLICK HERE TO VIEW THIS VIDEO PRESENTATION IN FULL VIEW MODE

CLICK HERE FOR YOUTUBE VERSION OF THIS VIDEO - TO VIEW ON A MOBILE PHONE/TABLET

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

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):

RDAExpress : a service to convert any library catalog to RDA

A clean database is the key to providing library users the best possible searching experience and catalogers have dedicated years of service in cultivating and maintaining their databases to this end. The new RDA standard has great benefits, providing enriched content and priming libraries for a Linked Data environment, but it also has an impact on workflow, budgets and patron experience. RDA holds the promise for libraries to restructure its data to provide a better searching experience for users and ultimately link outside the library to be more competitive in today’s digital world.  Most integrated library systems are compliant with RDA, in that they can handle a mixed database of AACR2 and RDA records, but is that really helpful to your users? A mixed database results in a mixed display, with your newer records providing more specific information than your legacy records, disrupting search and discovery.

RDAExpress (https://www.rdaexpress.com) promises to help address this disruption and take the headache out of retrospective conversion of your database to RDA - an undertaking that is nearly impossible for catalogers to do while still keeping up with new titles. It is an RDA Conversion service to upgrade your existing records without worrying what kind of ILS you currently have. 

"Our service is going to unleash greater discoverability in library catalogs" says Heather Powers, eBiblioFile Product Owner. “Library records will have more and better relationships and descriptions. The catalog will be ready for FRBR. And the best part is that RDAExpress does all the work to make this possible now.”

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):

Additional information on use of $b in fields 336-338

Library of Congress has begun supplying $b codes for the equivalent terms in $a of fields 336 (Content type), 337 (Media type), and 338 (Carrier type). This is the most efficient manner to start populating a subfield that LC initially chose not to apply. This will allow LC records to conform more to records produced outside of LC (e.g., OCLC generally adds the codes in $b in new records). It will be supplied automatically if cataloger are using the macro or the RDA templates in Voyager—staff are not expected to manually add $b to fields in existing records that lack the subfield.

[Source : Library of Congress]

Appendix I : New Relationship Designators

There are three new relationship designators Appendix I: 

organizer [I.2.2]

cartographer (expression) [I.3.1]

minute taker [I.3.1]

[Source : RDA Toolkit]

Comments by Aaron Kuperman, Law Librarian, Library of Congress : This list is flexible. It is expected that new terms will be constantly added. Consider it as being similar to how LCSH grows, rather than the former system under LCRI under changes were few and far between.

Editor of Compilation vs Compiler

RDA RELATIONSHIP DESIGNATORS

RDA Relationship Designators : Editor of Compilation vs Compiler 

The editor of a compilation, as defined in I.3.1, is not a creator of a work and thus has to be treated as a 700, not a 100.

On the other hand, a compiler (for example of a dictionary, a directory, a bibliography, etc.) can be considered a creator (see I.2.1) and thus can be treated as a 100.

Expert remarks by Aaron Kuperman, Law Librarian, Library of Congress : A good rule of thumb is that a compilation needs to consist of works that can (and should) be listed in the contents note.

According to RDA Toolkit: I.2.1 Relationship Designators for Creators: 

Compiler : A person, family, or corporate body responsible for creating a new work (e.g., a bibliography, a directory) by selecting, arranging, aggregating, and editing data, information, etc. For a compiler as a contributor, see editor at I.3.1.

According to RDA Toolkit: I.3.1 Relationship Designators for Contributors: 

Editor : A person, family, or corporate body contributing to an expression of a work by revising or clarifying the content, or by selecting and putting together works, or parts of works, by one or more creators. Contributions may include adding an introduction, notes, or other critical matter, or preparing the expression of a work for production, publication, or distribution. For major revisions, adaptations, etc., that substantially change the nature and content of the original work, resulting in a new work, see author at I.2.1.

Note:

I.2 - Relationship Designators for Persons, Families, and Corporate Bodies Associated with a Work

I.3 - Relationship Designators for Persons, Families, and Corporate Bodies Associated with an Expression

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

According to RDA Toolkit Release (April 22, 2014):

	Relationship Designators for Contributors
I.3.1	The relationship designator for “editor of compilation” has been deleted, and the concept incorporated into a revised relationship designator for “editor.”

[Blog post revised on June 5, 2015]

Conventional Collective title / Uniform title : Questions and Answers

Question : Is it allowed to give 240 conventional collective title / uniform title in following example:

010	__ |a 2012352243
020	__ |a 9788179171615 (hb)
020	__ |z 9788179171623 (pb)
025	__ |a I-H-2012-352243; 21-92
037	__ |b Library of Congress -- New Delhi Overseas Office
040	__ |a DLC |b eng |c DLC |e rda |d DLC
041	1_ |a hin |h hin |h nep
042	__ |a lcode |a pcc
043	__ |a a-np---
050	00 |a DS495.6 |b .P67 2011
100	0_ |a Pracaṇḍa, |d 1944- |e interviewee.
240	10 |a Interviews. |k Selections
245	10 |a Evaresṭa para Lāla jhaṇḍā : |b Nepāla ke Māovādī netā Pracaṇḍa se bātacīta / |c sampādaka Ānanda Svarūpa Varmā.
264	_1 |a Dillī : |b Grantha Śilpī (Iṇḍiyā) Prāiveṭa Limiṭeḍa, |c 2011.
300	__ |a 357 pages ; |c 22 cm
336	__ |a text |2 rdacontent
337	__ |a unmediated |2 rdamedia
338	__ |a volume |2 rdacarrier
520	__ |a Collection of interviews with Pracanda, born 1944, Nepali politician and chairman of the Nepāla Kamyunishṭa Pārṭī (Māovādī) on the current political scene, Maoist movement, civil war, and insurgency in Nepal.
546	__ |a In Hindi; includes articles translated from English and Nepali.
600	00 |a Pracaṇḍa, |d 1944- |v Interviews.
650	_0 |a Politicians |z Nepal |v Interviews.
610	20 |a Nepāla Kamyunishṭa Pārṭī (Māovādī) |v Interviews.
651	_0 |a Nepal |x Politics and government |y 1990-
651	_0 |a Nepal |x History |y Civil War, 1996-2006.
650	_0 |a Insurgency |z Nepal

Answer : The relevant RDA rule for this case is 6.2.2.10.2 - Complete Works in a Single Form which prescribes to Record one of the conventional collective titles as the preferred title for a compilation of works that consists of, or purports to be, the complete works of a person, family, or corporate body, in one particular form such as: Correspondence, Novels, Speeches, Lyrics, etc ...

Comment : Remember that 6.2.2.10.2 is not a closed list so you can choose whatever term is appropriate if it’s not already listed there. As this a compilation of Pracanda’s interviews, the 240 is correct. Under RDA, the decision to create a conventional collective title (formerly “uniform title”) based on whether the title proper is adequate or not (as we used to under AACR2, .cf LCRI 25.10) no longer applies.

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

RDA RELATIONSHIP DESIGNATORS

I.2 - Relationship Designators for Persons, Families, and Corporate Bodies Associated with a Work

According to RDA Appendix: I.2.1 Relationship Designators for Creators

interviewee : A person, family, or corporate body responsible for creating a work by responding to an interviewer, usually a reporter, pollster, or some other information gathering agent.

interviewer A person, family, or corporate body responsible for creating a work by acting as an interviewer, reporter, pollster, or some other information gathering agent.

[Revised May, 6 2015]

[Source: LC online catalog and RDA Toolkit]

Corporate Body Relationship Designator : Questions & Answers

Question: What would be the relationship designator for organizer of a conference.

Answer: organizer : A person, family, or corporate body organizing the exhibit, event, conference, etc., which gave rise to a work.

Please note that is a new addition in Appendix A I.2.2 - Relationship Designators for Other Persons, Families, or Corporate Bodies Associated with a Work

[Source: RDA Toolkit]

RDA RELATIONSHIP DESIGNATORS

Books on RDA Cataloging from Facet Publishing

Books on RDA Cataloging from Facet Publishing

RDA Terminology

Listed below are some of the main differences in terminology between AACR2 and RDA. Some of the changes reflect our turning away from the catalog card environment, while others reflect terminology in the FRBR/FRAD models and the International Cataloguing Principles.

AACR2	RDA	Notes
heading	authorized access point	“heading” reflects outmoded ‘catalog-card-speak’
author, composer, artist, etc.	creator
main entry	preferred title and, if appropriate, the authorized access point for the creator	“main entry” reflects outmoded ‘catalog-card-speak’, related to cards in a file cabinet
uniform title	Two RDA counterparts: 1.      the preferred title and any differentiating information; 2.      a conventional collective title such as “Works”
see reference	variant access point
see also reference	authorized access point for related entity
physical description	carrier description
general material designator	three elements: 1.      content type 2.      media type 3.      carrier type	GMD was an inconsistent presentation of different categories of information
chief source	preferred sources	This is not only a change in terminology; ‘sources’ have been expanded from a single source to multiple sources

[Source: Library of Congress]

Authorized Access Point - Corporate Name - MARC to RDA Mapping

MARC 21 FIELD TAG	MARC 21 SUBFIELD CODE	MARC 21 FIELD / SUBFIELD NAME	RDA INSTRUCTION NUMBER	RDA ELEMENT NAME
110		Main entry—Corporate name	19.2	Creator
110		Main entry—Corporate name	19.3	Other Person, Family, or Corporate Body Associated with a Work
110	a	Corporate name or jurisdiction name as entry element	6.22	Signatory to a Treaty, etc.
110	a	Corporate name or jurisdiction name as entry element	11.2.2	Preferred Name for the Corporate Body
110	a	Corporate name or jurisdiction name as entry element	11.2.3	Location of Headquarters, etc.
110	a	Corporate name or jurisdiction name as entry element	11.4.3	Date of Establishment
110	a	Corporate name or jurisdiction name as entry element	11.4.4	Date of Termination
110	a	Corporate name or jurisdiction name as entry element	11.5	Associated Institution
110	a	Corporate name or jurisdiction name as entry element	11.7	Other Designation Associated with the Corporate Body
110	b	Subordinate unit	11.2.2	Preferred Name for the Corporate Body
110	c	Location of meeting	11.3.2	Location of Conference, etc.
110	c	Location of meeting	11.5	Associated Institution
110	d	Date of meeting or treaty signing	11.4.2	Date of Conference, etc.
110	d	Date of meeting or treaty signing	6.4	Date of Work
110	e	Relator term	18.5	Relationship Designator
110	f	Date of a work	6.10	Date of Expression
110	g	Miscellaneous information	11.7	Other Designation Associated with the Corporate Body
110	k	Form subheading	6.2.2	Preferred Title for the Work
110	l	Language of a work	6.11	Language of Expression
110	n	Number of part/section/meeting	6.2.2	Preferred Title for the Work
110	n	Number of part/section/meeting	6.3	Form of Work
110	n	Number of part/section/meeting	6.4	Date of Work
110	n	Number of part/section/meeting	6.5	Place of Origin of the Work
110	n	Number of part/section/meeting	6.6	Other Distinguishing Characteristic of the Work
110	n	Number of part/section/meeting	11.6	Number of a Conference, etc.
110	p	Name of part/section of a work	6.2.2	Preferred Title for the Work
110	p	Name of part/section of a work	6.3	Form of Work
110	p	Name of part/section of a work	6.4	Date of Work
110	p	Name of part/section of a work	6.5	Place of Origin of the Work
110	p	Name of part/section of a work	6.6	Other Distinguishing Characteristic of the Work
110	t	Title of a work	6.2.2	Preferred Title for the Work
110	t	Title of a work	6.3	Form of Work
110	t	Title of a work	6.4	Date of Work
110	t	Title of a work	6.5	Place of Origin of the Work
110	t	Title of a work	6.6	Other Distinguishing Characteristic of the Work
110	u	Affiliation	11.9	Address of the Corporate Body

[Source: RDA Toolkit]

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):