You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: argilla/docs/how_to_guides/migrate_from_legacy_datasets.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Migrate your legacy datasets to Argilla V2
2
2
3
-
This guide will help you migrate task specific datasets to Argilla V2. These do not include the `FeedbackDataset` which is just an interim naming convention for the latest extensible dataset. Task specific datasets are datasets that are used for a specific task, such as text classification, token classification, etc. If you would like to learn about the backstory of SDK this migration, please refer to the [SDK migration blog post](https://argilla.io/blog/introducing-argilla-new-sdk/).
3
+
This guide will help you migrate task specific datasets to Argilla V2. These do not include the `FeedbackDataset` which is just an interim naming convention for the latest extensible dataset. Task specific datasets are datasets that are used for a specific task, such as text classification, token classification, etc. If you would like to learn about the backstory of SDK this migration, please refer to the [SDK migration blog post](https://argilla.io/blog/introducing-argilla-new-sdk/).
4
4
5
5
!!! note
6
6
Legacy Datasets include: `DatasetForTextClassification`, `DatasetForTokenClassification`, and `DatasetForText2Text`.
@@ -13,11 +13,11 @@ To follow this guide, you will need to have the following prerequisites:
13
13
- An argilla >=1.29 server instance running. If you don't have one, you can create one by following the [Argilla installation guide](../../getting_started/installation.md).
14
14
- The `argilla` sdk package installed in your environment.
15
15
16
-
If your current legacy datasets are on a server with Argilla release after 1.29, you could chose to recreate your legacy datasets as new datasets on the same server. You could then upgrade the server to Argilla 2.0 and carry on working their. Your legacy datasets will not be visible on the new server, but they will remain in storage layers if you need to access them.
16
+
If your current legacy datasets are on a server with Argilla release after 1.29, you could chose to recreate your legacy datasets as new datasets on the same server. You could then upgrade the server to Argilla 2.0 and carry on working their. Your legacy datasets will not be visible on the new server, but they will remain in storage layers if you need to access them.
17
17
18
18
## Steps
19
19
20
-
The guide will take you through three steps:
20
+
The guide will take you through three steps:
21
21
22
22
1.**Retrieve the legacy dataset** from the Argilla V1 server using the new `argilla` package.
23
23
2.**Define the new dataset** in the Argilla V2 format.
@@ -101,7 +101,7 @@ dataset.create()
101
101
102
102
```python
103
103
dataset = client.datasets(name=dataset_name)
104
-
104
+
105
105
if dataset.exists():
106
106
dataset.delete()
107
107
```
@@ -119,16 +119,16 @@ Here are a set of example functions to convert the records for single-label and
119
119
""" This function maps a text classification record dictionary to the new Argilla record."""
@@ -240,7 +240,7 @@ Here are a set of example functions to convert the records for single-label and
240
240
The functions above depend on the `users_by_name` dictionary and the `current_user` object to assign responses to users, we need to load the existing users. You can retrieve the users from the Argilla V2 server and the current user as follows:
241
241
242
242
```python
243
-
# For
243
+
# For
244
244
users_by_name = {user.username: user for user in client.users}
0 commit comments