ro-h commited on
Commit
82e723b
1 Parent(s): 01ed5e9

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +14 -2
README.md CHANGED
@@ -30,7 +30,7 @@ directly, reference [https://huggingface.co/datasets/ro-h/regulatory_comments_ap
30
 
31
  ### Dataset Description and Structure
32
 
33
- This dataset will contain approximately 70 dockets. The number of dockets included are rate-limited by the
34
  government API. If a larger set of dockets are required, consider requesting a rate-unlimited API key and
35
  directly calling from the API using [https://huggingface.co/datasets/ro-h/regulatory_comments_api].
36
 
@@ -40,19 +40,31 @@ Comments will be retrieved in relevance order according to Regulation.gov.
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**
 
30
 
31
  ### Dataset Description and Structure
32
 
33
+ This dataset will contain approximately 100 dockets. The number of dockets included are rate-limited by the
34
  government API. If a larger set of dockets are required, consider requesting a rate-unlimited API key and
35
  directly calling from the API using [https://huggingface.co/datasets/ro-h/regulatory_comments_api].
36
 
 
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(str)): A list of string 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**