huggingface
diff --git a/‎.github/workflows/build_documentation.yml
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/build_documentation.yml
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/workflows/build_pr_documentation.yml
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/build_pr_documentation.yml
Lines changed: 1 addition & 1 deletion
diff --git a/‎README.md
Lines changed: 1 addition & 1 deletion b/‎README.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎chapters/ar/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion b/‎chapters/ar/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion
diff --git a/‎chapters/bn/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion b/‎chapters/bn/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion
diff --git a/‎chapters/de/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion b/‎chapters/de/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion
diff --git a/‎chapters/de/chapter3/2.mdx
Lines changed: 3 additions & 0 deletions b/‎chapters/de/chapter3/2.mdx
Lines changed: 3 additions & 0 deletions
diff --git a/‎chapters/en/_toctree.yml
Lines changed: 20 additions & 0 deletions b/‎chapters/en/_toctree.yml
Lines changed: 20 additions & 0 deletions
diff --git a/‎chapters/en/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion b/‎chapters/en/chapter0/1.mdx
Lines changed: 1 addition & 1 deletion
diff --git a/‎chapters/en/chapter1/1.mdx
Lines changed: 1 addition & 1 deletion b/‎chapters/en/chapter1/1.mdx
Lines changed: 1 addition & 1 deletion
diff --git a/‎chapters/en/chapter10/1.mdx
Lines changed: 26 additions & 0 deletions b/‎chapters/en/chapter10/1.mdx
Lines changed: 26 additions & 0 deletions
diff --git a/‎chapters/en/chapter10/2.mdx
Lines changed: 55 additions & 0 deletions b/‎chapters/en/chapter10/2.mdx
Lines changed: 55 additions & 0 deletions
diff --git a/‎chapters/en/chapter10/3.mdx
Lines changed: 108 additions & 0 deletions b/‎chapters/en/chapter10/3.mdx
Lines changed: 108 additions & 0 deletions
diff --git a/‎chapters/en/chapter10/4.mdx
Lines changed: 44 additions & 0 deletions b/‎chapters/en/chapter10/4.mdx
Lines changed: 44 additions & 0 deletions
@@ -14,6 +14,6 @@ jobs:
       package: course
       path_to_docs: course/chapters/
       additional_args: --not_python_module
-      languages: ar bn de en es fa fr gj he hi id it ja ko pt ru th tr vi zh-CN zh-TW
+      languages: ar bn de en es fa fr gj he hi id it ja ko ne pt ru rum th tr vi zh-CN zh-TW
     secrets:
       hf_token: ${{ secrets.HF_DOC_BUILD_PUSH }}
@@ -16,4 +16,4 @@ jobs:
       package: course
       path_to_docs: course/chapters/
       additional_args: --not_python_module
-      languages: ar bn de en es fa fr gj he hi id it ja ko pt ru th tr vi zh-CN zh-TW
+      languages: ar bn de en es fa fr gj he hi id it ja ko ne pt ru rum th tr vi zh-CN zh-TW
@@ -110,7 +110,7 @@ pip install -r requirements.txt
 make style
 ```
 
-Once that's run, commit any changes, open a pull request, and tag [@lewtun](https://github.com/lewtun) for a review. Congratulations, you've now completed your first translation 🥳!
+Once that's run, commit any changes, open a pull request, and tag [@lewtun](https://github.com/lewtun) and [@stevhliu](https://github.com/stevhliu) for a review. If you also know other native-language speakers who are able to review the translation, tag them as well for help. Congratulations, you've now completed your first translation 🥳!
 
 > 🚨 To build the course on the website, double-check your language code exists in `languages` field of the `build_documentation.yml` and `build_pr_documentation.yml` files in the `.github` folder. If not, just add them in their alphabetical order.
 
 
@@ -105,7 +105,7 @@ ls -a
 source .env/bin/activate
 
 # Deactivate the virtual environment
-source .env/bin/deactivate
+deactivate
 ```
 
 <div dir="rtl" style="direction:rtl;text-align:right;">
 
@@ -87,7 +87,7 @@ ls -a
 source .env/bin/activate
 
 # virtual environment টি deactivate করার কমান্ড
