Update README.md
Browse files
README.md
CHANGED
|
@@ -8,12 +8,14 @@ tags:
|
|
| 8 |
pretty_name: Regulation.gov Public Comments API
|
| 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
|
| 16 |
-
to aggregate and clean public comments for dockets
|
| 17 |
|
| 18 |
Each example will consist of one docket, and include metadata such as docket id, docket title, etc.
|
| 19 |
Each docket entry will also include information about the top 10 comments, including comment metadata
|
|
@@ -27,8 +29,10 @@ reference https://huggingface.co/datasets/ro-h/regulatory_comments.
|
|
| 27 |
|
| 28 |
### Dataset Description and Structure
|
| 29 |
|
| 30 |
-
This dataset will call the API to individually gather docket and comment information
|
| 31 |
-
|
|
|
|
|
|
|
| 32 |
API limit is 1000 calls per hour. Since each comment's text requires an individual call and there will be ~10 comments collected per docket,
|
| 33 |
only around 100 dockets can be collected without extending the limit. Furthermore, since some dockets don't have comment data and
|
| 34 |
thus will not be included, it is realistic to expect approximatley 60-70 dockets collected. For this number of dockets, expect a load
|
|
@@ -70,6 +74,14 @@ comment_length (int): The length of the comment in terms of the number of charac
|
|
| 70 |
**Comment Content**
|
| 71 |
text (str): The actual text of the comment submitted. This is the primary content for analysis, containing the commenter's views, arguments, and feedback on the regulatory matter.
|
| 72 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 73 |
- **Curated by:** Ro Huang
|
| 74 |
|
| 75 |
### Dataset Sources
|
|
@@ -107,8 +119,7 @@ accordingly.
|
|
| 107 |
|
| 108 |
While this is a vital part of the United States regulatory process, there is little understanding of how agencies approach
|
| 109 |
public comments and modify their proposed regulations. Further, the data extracted from the API is often unclean and difficult
|
| 110 |
-
to navigate.
|
| 111 |
-
an issue that a diversity of stakeholders have investment in.
|
| 112 |
|
| 113 |
#### Data Collection and Processing
|
| 114 |
|
|
|
|
| 8 |
pretty_name: Regulation.gov Public Comments API
|
| 9 |
size_categories:
|
| 10 |
- n<1K
|
| 11 |
+
task_categories:
|
| 12 |
+
- text-classification
|
| 13 |
---
|
| 14 |
# Dataset Card for Regulatory Comments (Direct API Call)
|
| 15 |
|
| 16 |
United States governmental agencies often make proposed regulations open to the public for comment.
|
| 17 |
Proposed regulations are organized into "dockets". This dataset will use Regulation.gov public API
|
| 18 |
+
to aggregate and clean public comments for dockets selected by the user
|
| 19 |
|
| 20 |
Each example will consist of one docket, and include metadata such as docket id, docket title, etc.
|
| 21 |
Each docket entry will also include information about the top 10 comments, including comment metadata
|
|
|
|
| 29 |
|
| 30 |
### Dataset Description and Structure
|
| 31 |
|
| 32 |
+
This dataset will call the API to individually gather docket and comment information. The user must input their
|
| 33 |
+
own API key ([https://open.gsa.gov/api/regulationsgov/]), as well as a list of dockets they want to draw information from.
|
| 34 |
+
|
| 35 |
+
Data collection will stop when all dockets input have been gathered, or when the API hits a rate-limit. The government
|
| 36 |
API limit is 1000 calls per hour. Since each comment's text requires an individual call and there will be ~10 comments collected per docket,
|
| 37 |
only around 100 dockets can be collected without extending the limit. Furthermore, since some dockets don't have comment data and
|
| 38 |
thus will not be included, it is realistic to expect approximatley 60-70 dockets collected. For this number of dockets, expect a load
|
|
|
|
| 74 |
**Comment Content**
|
| 75 |
text (str): The actual text of the comment submitted. This is the primary content for analysis, containing the commenter's views, arguments, and feedback on the regulatory matter.
|
| 76 |
|
| 77 |
+
|
| 78 |
+
|
| 79 |
+
Note that commenter name features were phased in later in the system, so some dockets will have no
|
| 80 |
+
first name/last name entries. Further, some comments were uploaded solely via attachment,
|
| 81 |
+
and are stored in the system as null; the API has no access to comment attachments.
|
| 82 |
+
Finally, note that huggingface converts lists of dictionaries to dictionaries of lists.
|
| 83 |
+
|
| 84 |
+
|
| 85 |
- **Curated by:** Ro Huang
|
| 86 |
|
| 87 |
### Dataset Sources
|
|
|
|
| 119 |
|
| 120 |
While this is a vital part of the United States regulatory process, there is little understanding of how agencies approach
|
| 121 |
public comments and modify their proposed regulations. Further, the data extracted from the API is often unclean and difficult
|
| 122 |
+
to navigate.
|
|
|
|
| 123 |
|
| 124 |
#### Data Collection and Processing
|
| 125 |
|