Authorized Access Point The 'controlled' or 'established' heading representing the RDA entity (Work, Expression, Person, Family, or Corporate body)

A person, family, or corporate body associated with one or more aspect of a bibliographic resource (a Work, Expression, Manifestation, or Item entity, aka a 'Group 1' entity). Also known as a 'Group 2' entity.

Data must be recorded for this element (if applicable and readily ascertainable: 0.6.1)

• For matching: if the data has not been given as another element instead:
  • it is not ok if the element is missing and the fact that the element is missing indicates a true difference (except for error or old cataloging rules)

• For editing:
  • if the data has been given as a wrong element, move it to the correct element
  • if the data is completely missing, add the data for this element

Data must be recorded for this element (if applicable and readily ascertainable), but if more than one statement is provided, only the first that the cataloger chooses to record is required (see the applicable instruction for how to choose which statement is recorded first)

• For matching: if the data has not been given as another element instead:
  • it is not ok if the core statement is missing (except for error or old cataloging rules); but
  • it is ok if a non-core statement is missing, unless evidence indicates that the fact that the element is missing indicates a true difference

• For editing:
  • if the data has been given as a wrong element, move it to the correct element
  • if the core statement for the element is completely missing, add it;
  • if a non-core statement is missing, consider adding it–remember the principles of differentiation and sufficiency

Data must only be recorded (if applicable and readily ascertainable) if other specified data is not identified or known, or under other specific circumstances (see the Core instruction for the element for details)

• For matching: if the data has not been given as another element instead:
  • it is ok if the element is missing, as long as the related element is present or if the specific circumstances allow it to be skipped; but
  • it is not ok:
    • if the element is missing and the related element is also missing or if the specific circumstance do not allow it to be skipped (except for error or old cataloging rules); or
    • if evidence indicates that the fact that the element is missing indicates a true difference

• For editing:
  • it is ok if the element is missing as long as the related element is present
  • but if the related, core element is also missing, and cannot be added, then add this element
  • also consider adding this element if it helps to explain 'supplied' data in the related, core element

Data is not core for RDA, but LC says it must be recorded if applicable and readily ascertainable (see the LC-PCC PS at the Core instruction for the element for details)

• For matching: if the data has not been given as another element instead:
  • it is ok if the element is missing, since the other cataloger might simply have decided not to add it; but
  • it is not ok if evidence indicates that the fact that the element is missing indicates a true difference

• For editing:
  • if the data has been given as a wrong element, move it to the correct element
  • if you are following LC policy, add the data for this element
  • if you are not following LC policy, add the data if you feel it might be useful–remember the principles of differentiation and sufficiency

Data is not core for RDA, but LC says it must be recorded (if applicable and readily ascertainable) in specified situations (see the LC-PCC PS at the Core instruction for the element for details)

• For matching: if the data has not been given as another element instead:
  • it is ok if the element is missing, since the other cataloger might simply have decided not to add it; but
  • it is not ok if evidence indicates that the fact that the element is missing indicates a true difference

• For editing:
  • if the data has been given as a wrong element, move it to the correct element
  • if you are following LC policy, and the situation outlined by LC is applicable to your resource, add the data for this element
  • if you are not following LC policy, add the data if you feel it might be useful–remember the principles of differentiation and sufficiency

Data is not core for RDA, but LC and PCC both say it must be recorded if applicable and readily ascertainable (see the LC-PCC PS, at the Core instruction for the element, for details)

• For matching: if the data has not been given as another element instead:
  • it is ok if the element is missing, since the other cataloger might simply have decided not to add it; but
  • it is not ok if evidence indicates that the fact that the element is missing indicates a true difference

• For editing:
  • if the data has been given as a wrong element, move it to the correct element
  • if you are following LC-PCC policy, add the data for this element
  • if you are not following LC-PCC policy, add the data if you feel it might be useful–remember the principles of differentiation and sufficiency

Data is not core for RDA, but LC and PCC both say it must be recorded (if applicable and readily ascertainable) if other specified data is not identified or known (see the LC-PCC PS at the Core instruction for the element for details)

• For matching: if the data has not been given as another element instead:
  • it is ok if the element is missing, since the other cataloger might simply have decided not to add it; but
  • it is not ok if evidence indicates that the fact that the element is missing indicates a true difference

• For editing:
  • if the data has been given as a wrong element, move it to the correct element
  • if you are following LC-PCC policy, and the situation outlined by LC is applicable to your resource, add the data for this element
  • if you are not following LC-PCC policy, add the data if you feel it might be useful–remember the principles of differentiation and sufficiency

