1

2

Note there is a big difference of LC treating subject compilation between AACR2 25.15A1 and RDA 6.16.2.5.1 LCPS in 6.16.2.5.1: If a subject compilation lacks a collective title, construct an authorized access point representing the compilation using a devised title formulated according to the instructions in RDA 2.3.2.11. AACR2 25.15 A1 LCRI: If a subject compilation lacks both a citation title and a collective title, use the uniform title of the first law in the collection (even if the title page title is identical with this uniform title). NOTE: for single law, AACR2 25.15 has one more rule: If there are several different laws, etc., with the same title entered under the heading for the same jurisdiction, add the year of promulgation. United Kingdom [Education Act (1944)]

3

Session laws: add to "Laws, etc." the phrase "Session laws" followed by the date(s) covered. Enclose temporary date(s) in angle brackets. If the public laws and private laws or general laws and special laws are regularly published as separate editions, add "Public laws" and "Private laws" or "General laws" and "Special laws," as appropriate, after the date(s)

4

5

AACR2 25.16 B2: Use as the uniform title for a treaty, etc., between four or more parties the name by which the treaty is known. Use an English name if there is one. Add, in parentheses, the year, earlier year, or earliest year of signing. RDA 6.19.2.7: It’s not required to use English name if available; in addition; no abbreviations in the date.

6

7

8

9

10

NOTE: RDA 19.2 and 19.3 don't say anything about what should be a main access point (i.e. authorized access point) and what should be a variant access point. They just tell you what should be recorded in the element Creator or the element Other Person, Family or Corporate Body Associated with Legal Works. A work can have more than one creator, and in most cases the creator or the first-named creator will also be used in the authorized access point, but not always. Laws enacted by a different jurisdiction are a case in point.

11

Note in AACR2 21.31.B2: Make added entries under the headings for the jurisdictions governed if there are two or three. If there are four or more jurisdictions and they are named in the chief source of information of the item being catalogued, make an added entry under the heading for the one named first. If all the laws are enacted by a single jurisdiction, make an added entry under the heading for the enacting jurisdiction. Add a uniform title as instructed in 25.15A to each added entry heading. RDA: no rule of 3, you may list all the jurisdictions; if there is collective title, based on LCPS 25.1, use 505 to list all the laws/jurisdiction; first law/predominant law is required as additional access point; if no collective title, list all the title in 245, no 505 needed, but you may still use first law/predominant law as additional access point or you may choose list all of them.

12

13

LCPS 6.29.1.7: The major types of U.S. publications that are covered by RDA 6.29.1.7 are the following: 1.rules or regulations: statements of general or specific applicability designed to implement or interpret law or policy; 2.licenses: permits, certificates, or other forms of permission; 3.advisory opinions: advice regarding proposed action; the advice is not binding but serves only to convey authoritative interpretations of statutes or regulations; 4.decisions: statements adjudicating controversies that arise from the violation or interpretation of statutes and administrative regulations or rules. Such a function is performed by special boards of review, administrative law judges, hearing examiners, and other officers through administrative decisions. NOTE: for laws and regulations issued together, there is a difference between AACR2 and RDA. AACR2 21.32A2 will established authorized access point based the first named entity, but RDA 6.29.1.8 alternative and LCPS will make the access point under law.

14

15

NOTE: here again confusing part, promulgating agency is creator, but it should not be put in MARC 110 since based on 6.29.1.10 court governed should be treated as authorized access point. Promulgating agency as creator is a core element, which is required.

16

17

18

19

NOTE: In AACR2 21.35A1, signatories within 2-3, list others other than the main access point; AACR2 21.35.A2, 4 or more signatories, list the home country if it’s a signatory; or the first named on in the resource in LCRI 21.35A1, LC will not add various access points for other signatories to the treaty, but will add to authority records as reference access points. BUT RDA 6.29.3.3 add all other signatories, they will be considered as “Creator” as in RDA 19.2.1.3, no number limit, but only the first one is required as core element. For bilateral treaty, both sides are core elements. NOTE: In AACR2 21.35A1 if agreement between multiple (2 or more ) national governments, construct main access point under first government according to English alphabet. RDA, no such rule.

20

Note: 1 If no consistency in order in which governments are named, use govt. named first in first resource received 2. If first signatory can’t be determined use preferred title of treaty

21

RDA 6.29.3.3 For a treaty or other agreement between two or more of the following: a)national governments b)international intergovernmental bodies c)the Holy See d)jurisdictions now below the national level but retaining treaty-making powers construct additional variant access points using the authorized access points representing each of the signatories to the treaty, etc. (other than the one used to construct the authorized access point). Make additions to the variant access points NOTE: only bilateral treaty, the other party is required as various access points as a core element.

22

Note: As creators, only the first signatory of the treaties is the core element and is required.

23

NOTE: report of one court (recent updates)

24

Here is the reference list. Very useful. However, nothing can compare with reading through the rules by yourself.

25

Microsoft Engineering Excellence

Microsoft Confidential 26