This chapter comprises general guidance that applies to all works for individual treaties and individual treaty protocols in the Name Authority File.
Note on Past Practices
Practices in NARs for treaties have changed over the years. Therefore, use caution in copying or deriving from existing records.
Works vs. Expressions
GPO establishes treaties at the work level. If a treaty contains text in more than one language, record information only for the English. Do not establish individual NARs for the other language versions. Do not provide a 377 field.
What to Establish in the Authority File
- Establish treaties when cataloging publications comprising treaties, such as the Department of State’s Treaties and other international acts series (n 84731555), or the Senate’s Treaty doc. Series (n 86729721). For more information on these series, see: Bibliographic Cataloging: Treaties.
- Establish treaties when needed for a subject or related work access point
- Follow A.18: Names of Documents and A.10: General Guideline for English Language Capitalization
- GPO Practice: Capitalize both the preferred and variant titles of the treaty wherever these occur in the NAR.
Preferred Titles for Treaties
- Apply 126.96.36.199
- Since the treaty series that GPO catalog essentially “package” the treaty, take the preferred name from the caption, if available, of the treaty itself (e.g., from page ) rather than from the cover or title page.
Authorized Access Points for Treaties
- Apply the following RDA instructions: 188.8.131.52, 184.108.40.206, and 220.127.116.11.1
- Add the full date of signing to the authorized access point.
- Record the date when a treaty was signed as fully as possible in this order: year, month, and day.
- See examples in RDA 18.104.22.168.1
Authorized Access Points for Protocols
- Apply 22.214.171.124, 126.96.36.199, and 188.8.131.52.3
- Tip: the key point to remember is that the authorized access point for the protocol must collocate with that of the original treaty. Consequently, the preferred title for the protocol may not even appear in the resource cataloged, let alone in the preferred source. This may seem to contradict normal cataloging practice. Titles of the protocol that would normally be recorded as preferred titles, may instead be recorded as variant titles.
Dates of Treaties and Protocols
- Apply the following RDA instructions: 6.20.3
When to Recode pre-RDA Treaty NARs to RDA
- Whenever updating an existing pre-RDA treaty NAR, recode it to RDA. Consult: Name Authorities: RDA, General Policies: When to Recode an Existing NAR to RDA.
- Common situation: when cataloging a protocol to an existing treaty NAR that is coded AACR2, you must first recode the original treaty to RDA, so that the protocol will be RDA compliant while collocating with the original treaty.
MARC Fields for Treaties and Protocols
046 – Special Coded Dates
Record the date of signing, etc. in subfield ǂk
370 – Associated Place
Record the location of the signing, etc. in subfield ǂg
380 - Form of Work
Use: 380 Treaties ǂ2 lcsh
4XX – Variant Access Points
- Apply RDA 6.19.3, and 184.108.40.206
- Tip: Include the same date as in the authorized access point (220.127.116.11).
- GPO Practice: for multilateral treaties, make up to ten variant access points under jurisdictions.
- Titles of protocols that would normally be recorded as preferred titles, may instead be recorded as variant titles.