-source .env/bin/deactivate
+deactivate
 ```
 
 `which python` কমান্ড চালিয়ে নিশ্চিত করতে পারেন যে  virtual environment টি activate হয়েছে কিনা। 
 
@@ -86,7 +86,7 @@ Mit den Skripten "activate" und "deactivate" kannst du in deine virtuelle Umgebu
 source .env/bin/activate
 
 # Deaktivieren der virtuellen Umgebung
-source .env/bin/deactivate
+deactivate
 ```
 
 Du kannst dich vergewissern, dass die Umgebung aktiviert ist, indem du den Befehl `which python` ausführst: Wenn er auf die virtuelle Umgebung verweist, dann hast du sie erfolgreich aktiviert!
 
@@ -87,6 +87,9 @@ In diesem Abschnitt verwenden wir den MRPC-Datensatz (Microsoft Research Paraphr
 Das Hub enthält nicht nur Modelle; Es hat auch mehrere Datensätze in vielen verschiedenen Sprachen. Du kannst die Datensätze [hier](https://huggingface.co/datasets) durchsuchen, und wir empfehlen, einen weiteren Datensatz zu laden und zu verarbeiten, sobald Sie diesen Abschnitt abgeschlossen haben (die Dokumentation befindet sich [hier](https://huggingface.co/docs/datasets/loading)). Aber jetzt konzentrieren wir uns auf den MRPC-Datensatz! Dies ist einer der 10 Datensätze, aus denen sich das [GLUE-Benchmark](https://gluebenchmark.com/) zusammensetzt. Dies ist ein akademisches Benchmark, das verwendet wird, um die Performance von ML-Modellen in 10 verschiedenen Textklassifizierungsaufgaben zu messen.
 
 Die Bibliothek 🤗 Datasets bietet einen leichten Befehl zum Herunterladen und Caching eines Datensatzes aus dem Hub. Wir können den MRPC-Datensatz wie folgt herunterladen:
+<Tipp>
+⚠️ ** Warnung** Stelle sicher, dass `datasets` installiert ist, indem du `pip install datasets` ausführst. Dann lade den MRPC-Datensatz und drucke ihn aus, um zu sehen, was er enthält.
+</Tipp>
 
 ```py
 from datasets import load_dataset
 
@@ -191,6 +191,26 @@
     title: End-of-chapter quiz
     quiz: 9
 
+- title: 10. Curate high-quality datasets
+  new: true
+  subtitle: How to use Argilla to create amazing datasets
+  sections:
+  - local: chapter10/1
+    title: Introduction to Argilla
+  - local: chapter10/2
+    title: Set up your Argilla instance
+  - local: chapter10/3
+    title: Load your dataset to Argilla
+  - local: chapter10/4
+    title: Annotate your dataset
+  - local: chapter10/5
+    title: Use your annotated dataset
+  - local: chapter10/6
+    title: Argilla, check!
+  - local: chapter10/7
+    title: End-of-chapter quiz
+    quiz: 10
+
 - title: Course Events
   sections:
   - local: events/1
 
@@ -86,7 +86,7 @@ You can jump in and out of your virtual environment with the `activate` and `dea
 source .env/bin/activate
 
 # Deactivate the virtual environment
-source .env/bin/deactivate
+deactivate
 ```
 
 You can make sure that the environment is activated by running the `which python` command: if it points to the virtual environment, then you have successfully activated it!
 
@@ -23,7 +23,7 @@ Here is a brief overview of the course:
 
 - Chapters 1 to 4 provide an introduction to the main concepts of the 🤗 Transformers library. By the end of this part of the course, you will be familiar with how Transformer models work and will know how to use a model from the [Hugging Face Hub](https://huggingface.co/models), fine-tune it on a dataset, and share your results on the Hub!
 - Chapters 5 to 8 teach the basics of 🤗 Datasets and 🤗 Tokenizers before diving into classic NLP tasks. By the end of this part, you will be able to tackle the most common NLP problems by yourself.
-- Chapters 9 to 12 go beyond NLP, and explore how Transformer models can be used to tackle tasks in speech processing and computer vision. Along the way, you'll learn how to build and share demos of your models, and optimize them for production environments. By the end of this part, you will be ready to apply 🤗 Transformers to (almost) any machine learning problem!
+- Chapter 9 goes beyond NLP to cover how to build and share demos of your models on the 🤗 Hub. By the end of this part, you will be ready to showcase your 🤗 Transformers application to the world!
 
 This course:
 
 
@@ -0,0 +1,26 @@
+# Introduction to Argilla[[introduction-to-argilla]]
+
+<CourseFloatingBanner
+    chapter={10}
+    classNames="absolute z-10 right-0 top-0"
+/>
+
+In Chapter 5 you learnt how to build a dataset using the 🤗 Datasets library and in Chapter 6 you explored how to fine-tune models for some common NLP tasks. In this chapter, you will learn how to use [Argilla](https://argilla.io) to **annotate and curate datasets** that you can use to train and evaluate your models.
+
+The key to training models that perform well is to have high-quality data. Although there are some good datasets in the Hub that you could use to train and evaluate your models, these may not be relevant for your specific application or use case. In this scenario, you may want to build and curate a dataset of your own. Argilla will help you to do this efficiently.
+
+<img src="https://huggingface.co/datasets/huggingface-course/documentation-images/resolve/main/en/chapter10/signin-hf-page.png" alt="Argilla sign in page."/>
+
+With Argilla you can:
+
+- turn unstructured data into **structured data** to be used in NLP tasks.
+- curate a dataset to go from a low-quality dataset to a **high-quality dataset**.
+- gather **human feedback** for LLMs and multi-modal models.
+- invite experts to collaborate with you in Argilla, or crowdsource annotations!
+
+Here are some of the things that you will learn in this chapter:
+
+- How to set up your own Argilla instance.
+- How to load a dataset and configure it based on some popular NLP tasks.
+- How to use the Argilla UI to annotate your dataset.
+- How to use your curated dataset and export it to the Hub.
@@ -0,0 +1,55 @@
+# Set up your Argilla instance[[set-up-your-argilla-instance]]
+
+<CourseFloatingBanner chapter={10}
+  classNames="absolute z-10 right-0 top-0"
+  notebooks={[
+    {label: "Google Colab", value: "https://colab.research.google.com/github/huggingface/notebooks/blob/master/course/en/chapter10/section2.ipynb"},
+    {label: "Aws Studio", value: "https://studiolab.sagemaker.aws/import/github/huggingface/notebooks/blob/master/course/en/chapter10/section2.ipynb"},
+]} />
+
+To start using Argilla, you will need to set up your own Argilla instance first. Then you will need to install the Python SDK so that you can manage Argilla using Python code.
+
+## Deploy the Argilla UI
+
+The easiest way to set up your Argilla instance is through Hugging Face Spaces. To create your Argilla Space, simply follow [this form](https://huggingface.co/new-space?template=argilla%2Fargilla-template-space). If you need further guidance, check the [Argilla quickstart](https://docs.argilla.io/latest/getting_started/quickstart/).
+<img src="https://huggingface.co/datasets/huggingface-course/documentation-images/resolve/main/en/chapter10/space_config.png" alt="Space configuration form."/>
+
+>[!WARNING]
+> ⚠️ You may want to enable **Persistent storage** so the data isn't lost if the Space is paused or restarted.
+> You can do that from the Settings of your Space.
+
+Once Argilla is up and running, you can log in with your credentials.
+
+## Install and connect the Python SDK
+
+Now you can go to your Python environment or notebook and install the argilla library:
+
+`!pip install argilla`
+
+Let's connect with our Argilla instance. To do that you will need the following information:
+
+- **Your API URL**: This is the URL where Argilla is running. If you are using a Space, you can open the Space, click on the three dots in the top right corner, then "Embed this Space" and copy the **Direct URL**. It should look something like `https://<your-username>.<space-name>.hf.space`.
+- **Your API key**: To get your key, log in to your Argilla instance and go to "My Settings", then copy the API key.
+- **Your HF token**: If your Space is private, you will need to an Access Token in your Hugging Face Hub account with writing permissions.
+
+```python
+import argilla as rg
+
+HF_TOKEN = "..."  # only for private spaces
+
+client = rg.Argilla(
+    api_url="...",
+    api_key="...",
+    headers={"Authorization": f"Bearer {HF_TOKEN}"},  # only for private spaces
+)
+```
+
+To check that everything is working properly, we'll call `me`. This should return our user:
+
+```python
+client.me
+```
+
+If this worked, your Argilla instance is up and running and you're connected to it! Congrats!
+
+We can now get started with loading our first dataset to Argilla.
@@ -0,0 +1,108 @@
+# Load your dataset to Argilla[[load-your-dataset-to-argilla]]
+
+<CourseFloatingBanner chapter={10}
+  classNames="absolute z-10 right-0 top-0"
+  notebooks={[
+    {label: "Google Colab", value: "https://colab.research.google.com/github/huggingface/notebooks/blob/master/course/en/chapter10/section3.ipynb"},
+    {label: "Aws Studio", value: "https://studiolab.sagemaker.aws/import/github/huggingface/notebooks/blob/master/course/en/chapter10/section3.ipynb"},
+]} />
+
+Depending on the NLP task that you're working with and the specific use case or application, your data and the annotation task will look differently. For this section of the course, we'll use [a dataset collecting news](https://huggingface.co/datasets/SetFit/ag_news) to complete two tasks: a text classification on the topic of each text and a token classification to identify the named entities mentioned.
+
+<iframe
+  src="https://huggingface.co/datasets/SetFit/ag_news/embed/viewer/default/train"
+  frameborder="0"
+  width="100%"
+  height="560px"
+></iframe>
+
+It is possible to import datasets from the Hub using the Argilla UI directly, but we'll be using the SDK to learn how we can make further edits to the data if needed.
+
+## Configure your dataset
+
+The first step is to connect to our Argilla instance as we did in the previous section:
+
+```python
+import argilla as rg
+
+HF_TOKEN = "..."  # only for private spaces
+
+client = rg.Argilla(
+    api_url="...",
+    api_key="...",
+    headers={"Authorization": f"Bearer {HF_TOKEN}"},  # only for private spaces
+)
+```
+
+We can now think about the settings of our dataset in Argilla. These represent the annotation task we'll do over our data. First, we can load the dataset from the Hub and inspect its features, so that we can make sure that we configure the dataset correctly.
+
+```python
+from datasets import load_dataset
+
+data = load_dataset("SetFit/ag_news", split="train")
+data.features
+```
+
+These are the features of our dataset:
+
+```python out
+{'text': Value(dtype='string', id=None),
+ 'label': Value(dtype='int64', id=None),
+ 'label_text': Value(dtype='string', id=None)}
+```
+
+It contains a `text` and also some initial labels for the text classification. We'll add those to our dataset settings together with a `spans` question for the named entities:
+
+```python
+settings = rg.Settings(
+    fields=[rg.TextField(name="text")],
+    questions=[
+        rg.LabelQuestion(
+            name="label", title="Classify the text:", labels=data.unique("label_text")
+        ),
+        rg.SpanQuestion(
+            name="entities",
+            title="Highlight all the entities in the text:",
+            labels=["PERSON", "ORG", "LOC", "EVENT"],
+            field="text",
+        ),
+    ],
+)
+```
+
+Let's dive a bit deeper into what these settings mean. First, we've defined **fields**, these include the information that we'll be annotating. In this case, we only have one field and it comes in the form of a text, so we've choosen a `TextField`.
+
+Then, we define **questions** that represent the tasks that we want to perform on our data:
+
+- For the text classification task we've chosen a `LabelQuestion` and we used the unique values of the `label_text` column as our labels, to make sure that the question is compatible with the labels that already exist in the dataset.
+- For the token classification task, we'll need a `SpanQuestion`. We've defined a set of labels that we'll be using for that task, plus the field on which we'll be drawing the spans.
+
+To learn more about all the available types of fields and questions and other advanced settings, like metadata and vectors, go to the [Argilla docs](https://docs.argilla.io/latest/how_to_guides/dataset/#define-dataset-settings).
+
+## Upload the dataset
+
+Now that we've defined some settings, we can create the dataset:
+
+```python
+dataset = rg.Dataset(name="ag_news", settings=settings)
+
+dataset.create()
+```
+
+The dataset now appears in our Argilla instance, but you will see that it's empty:
+
+<img src="https://huggingface.co/datasets/huggingface-course/documentation-images/resolve/main/en/chapter10/empty_dataset.png" alt="Screenshot of the empty dataset."/>
+
+Now we need to add the records that we'll be annotating i.e., the rows in our dataset. To do that, we'll simply need to log the data as records and provide a mapping for those elements that don't have the same name in the hub and Argilla datasets:
+
+```python
+dataset.records.log(data, mapping={"label_text": "label"})
+```
+
+In our mapping, we've specified that the `label_text` column in the dataset should be mapped to the question with the name `label`. In this way, we'll use the existing labels in the dataset as pre-annotations so we can annotate faster.
+
+While the the records continue to log, you can already start working with your dataset in the Argilla UI. At this point, it should look like this:
+
+<img src="https://huggingface.co/datasets/huggingface-course/documentation-images/resolve/main/en/chapter10/argilla_initial_dataset.png" alt="Screenshot of the dataset in Argilla."/>
+
+Now our dataset is ready to start annotating!
@@ -0,0 +1,44 @@
+# Annotate your dataset[[annotate-your-dataset]]
+
+<CourseFloatingBanner
+    chapter={10}
+    classNames="absolute z-10 right-0 top-0"
+/>
+
+Now it is time to start working from the Argilla UI to annotate our dataset. 
+
+## Align your team with annotation guidelines
+
+Before you start annotating your dataset, it is always good practice to write some guidelines, especially if you're working as part of a team. This will help you align on the task and the use of the different labels, and resolve questions or conflicts when they come up.
+
+In Argilla, you can go to your dataset settings page in the UI and modify the guidelines and the descriptions of your questions to help with alignment.
+
+<img src="https://huggingface.co/datasets/huggingface-course/documentation-images/resolve/main/en/chapter10/argilla_dataset_settings.png" alt="Screenshot of the Dataset Settings page in Argilla."/>
+
+If you want to dive deeper into the topic of how to write good guidelines, we recommend reading [this blogpost](https://argilla.io/blog/annotation-guidelines-practices) and the bibliographical references mentioned there.
+
+## Distribute the task
+
+In the dataset settings page, you can also change the dataset distribution settings. This will help you annotate more efficiently when you're working as part of a team. The default value for the minimum submitted responses is 1, meaning that as soon as a record has 1 submitted response it will be considered complete and count towards the progress in your dataset.
+
+Sometimes, you want to have more than one submitted response per record, for example, if you want to analyze the inter-annotator agreement in your task. In that case, make sure to change this setting to a higher number, but always smaller or equal to the total number of annotators. If you're working on the task alone, you want this setting to be 1.
+
+## Annotate records
+
+>[!TIP]
+>💡 If you are deploying Argilla in a Hugging Face Space, any team members will be able to log in using the Hugging Face OAuth. Otherwise, you may need to create users for them following [this guide](https://docs.argilla.io/latest/how_to_guides/user/).
+
+When you open your dataset, you will realize that the first question is already filled in with some suggested labels. That's because in the previous section we mapped our question called `label` to the `label_text` column in the dataset, so that we simply need to review and correct the already existing labels:
+
+<img src="https://huggingface.co/datasets/huggingface-course/documentation-images/resolve/main/en/chapter10/argilla_initial_dataset.png" alt="Screenshot of the dataset in Argilla."/>
+
+For the token classification, we'll need to add all labels manually, as we didn't include any suggestions. This is how it might look after the span annotations:
+
+<img src="https://huggingface.co/datasets/huggingface-course/documentation-images/resolve/main/en/chapter10/argilla_dataset_with_spans.png" alt="Screenshot of the dataset in Argilla with spans annotated."/>
+
+As you move through the different records, there are different actions you can take: 
+- submit your responses, once you're done with the record.
+- save them as a draft, in case you want to come back to them later.
+- discard them, if the record souldn't be part of the dataset or you won't give responses to it.
+
+In the next section, you will learn how you can export and use those annotations.