yes-man-today
commited on
Merge branch 'main' of hf.co:datasets/ro-h/regulatory_comments_api
Browse files
README.md
CHANGED
@@ -9,7 +9,7 @@ pretty_name: Regulation.gov Public Comments API
|
|
9 |
size_categories:
|
10 |
- n<1K
|
11 |
---
|
12 |
-
# Dataset Card for
|
13 |
|
14 |
United States governmental agencies often make proposed regulations open to the public for comment.
|
15 |
Proposed regulations are organized into "dockets". This dataset will use Regulation.gov public API
|
@@ -40,19 +40,31 @@ If a larger set of dockets are required, consider requesting a rate-unlimited AP
|
|
40 |
The following information is included in this dataset:
|
41 |
|
42 |
**Docket Metadata**
|
|
|
43 |
id (int): A unique numerical identifier assigned to each regulatory docket.
|
|
|
44 |
title (str): The official title or name of the regulatory docket. This title typically summarizes the main issue or area of regulation covered by the docket.
|
|
|
45 |
context (str): The date when the docket was last modified on Regulations.gov.
|
|
|
46 |
purpose (str): Whether the docket was rulemaking, non-rulemaking, or other.
|
|
|
47 |
keywords (list): A string of keywords, as determined by Regulations.gov.
|
48 |
|
49 |
**Comment Metadata**
|
|
|
50 |
comment_id (int): A unique numerical identifier for each public comment submitted on the docket.
|
|
|
51 |
comment_title (str): The title or subject line of the individual public comment.
|
|
|
52 |
comment_url (str): A URL or web link to the specific comment or docket on Regulations.gov. This allows direct access to the original document or page for replicability purposes.
|
|
|
53 |
comment_date (str): The date when the comment was posted on Regulations.gov. This is important for understanding the timeline of public engagement.
|
|
|
54 |
commenter_fname (str): The first name of the individual or entity that submitted the comment. This could be a person, organization, business, or government entity.
|
|
|
55 |
commenter_lname (str): The last name of the individual or entity that submitted the comment.
|
|
|
56 |
comment_length (int): The length of the comment in terms of the number of characters (spaces included)
|
57 |
|
58 |
**Comment Content**
|
|
|
9 |
size_categories:
|
10 |
- n<1K
|
11 |
---
|
12 |
+
# Dataset Card for Regulatory Comments (Direct API Call)
|
13 |
|
14 |
United States governmental agencies often make proposed regulations open to the public for comment.
|
15 |
Proposed regulations are organized into "dockets". This dataset will use Regulation.gov public API
|
|
|
40 |
The following information is included in this dataset:
|
41 |
|
42 |
**Docket Metadata**
|
43 |
+
|
44 |
id (int): A unique numerical identifier assigned to each regulatory docket.
|
45 |
+
|
46 |
title (str): The official title or name of the regulatory docket. This title typically summarizes the main issue or area of regulation covered by the docket.
|
47 |
+
|
48 |
context (str): The date when the docket was last modified on Regulations.gov.
|
49 |
+
|
50 |
purpose (str): Whether the docket was rulemaking, non-rulemaking, or other.
|
51 |
+
|
52 |
keywords (list): A string of keywords, as determined by Regulations.gov.
|
53 |
|
54 |
**Comment Metadata**
|
55 |
+
|
56 |
comment_id (int): A unique numerical identifier for each public comment submitted on the docket.
|
57 |
+
|
58 |
comment_title (str): The title or subject line of the individual public comment.
|
59 |
+
|
60 |
comment_url (str): A URL or web link to the specific comment or docket on Regulations.gov. This allows direct access to the original document or page for replicability purposes.
|
61 |
+
|
62 |
comment_date (str): The date when the comment was posted on Regulations.gov. This is important for understanding the timeline of public engagement.
|
63 |
+
|
64 |
commenter_fname (str): The first name of the individual or entity that submitted the comment. This could be a person, organization, business, or government entity.
|
65 |
+
|
66 |
commenter_lname (str): The last name of the individual or entity that submitted the comment.
|
67 |
+
|
68 |
comment_length (int): The length of the comment in terms of the number of characters (spaces included)
|
69 |
|
70 |
**Comment Content**
|