• 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: 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 responsibility and/or content relationship is checked:
      
    • 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
  • PoR/AaE–check the Core instructions:
    • data for this element is CoreBut: 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 other evidence indicates that the fact that the element is missing indicates a true difference
  • 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 long as it seems possible
  • 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

Editing

General element information