PFAN - Participant's Manual

About PFAN

News and Updates

Rules for Contributions

Name Authority Manual

Participant's Manual

PFAN Policy Statements

PFAN Training

Frequently Asked Questions (FAQ)

Other Documentation

LAC

375 – Gender (R)

$a – Gender (R)

$s – Start period (NR)

$t – End period (NR)

$u – Uniform Resource Identifier (R)

$v – Source of information (R)

$2 – Source of term (NR)

Gender is not a Core attribute for persons in RDA. Gender is a highly personal and sensitive attribute. Exercise restraint in adding gender terms to authority records, keeping in mind these PFAN best practices:

1. Optionally record information about gender as the person self-identifies and explicitly discloses.
2. Record masculin or féminin in accordance with the term used by the person, or with gendered pronouns and/or inflected nouns used in the source.
3. Do not assume gender identity based on pictures or names.
4. Do not dig for given names or genders assigned at birth.
5. For transgender/transsexual persons, record the terms Transgenres or Transsexuels in accordance with the term used by the person.
6. For well-known persons who publicly transition between males and female mid-life and have literary warrant for recording both genders, record both masculin and féminin and other terms as applicable.
7. Record gender terms based on information in the source. For example, if a person claims to be a cisgender male, record Cisgenres $2rvm and masculin. If a person just says “en tant que jeune garçon [as a young boy] …” or uses male pronouns then record masculin, but do not assume he is cisgender or transgender.
8. Record dates (375 $s and $t) associated with a gender only when the person explicitly provides dates of transition.
9. Justify gender data recorded in the 375 field in a subfield $v or 670 field or both.
10. Take into account the following considerations:
    • Is there potential for this information to harm the person through outing or violating the right to privacy?
    • Is there an indication that the person consents to having this information shared publicly?
    • Will including this information help a library user in the search process?

When recording a term indicating gender, prefer the terms: masculin and féminin. For these terms, do not capitalize or indicate the source of the term in the $2 subfield.

If neither of these terms is appropriate or sufficiently precise, record an appropriate term or phrase, preferably using a controlled vocabulary, such as the RVMGD or the Gender and sexual diversity glossary, recording the source in subfield 2. For consistency, capitalize the first term in each subfield $a for terms other than masculin and féminin.

Example:

100 1# $a Lenoir, Axelle, $d 1979-

375 ## $a Transgenres $2 rvmgd

375 ## $a féminin $s 2018

375 ## $a masculin $s 1979 $t 2018

Last Update : 2021-03-12

Return to Table of Contents ⮝ |  Manual ⮞ |  Supplement ⮞

Cross-references (4XX and 5XX) [New]

General overview

Add required cross-references to the authority record, including tags, subfields, delimiters, and diacritics. Search all cross-references to ensure they do not conflict with established authorized access points (1XX). A cross-reference (4XX) may conflict with a 4XX on another record. Keep in mind that normalization may result in conflicts between the authorized access point and 4XX forms of the name on the same NAR or other records. Such conflicts must be resolved.

Cross-references are formulated according to the same guidelines and instructions as authorized access points.

Apply the guidelines in RDA and the associated PFAN PSs when formulating cross-references.

Do not record a "see" reference (4XX) that would normalize to the same form as the 1XX in the same record or to the same form as the 1XX or 5XX in another name authority record. "See also" references (5XX) must be in the same form as their corresponding authorized access points.

Do not add references solely for automatic conflict detection and updating of bibliographic records. Inherent in the PFAN principles is the goal of making all cataloging workflows more efficient; since its inception the PFAN has recognized the need to have a file that is easily and efficiently used by all. This goal can only be achieved by an authority file that is uniform, i.e., predictable, in its construction and formulation of access points and references. Given the nature of the Program, it is impossible for the shared authority file to meet the database maintenance needs of each individual library. Catalogers are allowed to use judgment in making additional references and under RDA variants are not core, but the expectation is that those references would be constructed in the form consistent with the standard cataloging rules, practices, and policies currently used by all PFAN participants.

Last Update : 2022-03-22

Return to Table of Contents ⮝ |  Manual (4XX) ⮞ |  Manual (5XX) ⮞ |  Supplement (4XX) ⮞ |  Supplement (5XX) ⮞

Return to Table of Contents ⮝ |  Manual ⮞ |  Supplement ⮞

-->