|
11 | 11 | "\n",
|
12 | 12 | "See the the API reference documentation for the module [here](https://developers.arcgis.com/python/latest/api-reference/arcgis.gis.toc.html#offlinecontentmanager).\n",
|
13 | 13 | "\n",
|
14 |
| - "The module is compact, and an object of the `OfflineContentManager` class can be accessed through the [`offline`](/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.ContentManager.offline) property of a [ContentManager]([GIS](/python/latest/api-reference/arcgis.gis.toc.html#contentmanager) object: `gis.content.offline`. It consists of 3 methods: \n", |
| 14 | + "The module is compact, and an object of the `OfflineContentManager` class can be accessed through the [`offline`](/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.ContentManager.offline) property of a [ContentManager](/python/latest/api-reference/arcgis.gis.toc.html#contentmanager) object: `gis.content.offline`. It consists of 3 methods: \n", |
15 | 15 | "* [`export_items()`](/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.OfflineContentManager.export_items) - to export item content to a package\n",
|
16 | 16 | "* [`import_content()`](/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.OfflineContentManager.import_content) - one to import package content \n",
|
17 | 17 | "* [`list_items()`](/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.OfflineContentManager.list_items) - to explore the content of a compressed backup.\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",
|
25 |
| - "There are a few situations where it may be advantageous to use this module instead of `clone_items()`. Creating a singular backup to use from a source org can avoid repeated calls to `clone_items()` in cases where content is being brought to multiple different GIS orgs. Additionally, creating backup packages provides safety against unexpected changes to an organiztion's content. Another notable difference between the OCM and `clone_items()` is that the `import_content()` method provides the option to skip over items that aren't recreated correctly, as opposed to rolling everything back like `clone_items()` does.\n", |
| 25 | + "There are a few situations where it may be advantageous to use this module instead of `clone_items()`. Creating a singular backup to use from a source org can avoid repeated calls to `clone_items()` in cases where content is being brought to multiple different GIS orgs. Additionally, creating backup packages provides safety against unexpected changes to an organization's content. Another notable difference between the OCM and `clone_items()` is that the `import_content()` method provides the option to skip over items that aren't recreated correctly, as opposed to rolling everything back like `clone_items()` does.\n", |
26 | 26 | "\n",
|
27 | 27 | "Let's take a look at its basic usage, and then a couple more specific use cases."
|
28 | 28 | ]
|
|
350 | 350 | "name": "python",
|
351 | 351 | "nbconvert_exporter": "python",
|
352 | 352 | "pygments_lexer": "ipython3",
|
353 |
| - "version": "3.11.10" |
| 353 | + "version": "3.13.2" |
354 | 354 | }
|
355 | 355 | },
|
356 | 356 | "nbformat": 4,
|
|
0 commit comments