Datasets:
Update README.md
Browse files
README.md
CHANGED
@@ -3,10 +3,10 @@ language:
|
|
3 |
- da
|
4 |
license: cc-by-4.0
|
5 |
size_categories:
|
6 |
-
-
|
7 |
task_categories:
|
8 |
- image-to-text
|
9 |
-
pretty_name: Danish Handwritten Text
|
10 |
tags:
|
11 |
- OCR
|
12 |
- HTR
|
@@ -39,18 +39,11 @@ configs:
|
|
39 |
|
40 |
### Dataset Summary
|
41 |
|
42 |
-
The Danish
|
43 |
|
44 |
-
...written by journalists at CNN and the Daily Mail.
|
45 |
...its intended use and the supported tasks. Give an overview of how and why the dataset was created.
|
46 |
...The summary shoul describe the domain, topic, or genre covered.
|
47 |
|
48 |
-
### Supported Tasks and Leaderboards
|
49 |
-
|
50 |
-
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`).
|
51 |
-
|
52 |
-
- `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).
|
53 |
-
|
54 |
### Languages
|
55 |
|
56 |
All the text is in Danish. The BCP-47 code for Danish is da.
|
@@ -59,7 +52,9 @@ All the text is in Danish. The BCP-47 code for Danish is da.
|
|
59 |
|
60 |
### Data Instances
|
61 |
|
62 |
-
Each data instance describes and represents a
|
|
|
|
|
63 |
|
64 |
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.
|
65 |
|
@@ -68,10 +63,8 @@ Provide any additional information that is not covered in the other sections abo
|
|
68 |
List and describe the fields present in the dataset. Mention their data type, and whether they are used as input or output in any of the tasks the dataset currently supports. If the data has span indices, describe their attributes, such as whether they are at the character level or word level, whether they are contiguous or not, etc. If the datasets contains example IDs, state whether they have an inherent meaning, such as a mapping to other datasets or pointing to relationships between data points.
|
69 |
|
70 |
- `image`: a scanned image of the physical page
|
71 |
-
- `authority`: a string identifying the institution that is responsible for the page, the transcription and the proof-reading
|
72 |
- `docId`: an integer representing the unique id of each page
|
73 |
- `docTitle`: a string containing the title of the book/protocol that the page belongs to
|
74 |
-
- `scriptType`: a string classifying the type of text
|
75 |
- `sequence`: description of `example_field`
|
76 |
- `alto`: an xml-encoded string containing layout and content information of the physical page, stored in [ALTO XML, version 4.2](https://www.loc.gov/standards/alto/v4/alto-4-2.xsd)
|
77 |
- `page`: an xml-encoded string containing layout and content information of the physical page, stored in [PAGE XML, version 2013-07-15](https://www.primaresearch.org/schema/PAGE/gts/pagecontent/2013-07-15/pagecontent.xsd)
|
@@ -125,17 +118,13 @@ If annotations were collected for the source data (such as class labels or synta
|
|
125 |
|
126 |
Describe the people or systems who originally created the annotations and their selection criteria if applicable.
|
127 |
|
128 |
-
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.
|
129 |
-
|
130 |
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.
|
131 |
|
132 |
### Personal and Sensitive Information
|
133 |
|
134 |
No efforts were made to anonymize the data.
|
135 |
|
136 |
-
|
137 |
-
|
138 |
-
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).
|
139 |
|
140 |
|
141 |
## Considerations for Using the Data
|
|
|
3 |
- da
|
4 |
license: cc-by-4.0
|
5 |
size_categories:
|
6 |
+
- 1K<n<10K
|
7 |
task_categories:
|
8 |
- image-to-text
|
9 |
+
pretty_name: Danish Handwritten Text 1841-1939
|
10 |
tags:
|
11 |
- OCR
|
12 |
- HTR
|
|
|
39 |
|
40 |
### Dataset Summary
|
41 |
|
42 |
+
The Danish handwriting dataset is a Danish-language dataset containing around 3200 pages of proof-read handwritten text.
|
43 |
|
|
|
44 |
...its intended use and the supported tasks. Give an overview of how and why the dataset was created.
|
45 |
...The summary shoul describe the domain, topic, or genre covered.
|
46 |
|
|
|
|
|
|
|
|
|
|
|
|
|
47 |
### Languages
|
48 |
|
49 |
All the text is in Danish. The BCP-47 code for Danish is da.
|
|
|
52 |
|
53 |
### Data Instances
|
54 |
|
55 |
+
Each data instance describes and represents a single scanned and transcribed physical page with handwritten text.
|
56 |
+
|
57 |
+
contains a scanned image of the of original page, it's date and sequence within a given book or protocol,
|
58 |
|
59 |
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.
|
60 |
|
|
|
63 |
List and describe the fields present in the dataset. Mention their data type, and whether they are used as input or output in any of the tasks the dataset currently supports. If the data has span indices, describe their attributes, such as whether they are at the character level or word level, whether they are contiguous or not, etc. If the datasets contains example IDs, state whether they have an inherent meaning, such as a mapping to other datasets or pointing to relationships between data points.
|
64 |
|
65 |
- `image`: a scanned image of the physical page
|
|
|
66 |
- `docId`: an integer representing the unique id of each page
|
67 |
- `docTitle`: a string containing the title of the book/protocol that the page belongs to
|
|
|
68 |
- `sequence`: description of `example_field`
|
69 |
- `alto`: an xml-encoded string containing layout and content information of the physical page, stored in [ALTO XML, version 4.2](https://www.loc.gov/standards/alto/v4/alto-4-2.xsd)
|
70 |
- `page`: an xml-encoded string containing layout and content information of the physical page, stored in [PAGE XML, version 2013-07-15](https://www.primaresearch.org/schema/PAGE/gts/pagecontent/2013-07-15/pagecontent.xsd)
|
|
|
118 |
|
119 |
Describe the people or systems who originally created the annotations and their selection criteria if applicable.
|
120 |
|
|
|
|
|
121 |
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.
|
122 |
|
123 |
### Personal and Sensitive Information
|
124 |
|
125 |
No efforts were made to anonymize the data.
|
126 |
|
127 |
+
The dataset contains 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).
|
|
|
|
|
128 |
|
129 |
|
130 |
## Considerations for Using the Data
|