Create README.md
Browse files
README.md
ADDED
@@ -0,0 +1,143 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
---
|
2 |
+
language:
|
3 |
+
- en
|
4 |
+
pretty_name: Possible Police Agency Homepage URLs
|
5 |
+
---
|
6 |
+
# Dataset Card for Dataset Name
|
7 |
+
|
8 |
+
<!-- Provide a quick summary of the dataset. -->
|
9 |
+
|
10 |
+
This dataset aggregates potential homepage URLs for police agencies, paired with Google Search snippets that describe each homepage. It aims to facilitate research, development, and verification tasks related to digital public safety resources.
|
11 |
+
## Dataset Details
|
12 |
+
|
13 |
+
This dataset compiles ten pairs of URLs and corresponding Google Search snippets for each police agency investigated.
|
14 |
+
|
15 |
+
### Dataset Description
|
16 |
+
|
17 |
+
<!-- Provide a longer summary of what this dataset is. -->
|
18 |
+
|
19 |
+
|
20 |
+
|
21 |
+
- **Curated by:** Police Data Accessibility Project
|
22 |
+
- **Funded by [optional]:** [More Information Needed]
|
23 |
+
- **Shared by [optional]:** [More Information Needed]
|
24 |
+
- **Language(s) (NLP):** [More Information Needed]
|
25 |
+
- **License:** [More Information Needed]
|
26 |
+
|
27 |
+
### Dataset Sources [optional]
|
28 |
+
|
29 |
+
<!-- Provide the basic links for the dataset. -->
|
30 |
+
|
31 |
+
- **Repository:** https://github.com/Police-Data-Accessibility-Project/data-source-identification
|
32 |
+
|
33 |
+
## Uses
|
34 |
+
|
35 |
+
<!-- Address questions around how the dataset is intended to be used. -->
|
36 |
+
|
37 |
+
### Direct Use
|
38 |
+
|
39 |
+
<!-- This section describes suitable use cases for the dataset. -->
|
40 |
+
|
41 |
+
This dataset is suitable for use in projects that require the identification or verification of official police agency homepages, such as data enrichment in research databases, verification tasks for public safety applications, and training datasets for machine learning models focused on URL classification or information retrieval.
|
42 |
+
### Out-of-Scope Use
|
43 |
+
|
44 |
+
<!-- This section addresses misuse, malicious use, and uses that the dataset will not work well for. -->
|
45 |
+
|
46 |
+
This dataset is not intended for use in operational systems without further verification of URL authenticity. It should not be used as a sole source for critical applications that require up-to-date and officially verified data.
|
47 |
+
|
48 |
+
## Dataset Structure
|
49 |
+
|
50 |
+
<!-- This section provides a description of the dataset fields, and additional information about the dataset structure such as criteria used to create the splits, relationships between data points, etc. -->
|
51 |
+
|
52 |
+
Each entry in the dataset represents a police agency, identified by a unique agency ID and name, and includes a list of ten URL and snippet pairs that potentially correspond to the agency's official homepage.
|
53 |
+
|
54 |
+
## Dataset Creation
|
55 |
+
|
56 |
+
### Curation Rationale
|
57 |
+
|
58 |
+
<!-- Motivation for the creation of this dataset. -->
|
59 |
+
|
60 |
+
The dataset was created to address the need for a comprehensive and accessible repository of potential police agency homepage URLs, to support research, development, and verification efforts in public safety and law enforcement domains.
|
61 |
+
|
62 |
+
### Source Data
|
63 |
+
|
64 |
+
<!-- This section describes the source data (e.g. news text and headlines, social media posts, translated sentences, ...). -->
|
65 |
+
|
66 |
+
#### Data Collection and Processing
|
67 |
+
|
68 |
+
<!-- This section describes the data collection and processing process such as data selection criteria, filtering and normalization methods, tools and libraries used, etc. -->
|
69 |
+
|
70 |
+
Data was collected using automated scripts that performed Google Searches for each police agency and extracted the top ten URLs and their corresponding snippets.
|
71 |
+
|
72 |
+
#### Who are the source data producers?
|
73 |
+
|
74 |
+
<!-- This section describes the people or systems who originally created the data. It should also include self-reported demographic or identity information for the source data creators if this information is available. -->
|
75 |
+
|
76 |
+
The data was produced by automated scripts designed and implemented by the dataset curators, with manual oversight to ensure quality and relevance.
|
77 |
+
|
78 |
+
### Annotations [optional]
|
79 |
+
|
80 |
+
<!-- If the dataset contains annotations which are not part of the initial data collection, use this section to describe them. -->
|
81 |
+
|
82 |
+
#### Annotation process
|
83 |
+
|
84 |
+
<!-- This section describes the annotation process such as annotation tools used in the process, the amount of data annotated, annotation guidelines provided to the annotators, interannotator statistics, annotation validation, etc. -->
|
85 |
+
|
86 |
+
[More Information Needed]
|
87 |
+
|
88 |
+
#### Who are the annotators?
|
89 |
+
|
90 |
+
<!-- This section describes the people or systems who created the annotations. -->
|
91 |
+
|
92 |
+
[More Information Needed]
|
93 |
+
|
94 |
+
#### Personal and Sensitive Information
|
95 |
+
|
96 |
+
<!-- State whether the dataset contains data that might be considered personal, sensitive, or private (e.g., data that reveals addresses, uniquely identifiable names or aliases, racial or ethnic origins, sexual orientations, religious beliefs, political opinions, financial or health data, etc.). If efforts were made to anonymize the data, describe the anonymization process. -->
|
97 |
+
|
98 |
+
The dataset does not contain personal or sensitive information. URLs and snippets were collected from public Google Search results.
|
99 |
+
|
100 |
+
## Bias, Risks, and Limitations
|
101 |
+
|
102 |
+
<!-- This section is meant to convey both technical and sociotechnical limitations. -->
|
103 |
+
|
104 |
+
The dataset may reflect the biases inherent in Google Search algorithms and the potentially dynamic nature of URLs. Users should be aware that the dataset might not always represent the current official homepage of a police agency.
|
105 |
+
|
106 |
+
### Recommendations
|
107 |
+
|
108 |
+
Users are encouraged to verify the currentness and authenticity of URLs when using this dataset for critical applications. Additionally, consideration should be given to the potential biases in search engine results.
|
109 |
+
|
110 |
+
## Citation [optional]
|
111 |
+
|
112 |
+
<!-- If there is a paper or blog post introducing the dataset, the APA and Bibtex information for that should go in this section. -->
|
113 |
+
|
114 |
+
**BibTeX:**
|
115 |
+
|
116 |
+
@misc{possible_police_agency_homepage_urls,
|
117 |
+
author = {Police Data Accessibility Project},
|
118 |
+
title = {Possible Police Agency Homepage URLs Dataset},
|
119 |
+
year = {2024},
|
120 |
+
publisher = {GitHub/HuggingFace},
|
121 |
+
}
|
122 |
+
|
123 |
+
**APA:**
|
124 |
+
|
125 |
+
Police Data Accessibility Project. (2024). Possible Police Agency Homepage URLs Dataset. GitHub/HuggingFace.
|
126 |
+
|
127 |
+
## Glossary [optional]
|
128 |
+
|
129 |
+
<!-- If relevant, include terms and calculations in this section that can help readers understand the dataset or dataset card. -->
|
130 |
+
|
131 |
+
[More Information Needed]
|
132 |
+
|
133 |
+
## More Information [optional]
|
134 |
+
|
135 |
+
[More Information Needed]
|
136 |
+
|
137 |
+
## Dataset Card Authors [optional]
|
138 |
+
|
139 |
+
[More Information Needed]
|
140 |
+
|
141 |
+
## Dataset Card Contact
|
142 |
+
|
143 |
+
[More Information Needed]
|