Data does not have to be recorded, unless it is required to differentiate the resource or entity(0.6.1)

• For matching: if the data has not been given as another element instead:
  • it is ok if the element is missing, since the other cataloger might simply have decided not to add it; but
  • it is not ok if evidence indicates that the fact that the element is missing indicates a true difference

• For editing:
  • if the data has been given as a wrong element, move it to the correct element
  • if the data is missing completely, add the data if you feel it might be useful–remember the principles of differentiation and sufficiency

Data is recorded exactly as it would be provided as an established heading in a linked authority record for the Work or Expression, if such an authority record was available, as per the appropriate ‘Authorized Access Point’ instructions in RDA

• For matching: the data can be accepted as given, for matching

• For editing: make sure the data is constructed as the rules instruct

Data for the element must exactly mirror what is provided on the resource, except for transcription exceptions provided at 1.7, 1.8, and sometimes a special instruction for order (this is usually: “in the order indicated by the sequence, layout, or typography of the statements on the source of information”); see the instructions for details.

• For matching: the data must match word-for-word, letter-for-letter (except for order, exceptions, error, or old cataloging rules); data for an element that is given in square brackets is ‘supplied’ data, and comes from outside the resource itself

• For editing: make sure the data matches letter-for-letter (except for order, exceptions), e.g.: fix capitalization; add punctuation; replace separating punctuation; do not use [sic] or [i.e. …], explain inaccuracies in a note; decide whether to add omitted data

See above: Form transcribed, but …; see rule for order

See above: Form transcribed, but …; see rule for order

Data for the element must exactly mirror what is provided on the resource, except for transcription exceptions provided at 1.7, 1.8, and sometimes a special instruction for order and optional omissions; see the instructions for details.

• For matching: the data must match word-for-word, letter-for-letter (except for order, optional omissions, exceptions, error, or old cataloging rules); data for an element that is given in square brackets is ‘supplied’ data, and comes from outside the resource itself

• For editing: make sure the data matches letter-for-letter (except for order, optional omissions, exceptions), e.g.: fix capitalization; add punctuation; replace separating punctuation; do not use [sic] or [i.e. …], explain inaccuracies in a note; decide whether to add omitted data

See above: Form transcribed, but …; see rule for order and optional omissions

See above: Form transcribed, but …; see rule for order and optional omissions

Relationship data is recorded either as found in the established heading provided in a linked authority record, or as constructed by you as an established heading, as per the appropriate ‘Authorized Access Point’ instructions in RDA

• For matching: the data can be accepted as given, for matching

• For editing: verify Authorized Access Points against the LC/NACO Authority File

Data in a content relationship element for a related Work, Expression, or Manifestation is recorded either as a structured or an unstructured description instead of as an Authorized Access Point, or as a link to another record

• For matching: the contents must be appropriate for the resource

• For editing: make sure that the description of the contents is appropriate for the resource

Data in the element is recorded in your own words, avoiding the use of abbreviations, except for commonly accepted terms (e.g., ‘etc.’, ‘hr.’, ‘min.’—see RDA Appendix B)

• For matching: the intent of the data must be appropriate for the resource

• For editing: make sure the intent of the data is appropriate for the resource

Data in the relationship element is recorded either as found in the established heading provided in a linked authority record, or as constructed by you as an established heading, as per the appropriate ‘Authorized Access Point’ instructions in RDA

• For matching:
  • responsibility and/or content relationship data only needs to be checked for matching if a relationship is not already provided elsewhere in the record (e.g., in a statement of responsibility or in a structured description for contents); if you must check responsibility and/or content relationship:
    • responsibility relationship data must be appropriate for the resource, even though the form of the Authorized Access Point might be different from the name given elsewhere
    • content relationship data must be appropriate for the resource, even though the form of the Authorized Access Point might be different from the titles given elsewhere
  • other relationship data (e.g., derivative works) can be accepted as given, for matching

• For editing:
  • make sure the relationship is appropriate for the resource
  • verify Authorized Access Points against the LC/NACO Authority File

See below

Data in the element is not transcribed exactly from the resource, but is entered specifically as instructed for the element

• For matching: the data must be appropriate for the resource, even if it is not entered exactly as instructed due to interpretation or error

• For editing: make sure the data is recorded as instructed

Only terms from the specified list for the element can be used in the element

• For matching: the term must be appropriate for the resource, even if it is not a term from the official list of terms

