From bca437d5d5bb485783dc060a7edf99352cec771b Mon Sep 17 00:00:00 2001 From: mnoszczak Date: Tue, 27 Jun 2023 12:14:15 +0200 Subject: [PATCH] Update docs --- examples/basics/export_data.ipynb | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/examples/basics/export_data.ipynb b/examples/basics/export_data.ipynb index 6f46493f2..8e1c19ad8 100644 --- a/examples/basics/export_data.ipynb +++ b/examples/basics/export_data.ipynb @@ -96,6 +96,7 @@ "- `last_activity_at`\n", "- `label_created_at`\n", "- `data_row_ids`\n", + "- `batch_ids`\n", "\n", "#### Filter details\n", "You can set the range for `last_activity_at` and `label_created_at` in the following formats: \n", @@ -107,7 +108,9 @@ "\n", "The `last_activity_at` filter captures the creation and modification of labels, metadata, workflow status, comments, and reviews.\n", "\n", - "If you wish to specify data rows to export, uncomment the `data_row_ids` filter and provide a list of applicable IDs. The data rows must be part of a batch attached to the project in question. You can provide up to 2,000 data row IDs." + "If you wish to specify data rows to export, uncomment the `data_row_ids` filter and provide a list of applicable IDs. The data rows must be part of a batch attached to the project in question. You can provide up to 2,000 data row IDs.\n", + "\n", + "The `batch_ids` filter allows you to specify data rows for export based on their associated batch ID. This is particularly useful when `data_row_ids` is not sufficient due to 2,000 data row IDs limit. " ], "cell_type": "markdown" }, @@ -140,7 +143,8 @@ "filters= {\n", " \"last_activity_at\": [\"2000-01-01 00:00:00\", \"2050-01-01 00:00:00\"],\n", " \"label_created_at\": [\"2000-01-01 00:00:00\", \"2050-01-01 00:00:00\"],\n", - " # \"data_row_ids\": [\"\", \"\"] \n", + " # \"data_row_ids\": [\"\", \"\"],\n", + " # \"batch_ids\": [\"\", \"\"],\n", "}\n", "\n", "export_task = project.export_v2(params=export_params, filters=filters)\n",