feat(auto): added link to the derivative repo

README.md

@@ -20,26 +20,26 @@ task_categories:
 dataset_info:
   - config_name: written
     features:
-      - name: threads
+      - name: title
+        dtype: string
+      - name: topics
         sequence:
-          - name: topics
+          - name: posts
             sequence:
-              - name: posts
-                sequence:
-                  - name: text
-                    dtype: string
+              - name: text
+                dtype: string
   - config_name: spoken
     features:
-      - name: threads
+      - name: title
+        dtype: string
+      - name: speech
+        dtype: audio
+      - name: topics
         sequence:
-          - name: topics
+          - name: posts
             sequence:
-              - name: posts
-                sequence:
-                  - name: text
-                    dtype: string
-                  - name: speech
-                    dtype: audio
+              - name: text
+                dtype: string
 ---
 
 <p align="center">
@@ -65,7 +65,7 @@ dataset_info:
 
 ### Dataset summary
 
-This dataset contains threads parsed from the `/b/` board of [2ch archive][archive].
+This dataset contains threads parsed from the `/b/` board of [2ch archive][archive]. See dataset viewer at the [derivative repo](/datasets/zeio/auto-batch).
 
 ## Dataset structure
 
@@ -133,6 +133,6 @@ Therefore, this dataset entry can be represented in json in the following format
 ### Dataset fields
 
 In `written` configuration the dataset is represented as a list of `Thread` objects, each `Thread` has a single property `topics`, which contains a list of `Topic` objects. Each `Topic` object has a single property `posts`, which points to the list of `Post` objects, making up the `Topic`. Each `Post` object contains a single property `text` which contains text representation of the post (essentially `text` is `html` code without `tags` and explicit links to other posts; there may still be implicit links to other posts in a form of quotes, prefixed with `>` symbol).  
-In `spoken` configuration the structure is basically the same, but some `Post` objects have and additional property `speech` with a spoken representation of the post.
+In `spoken` configuration the structure is basically the same, but some `Thread` objects have and additional property `speech` with a spoken representation of the thread.
 
 [archive]: https://2ch.hk/b/arch/