Merge remote-tracking branch 'origin/next' into tarun/what-is-geocoding

Author: tarunkukreja003

guide/03-the-gis/working-with-different-authentication-schemes.ipynb

@@ -535,7 +535,7 @@
     "## Storing your credentials locally\n",
     "If you are signing in frequently to a particular GIS and would like to store the credentials locally on your computer, then you could do so using the `profile` parameter of your `GIS`.\n",
     "\n",
-    "Persistent profiles for the GIS can be created by giving the GIS authorization credentials and specifying a profile name. The profile stores all of the authorization credentials (except the password) in the user’s home directory in an unencrypted config file named `.arcgisprofile.` The profile securely stores the password in an O.S. specific password manager through the [keyring](https://pypi.python.org/pypi/keyring) python module. (Note: Linux systems may need additional software installed and configured for proper security) Once a profile has been saved, passing the profile parameter by itself uses the authorization credentials saved in the configuration file/password manager by that profile name. Multiple profiles can be created and used in parallel.\n"
+    "Persistent profiles for the GIS can be created by giving the GIS authorization credentials and specifying a profile name. The profile stores all of the authorization credentials (except the password) in the user’s home directory in an unencrypted config file named `.arcgisprofile.` The profile securely stores the password in an OS specific password manager through the [keyring](https://pypi.python.org/pypi/keyring) python module. (Note: Linux systems may need additional software installed and configured for proper security) Once a profile has been saved, passing the profile parameter by itself uses the authorization credentials saved in the configuration file/password manager by that profile name. Multiple profiles can be created and used in parallel.\n"
    ]
   },
   {

guide/04-feature-data-and-analysis/appending-features.ipynb

@@ -7,11 +7,11 @@
    "source": [
     "# Working with Web Experiences in the Python API\n",
     "\n",
-    "As of version 2.2.0 of the ArcGIS API for Python, users can now work directly with [Experience Builder](https://www.esri.com/en-us/arcgis/products/arcgis-experience-builder/overview) items, enabling some very helpful content management workflows. In this notebook, we'll give an overview of the class and its properties before diving into some handy usage examples.\n",
+    "Users can work directly with [Experience Builder](https://www.esri.com/en-us/arcgis/products/arcgis-experience-builder/overview) items, enabling some very helpful content management workflows. In this notebook, we'll give an overview of the class and its properties before diving into some handy usage examples.\n",
     "\n",
     "## Class Basics\n",
     "\n",
-    "First let's examine a screenshot of the `Web Experience` class help from the API reference:"
+    "First let's examine a screenshot of the [`WebExperience`](/python/api-reference/arcgis.apps.expbuilder.html#webexperience) class help from the API reference:"
    ]
   },
   {
@@ -271,7 +271,7 @@
    "source": [
     "## Cloning an Experience and Validating its Success\n",
     "\n",
-    "Among other changes, 2.2.0 brings in the ability to clone experiences. This can be done both through `gis.content.clone_items()` or through the WebExperience class. We'll show here the helpful extra tools the class has to aid in this workflow."
+    "You can create experiences in one GIS organization and easily move them to another. As with other items, this can be done by using [`gis.content.clone_items()`](/python/api-reference/arcgis.gis.toc.html#arcgis.gis.ContentManager.clone_items). We'll show here the helpful extra tools the class has to aid in this workflow."
    ]
   },
   {
@@ -354,11 +354,11 @@
    ],
    "source": [
     "target = GIS(profile=\"another_online_profile\")\n",
-    "cloned_exp = portal_exp.clone(\n",
-    "    target = target, \n",
-    "    owner = \"another_online_user\",\n",
+    "cloned_list = target.content.clone_items(\n",
+    "    items = [portal_exp],\n",
     "    search_existing_items = False,\n",
     ")\n",
+    "cloned_exp = cloned_list[1]\n",
     "cloned_exp"
    ]
   },
@@ -374,9 +374,7 @@
    "cell_type": "code",
    "execution_count": null,
    "id": "d45bf80a",
-   "metadata": {
-    "scrolled": false
-   },
+   "metadata": {},
    "outputs": [],
    "source": [
     "WebExperience(cloned_exp).view()"
@@ -399,9 +397,9 @@
     "\n",
     "In addition to portal-based experiences, this class allows users to work with locally-based experiences created via the Developer Edition Experience Builder. In the past, users have expressed their desire to add local Experiences to their portals and remap data with ease, in order to cater to workflows such as moving from staging to production environments or migrating content to new Enterprise versions.\n",
     "\n",
-    "We'll show how to get an experience from the Developer Edition Experience Builder, upload it to different portals, and make sure the dependent data items get remapped accordingly. Instructions downloading and installing the Developer Edition can be found [here](https://developers.arcgis.com/experience-builder/guide/install-guide/).\n",
+    "We'll show how to get an experience from the Developer Edition Experience Builder, upload it to different portals, and make sure the dependent data items get remapped accordingly. Instructions downloading and installing the Developer Edition can be found [here](/experience-builder/guide/install-guide/).\n",
     "\n",
-    "First, you'll want to download your experience from the homepage of your local Experience Builder app, and then figure out what the path to the `config.json` file is. Once you know this, you can work with it in the ArcGIS API for Python."
+    "It's easy as just downloading your experience from the Developer Edition interface, and then knowing the path to your the download folder. Within the inner folders, there will be a file named `config.json`- this file contains the structure of your experience, expressed in the exact same way that online experiences are. You can pass in the path to this file to the `upload()` function, or the path to the main project folder in version 2.4.0 or higher."
    ]
   },
   {
@@ -618,7 +616,9 @@
    "id": "b7d49ce9",
    "metadata": {},
    "source": [
-    "As you can see, we can check instantly that our Experience is viewable in the new target GIS, and that the data sources were properly remapped. `dataSource_1` was remapped through `auto_remap`, and `dataSource_4` had its `itemId` and `portalUrl` values changed by `item_mapping`."
+    "As you can see, we can check instantly that our Experience is viewable in the new target GIS, and that the data sources were properly remapped. `dataSource_1` was remapped through `auto_remap`, and `dataSource_4` had its `itemId` and `portalUrl` values changed by `item_mapping`.\n",
+    "\n",
+    "One final note is that as of ArcGIS API for Python version 2.4.0, locally created experiences uploaded to a portal will also copy the experience's image resources as well- so if you have embedded images in your experience, those will get carried over, portrayed in your experience, and stored in the experience item's resources."
    ]
   }
  ],
@@ -638,7 +638,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.17"
+   "version": "3.11.0"
   }
  },
  "nbformat": 4,