Difference between revisions of "PFAN - Other Documentation"
Line 253: | Line 253: | ||
Example:<blockquote style="font-family:courier new;">151 Viernyï (Kazakhstan)</blockquote><blockquote style="font-family:courier new;">665 Fondée en 1854, cette ville a porté le nom de Viernyï jusqu'en 1921. Elle s'appelle maintenant Alma-Ata. Comme auteur, on utilise : Alma-Ata (Kazakhstan) ; Viernyï (Kazakhstan). Comme vedette-matière, on utilise : Alma-Ata (Kazakhstan).</blockquote> | Example:<blockquote style="font-family:courier new;">151 Viernyï (Kazakhstan)</blockquote><blockquote style="font-family:courier new;">665 Fondée en 1854, cette ville a porté le nom de Viernyï jusqu'en 1921. Elle s'appelle maintenant Alma-Ata. Comme auteur, on utilise : Alma-Ata (Kazakhstan) ; Viernyï (Kazakhstan). Comme vedette-matière, on utilise : Alma-Ata (Kazakhstan).</blockquote> | ||
− | In this example, only the first two phrases can be transferred to a 678 field. The two other phrases are not retained. As the access point is not valid as a subject heading, it is necessary to | + | In this example, only the first two phrases can be transferred to a 678 field. The two other phrases are not retained. As the access point is not valid as a subject heading, it is necessary to consider adding the following note in field 667: |
<blockquote style="font-family:courier new;">667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur ce lieu se trouvent sous Alma-Ata (Kazakhstan).</blockquote> | <blockquote style="font-family:courier new;">667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur ce lieu se trouvent sous Alma-Ata (Kazakhstan).</blockquote> | ||
|- style="vertical-align: top;" | |- style="vertical-align: top;" | ||
|667 | |667 | ||
− | |Ensure that the | + | |Ensure that the contents of this field is general enough to be pertinent to cataloguers in other institutions. If not, delete the field. |
Examples of 667 fields to delete: | Examples of 667 fields to delete: | ||
Line 281: | Line 281: | ||
|- style="vertical-align: top;" | |- style="vertical-align: top;" | ||
|678 | |678 | ||
− | | | + | |Ensure that the contents of the field truly consist of biographical or historical information and is appropriate for public display. The text must be worded in the form of concise and complete phrases. |
− | + | The content of all 665 fields in LAC and BAnQ records has been placed in field 678. It is possible that the original field 665 contained instructions about the access point to use as an author or as a subject heading (see the example under field 665 above). Delete these instructions in field 678 if they have been retained. Consider adding a 667 note on the use of the access point as a subject heading, if applicable. | |
'''<big>Justification de la zone 678</big>''' | '''<big>Justification de la zone 678</big>''' |
Revision as of 16:31, 22 December 2020
This article is actively undergoing a major edit for 24 h (Currently being edited by A. Dunnett, LAC). To help avoid edit conflicts, please do not edit this page while this message is displayed. This page was last revised at 16:31, 22 December 2020 (UTC) (3 years ago). Please remove this template if this page hasn't been edited in several hours. If you are the editor who added this template, please be sure to remove it or replace it with {{Under construction}} between editing sessions. |
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 |
LC Subject Cataloging Manual, H 405 - Establishing Certain Entities in the Name or Subject Authority File
LC SHM Instruction Sheet H 0405 - Establishing Certain Entities in the Name or Subject Authority File (PDF, 76 KB)
Last update: August 2020
PCC Post RDA Test Guidelines
Last update: October 2, 2020
PCC Guidelines for the Application of Relationship Designators in NACO Authority Records
Authority File Comparison Rules (NACO normalization)
Authority File Comparison Rules (NACO Normalization) (PDF, 72 KB)
Approved November 2007, with further revision April 1, 2009
Return to Table of Contents ⮝
Romanization
Language | Writing System | Romanization Table |
---|---|---|
Arabic | Arabic alphabet | ISO 233-2:1993 Information and Documentation -- Arabic characters into Latin characters -- Part 2: Arabic language -- Simplified transliteration |
Armenian | Armenian alphabet | ISO 9985:1996 Information and Documentation -- Transliteration of Armenian characters into Latin characters |
Assamese | Bengali alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Bengali | Bengali alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Belarusian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Bulgarian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Chinese | Chinese characters | ISO 7098:2015 Information and Documentation -- Romanization of Chinese |
Georgian | Georgian alphabet | ISO 9984:1996 Information and Documentation -- Transliteration of Georgian characters into Latin characters |
Gujarati | Gujarati alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Hebrew | Hebrew characters | ISO 259-2:1994 Documentation -- Transliteration of Hebrew characters into Latin characters -- Part 2: Simplified transliteration |
Hindi | Devanagari alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Inuktitut | Canadian Aboriginal syllabics | ALA-LC 2011 Inuktitut romanization table |
Kannada | Kannada alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Slavic and non-Slavic Languages | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Macedonian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Malayalam | Malayalam alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Marathi | Devanagari alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Mongolian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Nepali | Devanagari alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Oriya (odia) | Odia alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Pali | Various including Bengali, Burmese, Devanagari, Sinhalese and Thai alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Persian | Persian alphabet | ISO 233-3:1999 Information and Documentation -- Transliteration of Arabic characters into Latin characters -- Part 3: Persian language -- Simplified transliteration |
Russian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Sanskrit, Prakrit | Devanagari alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Serbian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Tajiki | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Tamil | Tamil alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Telugu | Telugu alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
Thai | Thai alphasyllabary | ISO 11940:1998 Information and Documentation -- Transliteration of Thai
(à confirmer) |
Ukrainian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
Yiddish | Hebrew alphabet | ISO 259-2:1994 Documentation -- Transliteration of Hebrew characters into Latin characters -- Part 2: Simplified transliteration |
Non-exhaustive List of Verifications to Make to an Existing Record
General Information
- Verify that the characters used are only those in the MARC 8 character set.
- Genrally, the information must provided in French. If a record is derived from an original English record, one can leave fields 670 and 675 in English but it must be ensured that the information recorded in other fields is in French. It is understood that all information in English will not necessarily have an equivalent in French. This would be the case, for example, for terms belonging to a controlled vocabulary for which there is no French version. In this case, the information must be deleted.
Field | Verification |
---|---|
008 | Verify that the coding is correct. For names (except name-title series), verify that the coding complies with the instructions relating to field 008: names (except name-titles series).
Position 10 (Descriptive cataloging rules) : must be changed to "z". Note: When 008/10 is changed to "z" (Other), a field 040 $e rda is automatically added. The reverse is not true. Position 39 (Source of cataloging): la value initially recorded in this field is retained; do not modify this value when updating a record, except if the initial value was incorrect. The initial value is incorrect if it is not " " [blank] for a record created originally by LAC, BAnQ or LC (symbol CaOONL, CaQMBN or DLC in field 040 $a) or "c" (Cooperative cataloguing program) for a record created originally by an university or NACO participant (symbol for the university or NACO participant appearing in field 040 $a). |
010 | Delete this field if it is present. |
016 | If there is no Canadiana number, verify in the LC field if the same entity is represented by an authority and if it contains a Canadiana number (it is possible to refine the search by using cs:caoonl). If yes, add this number to the record by changing the language code E at the end of the field to the code F (or by adding the code if it is absent).
If there is a Canadiana number but it does not end with the language code F, add this code to the end of the number. |
024 | Verify the coding (in particular subfields $0 and $1 for URIs). |
040 | Ensure that subfield $e rda is present, after having verified that field 1XX, fields 4XX and fields 5XX comply with RDA. |
043 | This field cannot be used in record for geographic names (records with field 151). Delete this field in other cases such as when the record contains an occurrence of field 100, 110, 111 or 130. |
053 | Ensure that classification numbers for class PS8000 are moved to field 065 and that field 053 is deleted.
Example :
Be sure to add a period between the classification number and the Cutter if one exists. Example:
Caution: Field 053 remains valid for LC classification numbers (PA-PT), including the classification numbers PR9180-9199.4 for French-Canadian literature, the classification numbers PR9180-9199.4 for English-Canadian literature and classification numbers PS1-3626 for American literature. |
083 | BAnQ records that were loaded into Canadiana and that contain this field do not contain subfield $2, which prevents the record from being saved. To be able to save the record, change the value in the first indicator to 7 and add subfield $2 23 before subfield $5 CaQMBN.
Exemple :
|
1XX | If the record is not RDA compliant, correct the access point if necessary to make it RDA compliant. |
4XX | If the record is not RDA compliant, correct the access points if necessary to make them RDA compliant.
Add missing dates in field 400 when field 100 contains dates (LAC has had a policy in the past not to add dates systematically.) Delete non-compliant $w subfields. In particular,
|
5XX | If the record is not RDA compliant, correct the access points if necessary to make them RDA compliant, which involves upgrading the authorities attached to the access points.
In the case of a name change for a corporate body, the 5XX fields should link the corporate body in field 1XX only to the immediately preceeding and immediately succeeding entities. Delete all 5XX fields for an entity that preceeds the immediately preceeding entity or succeeds the immediately succeeding entity. For example, in the case of corporate body A which becomes B, which becomes in turn C, the authority for entity A should not contain a 5XX field for entity C and the authority for entity C should not contain a 5XX field for entity A. |
663 | Ensure that the wording of the note complies with the most recent practice (see FAQ – PLC/PCC Practice for Creating NARs for Persons who use Pseudonyms (PDF, 345 KB)). |
665 | This field is not permitted in Canadiana. If possible, transfer the biographical or historical information to a 678 field and delete the 665 field.
Example:
In this example, only the first two phrases can be transferred to a 678 field. The two other phrases are not retained. As the access point is not valid as a subject heading, it is necessary to consider adding the following note in field 667:
|
667 | Ensure that the contents of this field is general enough to be pertinent to cataloguers in other institutions. If not, delete the field.
Examples of 667 fields to delete:
BAnQ: Before sending records to OCLC, ensure that all of the 667 fields have been copied into field 899 in Portfolio to preserve their contents in the event that local content is deleted by another PFAN participant, except fields 667 beginning with one of the following expressions: "En subdivision :", "Ne pas utiliser en subdivision" and "UTILISATION COMME VEDETTE-MATIÈRE :". If the content of a 667 field copied into field 899 is no longer pertinent for BAnQ, consider also deleting the corresponding 899 field in Portfolio. Delete the 667 field containing "CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN" after finalizing the record. |
670 | If the record was derived from a record originally created in English, it is not necessary to translate the field into French, as the case may be.
It is generally not necessary to modify an existing 670 field except in cases provided in the FAQ for field 670 (Source data found) in the name authority record for NACO. |
675 | If the record was derived from a record originally created in English, it is not necessary to translate the field into French, as the case may be.
Occurrences of subfield $a following the first occurrence must be preceeded by a semi-colon, space. Add this punctuation if it is missing. Delete any $a subfield that cites the Canadian authority file (ex. Autorités Canadiana) without accompanying this citation with a consultation date. |
678 | Ensure that the contents of the field truly consist of biographical or historical information and is appropriate for public display. The text must be worded in the form of concise and complete phrases.
The content of all 665 fields in LAC and BAnQ records has been placed in field 678. It is possible that the original field 665 contained instructions about the access point to use as an author or as a subject heading (see the example under field 665 above). Delete these instructions in field 678 if they have been retained. Consider adding a 667 note on the use of the access point as a subject heading, if applicable. Justification de la zone 678 Généralement, une zone 678 doit être justifiée par une zone 670. Si elle n'est pas justifiée et que son contenu est approprié pour une note biographique ou historique, conserver la zone et ajouter une note 670 citant le fichier interne de l'institution qui a fourni la zone 678 comme suit :
Si la notice a été modifiée après avoir été migrée, il faut consulter l’historique de la notice pour déterminer qui a ajouté la zone 678 à l’origine. Si la zone 678 n'est pas justifiée et que son contenu n'est pas approprié pour une note biographique ou historique, ne pas conserver la zone 678 sauf si une note appropriée peut être rédigée avec les informations dont on dispose. Noter que la zone 678 est facultative. Si le contenu de la zone doit être conservé parce qu'il ne se trouve nulle part ailleurs dans la notice, le transférer dans une note 670 citant le fichier interne de l'institution qui a fourni la zone 678. Exemple:
|
7XX | Supprimer la zone si la sous-zone $2 lacnaf est présente. |
Dernière mise à jour : 2020-12-09
Non-exhaustive List of Qualifiers
The non-exhaustive list of qualifiers comprises a series of terms to be used when an RDA instruction requires an added element to distinguish or specify an access point that represents a person, a corporate body or a work (for example, RDA 9.19.1.6).
The following list is a selection of terms whose use is encouraged by the Standards Committee to ensure the consistence of name authorities when a choice between several possible terms must be made. When you have the choice between two terms, give preference to the terms in this list. For example: "Organisme", rather than "Organisation".
This is not a closed list and suggestions are welcome: bac.pfan-fnap.lac@canada.ca.
English Term | French Term | Entity |
---|---|---|
Spacecraft | Véhicule spatial | Corporate Body |
Program | Programme | Corporate Body |
Firm | Firme | Corporate Body |
Organization | Organisme | Corporate Body |
Musical group | Groupe musical | Corporate Body |
Congrès | Corporate Body | |
Conférence | Corporate Body | |
Radio station | Station de radio | Corporate Body |
Television station | Station de télévision | Corporate Body |
Contest | Concours | Corporate Body |
Play | Pièce de théâtre | Work |
Motion picture | Film | Work |
Series | Collection | Work |
Association | Association | Corporate Body |
Lecturer * | Professeur d’université Maître de conférences |
Person |
Computer program
See Computer file |
||
Computer file | Fichier informatique | Work |
* Lecturer
According to the Cambridge dictionary, the term lecturer designates a person who teaches at a college or university, in Anglo-Saxon countries.
Ex. : Lecturer in psychology
This title corresponds to different cases in reality depending on the country where it is used. It would be desirable to use the equivalent French term in relation to what the title represents in the educational system where the author holds the title of lecturer.
Suggestions of French equivalents
- For an author in France who is designated as being "un maître de conférences", use (Maître de conférences)
- According to the Larousse dictionary, the title used by professors of the first rank of the second class of the teaching faculty of universities in France. Equivalent of the Anglo-Saxon term lecturer according to Wikipedia.
- For an author in Europe who is designated as being a lecturer, use (Maître de conférences) or (Professeur d'université)
- For an author who is designated as a lecturer in Australia, use (Professeur d'université)
- For an author who is designated as a lecturer in the United Kingdom, use (Maître de conférences) or (Professeur d'université)
- For an author who is designated as a lecturer in the United States, use (Professeur d'université) or (Chargé de cours)
- For an author who is designated as a lecturer in Canada, use (Chargé de cours)
When in doubt about which French equivalent to use, consult the List of academic ranks de Wikipédia in particular for the countries not mentioned above.
Lastly, note that a senior lecturer is more of a "professeur associé" than a "chargé de cours".
Last Update: June 19, 2020