ro-h commited on
Commit
03fdbe6
1 Parent(s): d664719

Create README.md

Browse files
Files changed (1) hide show
  1. README.md +111 -0
README.md ADDED
@@ -0,0 +1,111 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Dataset Card for Dataset Name
2
+
3
+ United States governmental agencies often make proposed regulations open to the public for comment.
4
+ Proposed regulations are organized into "dockets". This dataset will use Regulation.gov public API
5
+ to aggregate and clean public comments for dockets that mention opioid use.
6
+
7
+ Each example will consist of one docket, and include metadata such as docket id, docket title, etc.
8
+ Each docket entry will also include information about the top 10 comments, including comment metadata
9
+ and comment text.
10
+
11
+ In this version, the data is called directly from the API, which can result in slow load times.
12
+ If the user wants to simply load a pre-downloaded dataset,
13
+ reference https://huggingface.co/datasets/ro-h/regulatory_comments.
14
+
15
+ ## Dataset Details
16
+
17
+ ### Dataset Description and Structure
18
+
19
+ This dataset will contain approximately 70 dockets. The number of dockets included are rate-limited by the
20
+ government API. If a larger set of dockets are required, consider requesting a rate-unlimited API key and
21
+ directly calling from the API using [https://huggingface.co/datasets/ro-h/regulatory_comments_api].
22
+
23
+ Each docket will be associated with at least one comment. The maximum number of comments per docket is 10.
24
+ Comments will be retrieved in relevance order according to Regulation.gov.
25
+
26
+ The following information is included in this dataset:
27
+
28
+ **Docket Metadata**
29
+ id (int): A unique numerical identifier assigned to each regulatory docket.
30
+ 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.
31
+ context (str): The date when the docket was last modified on Regulations.gov.
32
+ purpose (str): Whether the docket was rulemaking, non-rulemaking, or other.
33
+ keywords (list): A string of keywords, as determined by Regulations.gov.
34
+
35
+ **Comment Metadata**
36
+ comment_id (int): A unique numerical identifier for each public comment submitted on the docket.
37
+ comment_title (str): The title or subject line of the individual public comment.
38
+ 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.
39
+ comment_date (str): The date when the comment was posted on Regulations.gov. This is important for understanding the timeline of public engagement.
40
+ 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.
41
+ commenter_lname (str): The last name of the individual or entity that submitted the comment.
42
+ comment_length (int): The length of the comment in terms of the number of characters (spaces included)
43
+
44
+ **Comment Content**
45
+ 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.
46
+
47
+ - **Curated by:** Ro Huang
48
+
49
+ ### Dataset Sources
50
+
51
+ - **Repository:** [https://huggingface.co/datasets/ro-h/regulatory_comments_api]
52
+ - **Original Website:** [https://www.regulations.gov/]
53
+ - **API Website:** [https://open.gsa.gov/api/regulationsgov/]
54
+
55
+ ## Uses
56
+
57
+ This dataset may be used by researchers or policy-stakeholders curious about the influence of
58
+ public comments on regulation development. For example, sentiment analysis may be run on
59
+ comment text; alternatively, simple descriptive analysis on the comment length and agency regulation
60
+ may prove interesting.
61
+
62
+ ## Dataset Creation
63
+
64
+ ### Curation Rationale
65
+
66
+ After a law is passed, it may require specific details or guidelines to be practically enforceable or operable.
67
+ Federal agencies and the Executive branch engage in rulemaking, which specify the practical ways that legislation
68
+ can get turned into reality. Then, they will open a Public Comment period in which they will receive comments,
69
+ suggestions, and questions on the regulations they proposed. After taking in the feedback, the agency will modify their
70
+ regulation and post a final rule.
71
+
72
+ As an example, imagine that the legislative branch of the government passes a bill to increase the number of hospitals
73
+ nationwide. While the Congressman drafting the bill may have provided some general guidelines (e.g., there should be at
74
+ least one hospital in a zip code), there is oftentimes ambiguity on how the bill’s goals should be achieved.
75
+ The Department of Health and Human Services is tasked with implementing this new law, given its relevance to national
76
+ healthcare infrastructure. The agency would draft and publish a set of proposed rules, which might include criteria for
77
+ where new hospitals can be built, standards for hospital facilities, and the process for applying for federal funding.
78
+ During the Public Comment period, healthcare providers, local governments, and the public can provide feedback or express
79
+ concerns about the proposed rules. The agency will then read through these public comments, and modify their regulation
80
+ accordingly.
81
+
82
+ While this is a vital part of the United States regulatory process, there is little understanding of how agencies approach
83
+ public comments and modify their proposed regulations. Further, the data extracted from the API is often unclean and difficult
84
+ to navigate. This dataset seeks to offer some clarity through aggregating comments related to Opioid Use Disorders,
85
+ an issue that a diversity of stakeholders have investment in.
86
+
87
+
88
+ #### Data Collection and Processing
89
+
90
+ **Filtering Methods:**
91
+ For each docket, we retrieve relevant metadata such as docket ID,
92
+ title, context, purpose, and keywords. Additionally, the top 10 comments
93
+ for each docket are collected, including their metadata (comment ID, URL, date,
94
+ title, commenter's first and last name) and the comment text itself. The process
95
+ focuses on the first page of 25 comments for each docket, and the top 10 comments
96
+ are selected based on their order of appearance in the API response.
97
+
98
+ **Data Normalization:**
99
+ The collected data is normalized into a structured format. Each docket and
100
+ its associated comments are organized into a nested dictionary structure.
101
+ This structure includes key information about the docket and a list of comments,
102
+ each with its detailed metadata.
103
+
104
+ **Tools and Libraries Used:**
105
+ Requests Library: Used for making API calls to the Regulations.gov API to fetch dockets and comments data.
106
+ Datasets Library from HuggingFace: Employed for defining and managing the dataset's structure and generation process.
107
+ Python: The entire data collection and processing script is written in Python.
108
+
109
+ **Error Handling:**
110
+ In the event of a failed API request (indicated by a non-200 HTTP response status),
111
+ the data collection process for the current docket is halted, and the process moves to the next docket.