• Core 19.2; I.2.1: CoreBut
  • if only one creator is responsible for the work being described, then that creator is core
    
  • if more than one creator is responsible for the work, then only one creator is core:
    
    • if principal responsibility for the work is indicated:
      
      • for only one of the creators, then that creator is core
        
      • for more than one of the creators, then the first named of those creators is core
        
    • if principal responsibility for the work is not indicated, then the creator named first is core
      
    • if you choose to record more than just the core creator, then enter the core creator first
• Scope 19.2.1.1
• Source 19.2.1.2: SAoPSoIiREW; OSAPiREW; IAiCoREW; OS
• Data entry 19.2.1.3: Recorded as a relationship
• Function Ch. 19: Rel
• Entity: Work

MARC-Bib: 1XX; 7XX (–No LC caption for 1XX)

• Check the 'Source' instruction to be sure that you are looking at the correct source(s) of information on the resource
• If data on the resource and data as the element in the record are:
  • PoR/PaE–check the Data Entry instructions:
    • data for this element must be Recorded as a relationship: make sure the relationship is appropriate for the resource and verify Authorized Access Points against the LC/NACO Authority File
  • PoR/AaE–check the Core instructions:
    • data for this element is CoreBut:
      
      • 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
  • AoR/PaE–check the Source instructions again:
    • since responsibility relationships can come from sources outside the resource itself, accept a responsibility relationship that is not found on the resource, as along as it seems possible; verify Authorized Access Points against the LC/NACO Authority File
  • AoR/AaE–go to the next element:
    • but be sure to check the resource carefully, if the data for the element is Core, or if the data is important for differentiating the resource from a similar resource
• Check below, for any useful Notes

General Notes:

• a family name can now be given as a Creator relationship
• a fictitious character can now be given as a Creator relationship
• see also Relationship Designators for Creators

Hybrid AACR:

MARC:

• because MARC tags are not explicit enough about the exact relationship of the creator to the work, you should always add relationship designators to make the relationship explicit; see also Relationship Designators for Creators
• you can delete any 7XX with $5–this indicates that the data in the field is appropriate only to the institution whose code is in the subfield

Matching

General element information