• For editing: make sure the term:
  • is appropriate for the resource
  • is given exactly from the official list of terms for the element, except for capitalization (check for typos)

Appropriate terms from the specified list for the element should be used in the element, but if none of the terms in the list is “appropriate or sufficiently specific”, other concise terms can be used

• For matching: the term must be appropriate for the resource, even if it is not a term from the official list of terms

• For editing: make sure the term:
  • is appropriate for the resource
  • is either given exactly from the official list of terms for the element, except for capitalization (check for typos);
  • or conforms to the structure and reasoning of the official list (e.g., singular vs, plural), if it is a locally added term

Data for the element must exactly mirror what is provided on the resource.

• For matching: the data must match word-for-word, letter-for-letter (except for error or old cataloging rules); data for an element that is given in square brackets is ‘supplied’ data, and comes from outside the resource itself, and so can be accepted as given, for matching, as long as it seems reasonable

• For editing: make sure the data matches word-for-word, letter-for-letter, e.g.: fix capitalization; add punctuation; replace separating punctuation; do not use [sic] or [i.e. …], explain inaccuracies in a note

Data for the element must exactly mirror what is provided on the resource, except for transcription exceptions provided at 1.7, 1.8, and sometimes a special rule.

• For matching: the data must match word-for-word, letter-for-letter (except for exceptions, error or old cataloging rules); data for an element that is given in square brackets is ‘supplied’ data, and comes from outside the resource itself, and so can be accepted as given, for matching, as long as it seems reasonable

• For editing: make sure the data matches word-for-word, letter-for-letter (except exceptions), e.g.: fix capitalization; add punctuation; replace separating punctuation; do not use [sic] or [i.e. …], explain inaccuracies in a note

See above: Transcribed, but …

See above: Transcribed, but …

See above: Transcribed, but …

See above: Transcribed, but …

A 'thing' associated with a bibliographic resource. Group 1 (WEMI) entities are: Work, Expression, Manifestation, or Item. Group 2 (Agent) entities are: Person, Family, or Corporate body.

Carrier elements are the data elements that RDA says are most often used to select a particular resource. They help a catalog user to choose between resources that seem similar, but have different carrier characteristics, e.g., is the font large print or regular print, is the text printed or digital (an eBook), is the story on board pages or cloth pages

Content elements are the data elements that RDA says are most often used to select a particular resource. They help a catalog user to choose between resources that seem similar, but have different characteristics, based on the actual contents of the resource; e.g., are there illustrations, is the introduction that I need included

Identifying elements are the data elements that RDA says are “most often used to identify a resource”. They help a catalog user to decide whether a record that a particular search has found, is actually for the resource that the user wanted to find, e.g., e.g., is this the needed edition, are the contents textual or audio, are they in English or another language or both

Relationship elements are the data elements that RDA says are used to find all resources that are:

• associated with a particular person, family or corporate body; or
• related to other resources that might be of interest to the user

If data is present on, or appropriate to, the resource and is also present as an element in the record, then check the Data Entry instructions for the element

If data is present on, or appropriate to, the resource but is absent as an element in the record, then check the Core instructions for the element

If data is absent from, or not appropriate to, the resource, or you do not have the resource in hand to check this information, but that data is present as an element in the record, then check the Source of information instructions for the element

If data is absent from, or not appropriate to, the resource and is absent as an element in the record, then go to the next element, but be sure to look carefully for the data if the element is Core

First indicator of a MARC field, aka: Indicator 1

Second indicator of a MARC field, aka: Indicator 2

Person, Family, or Corporate body

Relationship Designator, designates the relationships between:

• a resource and a person, family , or corporate body, e.g., “author”, “editor”, “translator”
• a resource and the works contained in it, e.g., “Contains (work)” or “Contains (expression)”
• a resource and another resource related to it, e.g., “Based on (work)”

Source of Information

Always look for data on a resource from the assigned source(s) of information for the element, and in the preferred order for those sources, e.g., SSaTP / ASWR / OSoI means: begin looking for data on the same source as the title proper, then try another source within the resource itself, then accept supplied data from the specified 'other sources of information'

