|
18 | 18 | "\n",
|
19 | 19 | "The way it works behind the scenes is:\n",
|
20 | 20 | "- In `export_items()`, an [`ItemGraph`](/python/latest/api-reference/arcgis.apps.itemgraph.html#itemgraph) is assembled with all of the items and the items they need to exist\n",
|
21 |
| - "- An output folder is generated, and within that, a folder for each item is created with the necessary data and metadata. Services without an underlying feature class file are exported to either a File Geodatabase or Shapefile, as specified in the export call's `service_format` argument.\n", |
| 21 | + "- An output folder is generated, and within that, a folder for each item is created with the necessary data and metadata. Services without an underlying feature class file are exported to a File Geodatabase by default, or the format specified in the export call's `service_format` argument.\n", |
22 | 22 | "- That output folder is compressed and stored either in the specified path or in a temporary directory\n",
|
23 | 23 | "- On import, the the package is decompressed, the graph is recreated in memory, and the items are created in order from least dependencies to most\n",
|
24 | 24 | "\n",
|
|
319 | 319 | "id": "1415d59e-96b2-4d46-acb4-8bbd8632990f",
|
320 | 320 | "metadata": {},
|
321 | 321 | "source": [
|
322 |
| - "As we can see, it skipped over importing the two failed items and gave us a warning about what happened, but carried out importing the one valid one. However, if we wanted, we could also set `failure_rollback = True`, and it wouldn't have imported anything, just like `clone_items()`." |
| 322 | + "As we can see, it skipped over importing the two failed items and gave us a warning about what happened, but carried out importing the one valid one. However, if we wanted, we could also set `failure_rollback = True`, and it wouldn't have imported anything, just like `clone_items()`.\n", |
| 323 | + "\n", |
| 324 | + "A quick search tells us that those are both errors commonly associated with reading JSON files in Python, meaning that our JSON files within our package are likely corrupted- we could unzip the package with a file explorer and examine them, or examine them in our ArcGIS organization and re-export them. \n", |
| 325 | + "\n", |
| 326 | + "This is just one use case for the `OfflineContentManager`, and there are numerous other advantages to using it. Some other use cases include:\n", |
| 327 | + "- Being able to back up items offline, providing more safety in the event of accidental deletion or changes\n", |
| 328 | + "- Migration between portals, especially in cases where `clone_items()` may encounter an issue\n", |
| 329 | + "- Creating drafts of applications that can be uploaded and edited elsewhere\n", |
| 330 | + "- Migrating from one organization to many- creating one backup prevents going through repeating export logic in `clone_items()`, and speeds up the process by only doing importing\n", |
| 331 | + "- Exporting large sets of hosted feature services to one specific file format\n", |
| 332 | + "\n", |
| 333 | + "Understanding the data you're working with will massively help in mastering this tool. For more resources, please refer to the guides" |
323 | 334 | ]
|
324 | 335 | }
|
325 | 336 | ],
|
|
339 | 350 | "name": "python",
|
340 | 351 | "nbconvert_exporter": "python",
|
341 | 352 | "pygments_lexer": "ipython3",
|
342 |
| - "version": "3.13.2" |
| 353 | + "version": "3.11.10" |
343 | 354 | }
|
344 | 355 | },
|
345 | 356 | "nbformat": 4,
|
|
0 commit comments