ronald commited on
Commit
97ab0fa
1 Parent(s): 50e2564

initial commit

Browse files
Files changed (1) hide show
  1. README.md +189 -1
README.md CHANGED
@@ -11,4 +11,192 @@ tags:
11
  pretty_name: scitechnews
12
  size_categories:
13
  - 1K<n<10K
14
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
11
  pretty_name: scitechnews
12
  size_categories:
13
  - 1K<n<10K
14
+ ---
15
+
16
+
17
+ # Dataset Card for SciTechNews
18
+
19
+ ## Dataset Description
20
+
21
+ - **Repository:** [https://github.com/ronaldahmed/scitechnews]()
22
+ - **Paper:** [link](‘Don’t Get Too Technical with Me’: A Discourse Structure-Based Framework for Science Journalism)
23
+ - **Point of Contact:** [mailto:ronald.cardenas@ed.ac.uk](Ronald Cardenas)
24
+
25
+ ### Dataset Summary
26
+
27
+ The SciTechNews dataset consists of scientific papers paired with their corresponding
28
+ press release snippet mined from [ACM TechNews](https://technews.acm.org/).
29
+ ACM TechNews is a news aggregator that provides regular news digests about scientific achieve-
30
+ ments and technology in the areas of Computer Science, Engineering, Astrophysics, Biology, and
31
+ others.
32
+
33
+
34
+ ### Supported Tasks and Leaderboards
35
+
36
+ For each of the tasks tagged for this dataset, give a brief description of the tag, metrics, and suggested models (with a link to their HuggingFace implementation if available). Give a similar description of tasks that were not covered by the structured tag set (repace the `task-category-tag` with an appropriate `other:other-task-name`).
37
+
38
+ - `task-category-tag`: The dataset can be used to train a model for [TASK NAME], which consists in [TASK DESCRIPTION]. Success on this task is typically measured by achieving a *high/low* [metric name](https://huggingface.co/metrics/metric_name). The ([model name](https://huggingface.co/model_name) or [model class](https://huggingface.co/transformers/model_doc/model_class.html)) model currently achieves the following score. *[IF A LEADERBOARD IS AVAILABLE]:* This task has an active leaderboard which can be found at [leaderboard url]() and ranks models based on [metric name](https://huggingface.co/metrics/metric_name) while also reporting [other metric name](https://huggingface.co/metrics/other_metric_name).
39
+
40
+ ### Languages
41
+
42
+ English
43
+
44
+ ## Dataset Structure
45
+
46
+
47
+ ### Data Fields
48
+
49
+ - `id`: unique identifier
50
+ - `pr-title`: Title of press release snippet
51
+ - `pr-summary`: Press release summary
52
+ - `pr-article`: Body of press release article
53
+ - `sc-title`: Title of scientific article
54
+ - `sc-abstract`: Abstract of scientific article
55
+ - `sc-article`: Concatenated sections of the scientific article
56
+ - `sc-sections`: List of sections in the scientific article
57
+ - `sc-section-names`: List of sections names in the scientific article
58
+ - `sc-authors`: list of authors' name and affiliations, in the format '<name> | <affil>'
59
+
60
+
61
+ Paragraphs in the press release articles (`pr-article`) and sections of the scientific article (`sc-sections`)
62
+ are separated by `\n`. Data is not sentence or word tokenized.<br>
63
+
64
+
65
+
66
+ ### Example Instance
67
+
68
+
69
+ ```
70
+ {
71
+ "id": String, # unique ID
72
+ "pr-title": String, # Title as found in the ACMTECHNEWS website
73
+ "pr-article": String, # Press release article
74
+ "pr-summary": String, # Press release summary
75
+ "sc-title": String, # Title of scientific article
76
+ "sc-abstract": String, # Abstract of scientific article
77
+ "sc-sections": List[String], # List of sections in the scientific article
78
+ "sc-section_names": List[String] # List of section names
79
+ "sc-authors": List[String] # list of authors' name and affiliations, in the format '<name> | <affil>'
80
+
81
+ }
82
+ ```
83
+
84
+ Provide any additional information that is not covered in the other sections about the data here. In particular describe any relationships between data points and if these relationships are made explicit.
85
+
86
+
87
+ ### Data Splits
88
+
89
+ Describe and name the splits in the dataset if there are more than one.
90
+
91
+ Describe any criteria for splitting the data, if used. If there are differences between the splits (e.g. if the training annotations are machine-generated and the dev and test ones are created by humans, or if different numbers of annotators contributed to each example), describe them here.
92
+
93
+ Provide the sizes of each split. As appropriate, provide any descriptive statistics for the features, such as average length. For example:
94
+
95
+ | | train | validation | test |
96
+ |-------------------------|------:|-----------:|-----:|
97
+ | Input Sentences | | | |
98
+ | Average Sentence Length | | | |
99
+
100
+ ## Dataset Creation
101
+
102
+ ### Curation Rationale
103
+
104
+ What need motivated the creation of this dataset? What are some of the reasons underlying the major choices involved in putting it together?
105
+
106
+ ### Source Data
107
+
108
+ This section describes the source data (e.g. news text and headlines, social media posts, translated sentences,...)
109
+
110
+ #### Initial Data Collection and Normalization
111
+
112
+ Describe the data collection process. Describe any criteria for data selection or filtering. List any key words or search terms used. If possible, include runtime information for the collection process.
113
+
114
+ If data was collected from other pre-existing datasets, link to source here and to their [Hugging Face version](https://huggingface.co/datasets/dataset_name).
115
+
116
+ If the data was modified or normalized after being collected (e.g. if the data is word-tokenized), describe the process and the tools used.
117
+
118
+ #### Who are the source language producers?
119
+
120
+ State whether the data was produced by humans or machine generated. Describe the people or systems who originally created the data.
121
+
122
+ If available, include self-reported demographic or identity information for the source data creators, but avoid inferring this information. Instead state that this information is unknown. See [Larson 2017](https://www.aclweb.org/anthology/W17-1601.pdf) for using identity categories as a variables, particularly gender.
123
+
124
+ Describe the conditions under which the data was created (for example, if the producers were crowdworkers, state what platform was used, or if the data was found, what website the data was found on). If compensation was provided, include that information here.
125
+
126
+ Describe other people represented or mentioned in the data. Where possible, link to references for the information.
127
+
128
+ ### Annotations
129
+
130
+ If the dataset contains annotations which are not part of the initial data collection, describe them in the following paragraphs.
131
+
132
+ #### Annotation process
133
+
134
+ If applicable, describe the annotation process and any tools used, or state otherwise. Describe the amount of data annotated, if not all. Describe or reference annotation guidelines provided to the annotators. If available, provide interannotator statistics. Describe any annotation validation processes.
135
+
136
+ #### Who are the annotators?
137
+
138
+ If annotations were collected for the source data (such as class labels or syntactic parses), state whether the annotations were produced by humans or machine generated.
139
+
140
+ Describe the people or systems who originally created the annotations and their selection criteria if applicable.
141
+
142
+ If available, include self-reported demographic or identity information for the annotators, but avoid inferring this information. Instead state that this information is unknown. See [Larson 2017](https://www.aclweb.org/anthology/W17-1601.pdf) for using identity categories as a variables, particularly gender.
143
+
144
+ Describe the conditions under which the data was annotated (for example, if the annotators were crowdworkers, state what platform was used, or if the data was found, what website the data was found on). If compensation was provided, include that information here.
145
+
146
+ ### Personal and Sensitive Information
147
+
148
+ State whether the dataset uses identity categories and, if so, how the information is used. Describe where this information comes from (i.e. self-reporting, collecting from profiles, inferring, etc.). See [Larson 2017](https://www.aclweb.org/anthology/W17-1601.pdf) for using identity categories as a variables, particularly gender. State whether the data is linked to individuals and whether those individuals can be identified in the dataset, either directly or indirectly (i.e., in combination with other data).
149
+
150
+ State whether the dataset contains other data that might be considered sensitive (e.g., data that reveals racial or ethnic origins, sexual orientations, religious beliefs, political opinions or union memberships, or locations; financial or health data; biometric or genetic data; forms of government identification, such as social security numbers; criminal history).
151
+
152
+ If efforts were made to anonymize the data, describe the anonymization process.
153
+
154
+ ## Considerations for Using the Data
155
+
156
+ ### Social Impact of Dataset
157
+
158
+ Please discuss some of the ways you believe the use of this dataset will impact society.
159
+
160
+ The statement should include both positive outlooks, such as outlining how technologies developed through its use may improve people's lives, and discuss the accompanying risks. These risks may range from making important decisions more opaque to people who are affected by the technology, to reinforcing existing harmful biases (whose specifics should be discussed in the next section), among other considerations.
161
+
162
+ Also describe in this section if the proposed dataset contains a low-resource or under-represented language. If this is the case or if this task has any impact on underserved communities, please elaborate here.
163
+
164
+ ### Discussion of Biases
165
+
166
+ Provide descriptions of specific biases that are likely to be reflected in the data, and state whether any steps were taken to reduce their impact.
167
+
168
+ For Wikipedia text, see for example [Dinan et al 2020 on biases in Wikipedia (esp. Table 1)](https://arxiv.org/abs/2005.00614), or [Blodgett et al 2020](https://www.aclweb.org/anthology/2020.acl-main.485/) for a more general discussion of the topic.
169
+
170
+ If analyses have been run quantifying these biases, please add brief summaries and links to the studies here.
171
+
172
+ ### Other Known Limitations
173
+
174
+ If studies of the datasets have outlined other limitations of the dataset, such as annotation artifacts, please outline and cite them here.
175
+
176
+ ## Additional Information
177
+
178
+ ### Dataset Curators
179
+
180
+ List the people involved in collecting the dataset and their affiliation(s). If funding information is known, include it here.
181
+
182
+ ### Licensing Information
183
+
184
+ Provide the license and link to the license webpage if available.
185
+
186
+ ### Citation Information
187
+
188
+ Provide the [BibTex](http://www.bibtex.org/)-formatted reference for the dataset. For example:
189
+ ```
190
+ @article{article_id,
191
+ author = {Author List},
192
+ title = {Dataset Paper Title},
193
+ journal = {Publication Venue},
194
+ year = {2525}
195
+ }
196
+ ```
197
+
198
+ If the dataset has a [DOI](https://www.doi.org/), please provide it here.
199
+
200
+ ### Contributions
201
+
202
+ Thanks to [@github-username](https://github.com/<github-username>) for adding this dataset.