• Core 2.4.2: CoreBut
  • if only one statement of responsibility is present on the SOI, then it is core
    
  • if more than one statement of responsibility is present on the SOI, then only the one that you choose to record first is core:
    
    • if you choose to record all statements, then enter them in the order specified (see Data entry order, below)
      
    • if you do not choose to record all statements, then only the first statement in the order specified below is core, but be sure to include any statements that identify creators (see 2.4.2.3 2nd paragraph)
• Scope 2.4.2.1
• Source 2.4.2.2: SSaTP; ASWR; [OSoI]
• Data entry 2.4.2.3: Form transcribed, but 1.7, order, and optional omissions
  
  • exceptions: 1.7 (Transcription)
    
  • order 2.4.1.6:
    
    • if multiple statements come from the first preferred source:
      
      • enter the most prominent statement(s)–as per layout or typography–first; but
        
      • if none seem more prominent, enter them in the sequence order provided on the source; but
        
      • if neither of these options seems a sensible order, enter the statements in the order that makes the most sense
        
    • if multiple statements come from a source that is not the first preferred source, enter them in the order that makes the most sense
      
  • optional omissions:
    
    • 2.4.1.4:
      
      • can omit additional wording in a statement
        
      • can omit additional names in a statement, see 2.4.1.5
        
    • 2.4.2: can omit non-core statements
• Function Ch. 2: Iden
• Entity: Manifestation

MARC-Bib: 245c (Statement of responsibility, etc.)

• 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 Form transcribed, but 1.7, order, and optional omissions: the data must match word-for-word and letter-for-letter (except for order, optional omissions, exceptions, error, or old cataloging rules)
      
    • if data is given in square brackets, it 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 the resource
  • 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 the Source for this element is or includes '[OSoI]': it is ok if the data is 'supplied' (i.e., in square brackets or as a note), but only if it seems applicable; but it is not ok if the data is not 'supplied' (except for error)
  • 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