Changes

Jump to navigation Jump to search
m
no edit summary
Line 21: Line 21:  
== May we add a date in a $d subfield, in an authorized access point, in an existing Canadiana record? ==
 
== May we add a date in a $d subfield, in an authorized access point, in an existing Canadiana record? ==
   −
Revising an existing authorized access point (AAP) creates additional work for bibliographic file maintenance (BFM); therefore, modifying an existing AAP simply to add a birth or death date, when they are absent, is really a last-resort option. Please note that adding a date is allowed in some circumstances ([[FAQ_%E2%80%93_Adding_dates_in_authority_records_for_personal_names#May_we_add_a_death_date_in_an_AAP.3F |see point 6, below]]).  
+
Revising an existing authorized access point (AAP) creates additional work for bibliographic file maintenance (BFM); therefore, modifying an existing AAP simply to add a birth or death date, when they are absent, is really a last-resort option. Please note that adding a date is allowed in some circumstances (see [[FAQ_%E2%80%93_Adding_dates_in_authority_records_for_personal_names#Are_there_any_situations_where_we_may_add_dates_to_an_existing_AAP_in_a_record_already_in_Canadiana.3F |point 6]] below).  
    
When an AAP being established conflicts with another AAP already established in Canadiana for another person, and a date is available for the person already established in Canadiana, but not for the new person, it is therefore preferable to make the new AAP unique by using another method allowed by RDA to distinguish AAPs, such as, (Profession/occupation), (Author of [Title of work]), etc., rather than modifying the existing AAP.  
 
When an AAP being established conflicts with another AAP already established in Canadiana for another person, and a date is available for the person already established in Canadiana, but not for the new person, it is therefore preferable to make the new AAP unique by using another method allowed by RDA to distinguish AAPs, such as, (Profession/occupation), (Author of [Title of work]), etc., rather than modifying the existing AAP.  
Line 27: Line 27:  
The LAC-BAnQ Policy Statement for RDA 9.19.1.1 states, however: “If there are no additions readily available to differentiate the access point in the new authority record, make an addition to the existing authorized access point”.
 
The LAC-BAnQ Policy Statement for RDA 9.19.1.1 states, however: “If there are no additions readily available to differentiate the access point in the new authority record, make an addition to the existing authorized access point”.
   −
When revising existing authority records, the date of birth, if known, must be recorded in field 046 $f, even if not included as part of the access point. (Cf. [[PFAN_-_Name_Authority_Manual#046_2nd_par | Name authority manual, field 046, 2nd paragraph]]).
+
When revising existing authority records, the date of birth, if known, must be recorded in field 046 $f, even if not included as part of the access point (see [[PFAN_-_Name_Authority_Manual#046_2nd_par | Name authority manual, field 046, 2nd paragraph]]).
    
== May we add a date to a new Authorized Access Point, being newly created, if there is no conflict? ==
 
== May we add a date to a new Authorized Access Point, being newly created, if there is no conflict? ==

Navigation menu

GCwiki