• For matching:
  • If Source is or includes:
    • 'Any': since Source is or includes 'Any', accept the data, but only if it seems applicable
    • '[OSoI]': since Source is or includes [OSoI], it is ok if the data is 'supplied' (e.g., in square brackets), but only if it seems applicable; but it is not ok if the data is not 'supplied' (except for error)
  • If Source does not include 'Any' or '[OSoI]':
    • and the Function of the data is to provide a Relationship (Rel): since responsibility relationships can come from sources outside the resource itself, accept responsibility relationships not found on the resource, as along as it seems possible
    • and the Function of the data is not to provide a Relationship (Rel): since this type of data is supposed to come from the resource somewhere, it is not ok if the data cannot be found anywhere on the resource, but check the entire resource (just in case)

• For editing:
  • If Source is or includes:
    • 'Any': since Source is or includes 'Any', accept the data, but only if it seems applicable
    • '[OSoI]': since Source is or includes '[OSoI]', it is ok if the data is 'supplied' (e.g., in square brackets), but only if it seems applicable; indicate that the data is 'supplied', if that has not been done
  • If Source does not include 'Any' or '[OSoI]':
    • and the Function of the data is to provide a Relationship (Rel): since responsibility relationships can come from sources outside the resource itself, accept responsibility relationships not found on the resource, as along as it seems possible; verify Authorized Access Points against the LC/NACO Authority File
    • and the Function of the data is not to provide a Relationship (Rel): since this type of data is supposed to come from the resource somewhere, it is not ok if the data cannot be found anywhere on the resource, but check the entire resource (just in case)–if you find the data on a source that is not allowed for the element, then consider making it an appropriate note

Any sources

Any Source Within the Resource itself

Another Source Within the First Issue

Another Source Within the Last Issue

Another Source Within the Resource itself

Evidence Presented By the Resource Itself + accompanying material or container + any source

Gazatteers and other reference sources + (see rule)

Information appearing only in the content of the resource itself

Information appearing only in the content of the resources emboyding the expression

Information appearing only in the content of the resources embodying the work

The ISSN register

Other formal statements appearing in resources associated with the corporate body

Other formal statements appearing in resources associated with the family

Other formal statements appearing in resources associated with the person

Other sources

Other statements appearing prominently in the resource itself

Other statements appearing prominently in the resources embodying the expression

Other statements appearing prominently in the resources embodying the work

Other Source of Information (2.2.4)

Other Source of Information–supplied data: must either be entered in square brackets or (if the instructions for an element specifically so instruct) explained in a note (2.2.4 & the LC PCC PS for it)

Preferred Source of Information (2.2.2)

• for resources consisting of pages, etc.: a title page, etc., see 2.2.2.2
  • Hint: do not consider a dust jacket part of the resource itself
• for moving images: a title frame or title screen, see 2.2.2.3
• for all other resources, see 2.2.2.4

For substitutes when a PSoI is lacking:

• for resources consisting of pages, etc., without a title page, etc., see 2.2.2.2
• for moving images, without a title frame or title screen, see 2.2.2.3
• for all other resources, see 2.2.2.4

Preferred Source of Information from Earlier Iteration

Preferred sources of information in resources associated with the corporate body

Preferred sources of information in resources associated with the family

Preferred sources of information in resources associated with the person

Preferred Source of Information from Later Issues or parts

Resources embodying the work

Reference sources

Statements appearing on the preferred sources of information in the resource itself

Statements appearing on the preferred sources of information in resources embodying the expression

Statements appearing on the preferred sources of information in resources embodying the work

Same Source as Corresponding Parallel Designation of Edition

Same Source as the Corresponding Parallel Designation of a Named Revision of an Edition

Same Source As the Corresponding Title Proper

Same Source As the Corresponding Title Proper of the Series

Same Source As the Corresponding Title Proper of the SubSeries

Same Source As the Distributor's Name

Same Source As Designation of Edition

Same Source as the Designation of a Named Revision of an Edition

Same Source As the Manufacturer's Name

Same Source As the Place of Distribution

Same Source As the Place of Manufacture

Same Source As the Place of Production

Same Source As the Place of Publication

Same Source As the Producer's Name

Same Source As the Publisher's Name

Same Source As the Title Proper

If the Title Proper is from OSoI, then Parallel Title Proper must be from the same source

Same Source As the Title Proper on First Issue

Same Source As the Title Proper on Last Issue

Same Source As the Title Proper of the Series

Same Source As the Title Proper of the SubSeries

Series Title Page

1.7.1:

• Capitalization
• Punctuation
• Diacritical Marks
• Symbols
• Spacing of Initials and Acronyms
• Letters or Words Intended to Be Read More Than Once
• Abbreviations
• Inaccuracies

The four levels or aspects of a bibliographic resource identified by FRBR: Work, Expression, Manifestation, Item