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: ckan-backend-dev/src/ckanext-wri/README.md
+13-16
Original file line number
Diff line number
Diff line change
@@ -241,8 +241,7 @@ Migrates an RW dataset/metadata to CKAN. It maps all supported RW fields to CKAN
241
241
242
242
**Parameters:**
243
243
-**rw_dataset_id** (string) – The RW UUID of the dataset to migrate (required—unless `gfw_dataset` is provided). Example: `c0b5f4b1-4f3b-4f1e-8f1e-3f4b1f3b4f1e`.
244
-
-**rw_application** (string) – The RW application of the dataset to migrate (required). Example: `rw`.
245
-
-**dx_application** (string) – The destination DX application name (group name) to associate the dataset with (required). Example: `land-carbon-lab`.
244
+
-**application** (string) – The RW application of the dataset to migrate (required). Example: `rw`.
246
245
-**dataset_slug** (string) – The desired slug of the dataset to migrate (optional). If you use this option, you will need to include this parameter each time you call `migrate_dataset` for this dataset. This value will override the `slug` value from the RW/GFW APIs. Example: `my-dataset`.
247
246
-**dataset_title** (string) – The desired title of the dataset to migrate (optional). If you use this option, you will need to include this parameter each time you call `migrate_dataset` for this dataset. This value will override the `name` value from the RW API or the `title` value from the GFW API. Example: `My Dataset`.
248
247
-**gfw_dataset** (string) – The GFW dataset to migrate (optional). If this dataset also has metadata in the RW API, you should also include `rw_dataset_id`. Example: `gfw_forest_data`.
@@ -261,7 +260,7 @@ A successful request will return the Prefect status of the new migration job.
@@ -284,8 +283,7 @@ A successful request will return the Prefect status of the new migration job.
284
283
"lucas-topic",
285
284
"nov-16-topic"
286
285
],
287
-
"rw_application": "rw",
288
-
"dx_application": "land-carbon-lab"
286
+
"application": "rw"
289
287
}
290
288
},
291
289
"idempotency_key": null,
@@ -445,8 +443,7 @@ You'll need this ID: `"id": "7cd8a09e-1834-4ab5-8b72-bd638e9392ae"` (`result.id`
445
443
Add a custom file to the `migration/files` directory and commit it to the repo. Once deployed, you can use the `file_name` parameter to specify it. The file should be a CSV with the following columns:
446
444
447
445
-`rw_dataset_id` (required—unless `gfw_dataset` is provided)
448
-
-`rw_application` (required)
449
-
-`dx_application` (required)
446
+
-`application` (required)
450
447
-`team` (optional)
451
448
-`topics` (optional)
452
449
-`geographic_coverage` (optional)
@@ -464,13 +461,14 @@ Add a custom file to the `migration/files` directory and commit it to the repo.
,gfw_forest_flux_removal_forest_type,gfw,global-forest-watch,"land,ghg-emissions,forest",,Jane Smith:[email protected],John Smith:[email protected],,Another Title Example,
0 commit comments