Difference between revisions of "FAQ – Adding dates in authority records for personal names"
Jump to navigation
Jump to search
m |
|||
| Line 16: | Line 16: | ||
* It is possible to differentiate living individuals by adding other elements, as indicated in RDA. | * It is possible to differentiate living individuals by adding other elements, as indicated in RDA. | ||
| − | == | + | == Do other participating institutions have to follow LAC's recommendations? == |
| − | + | Each institution is free to follow these or not, according to its own internal policies. For institutions choosing to follow LAC’s recommended practices, it is also possible to record the full birth date in a person’s authority record, if the cataloguer has received consent from the person. This practice is considered acceptable by LAC, even though it is not part of its initial recommendations. | |
| − | == | + | == 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 (see point 6, below). | |
| − | Lorsqu'un PAA en cours d'établissement est en conflit avec le PAA pour une autre personne déjà établi dans Canadiana et qu'une date est disponible pour la personne déjà représentée dans Canadiana mais pas pour la nouvelle, il est donc préférable de rendre le nouveau PAA unique en utilisant les autres possibilités qu’offre RDA pour distinguer un point d’accès d’un autre (par exemple, ([Profession/occupation]), (Auteur de [titre de l’ouvrage]), etc.) plutôt que de modifier le PAA déjà existant. | + | ''''Lorsqu'un PAA en cours d'établissement est en conflit avec le PAA pour une autre personne déjà établi dans Canadiana et qu'une date est disponible pour la personne déjà représentée dans Canadiana mais pas pour la nouvelle, il est donc préférable de rendre le nouveau PAA unique en utilisant les autres possibilités qu’offre RDA pour distinguer un point d’accès d’un autre (par exemple, ([Profession/occupation]), (Auteur de [titre de l’ouvrage]), etc.) plutôt que de modifier le PAA déjà existant.'''' |
| − | + | 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. 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? == |
| − | + | Yes. The date is a core element when an authority record is created. It must be added, if known, as it helps avoid future conflicts. | |
| − | == | + | == May we add a new subfield $d to an AAP being derived from the LC/NAF file (a new authority record added to Canadiana)? == |
| − | + | Yes. The form of the authorized access point, in Canadiana, does not need to be identical to the form of the authorized access point in the LC/NAF file, since they are two distinct authority files. It may even happen that an authorized access point created by LAC in LC/NAF be different from the access point created for the same entity in Canadiana. | |
| − | == | + | == May we add a death date in an AAP? == |
| − | + | LAC’s practice, as described in LAC-BAnQ’s PS 9.19.1.3, states that we do not add birth and/or death dates to existing Authorized Access Points (AACR2 or RDA) if they don’t include dates. | |
| − | == | + | == Are there any situations where we may add dates to an existing AAP in a record already in Canadiana? == |
| − | + | Adding a birth or death date is always allowed in the following situations: | |
| − | * | + | * When another change has to be made to the AAP (for instance, to fix a typo, update the person’s preferred name when the author changes names, or if another name is now more commonly used);qu’une autre modification doit être apportée au PAA (p. ex. pour corriger une coquille, mettre à jour le nom privilégié de la personne lorsque celle-ci change de nom ou qu’un autre nom est devenu prédominant); |
| − | * | + | * When a date is already present, to complete an open birth date with a death date, or the reverse; |
| − | * | + | * When no other addition is available to differentiate an access point in a new authority record. This is a last-resort solution, since it has an impact on BFM. |
| − | == | + | == May we add a date, in $d, to the variant names recorded in field 400, if this information is recorded in field 046 but is not part of the AAP? == |
| + | |||
| + | Generally speaking, if the AAP includes a date, the variant access points should also include a date. In the same way, if the AAP does not include a date, the variant access points should not include a date, except if a date is required, in the variant, to avoid a conflict between this variant and another AAP. | ||
| − | |||
<br> | <br> | ||
| − | '' | + | ''Last update: 2021-06-01''!<--(2021-05-28)--> |
--> | --> | ||
<br> | <br> | ||
[[category:PFAN]] | [[category:PFAN]] | ||
