🚸 Make use of new VitessceConfig interface (#24)

docs/vitessce.ipynb

@@ -35,7 +35,7 @@
    },
    "outputs": [],
    "source": [
-    "# !pip install vitessce\n",
+    "# !pip install vitessce>=0.3.4\n",
     "# !pip install 'lamindb[jupyter,aws,bionty]'\n",
     "!lamin load laminlabs/lamin-dev  # <-- replace with your instance"
    ]
@@ -162,7 +162,7 @@
     ")\n",
     "dataset = vc.add_dataset(name=\"Habib 2017\").add_object(\n",
     "    vit.AnnDataWrapper(\n",
-    "        adata_url=zarr_artifact.path.to_url(),\n",
+    "        adata_artifact=zarr_artifact,\n",
     "        obs_feature_matrix_path=\"layers/X_uint8\",\n",
     "        obs_embedding_paths=[\"obsm/X_umap\"],\n",
     "        obs_embedding_names=[\"UMAP\"],\n",
@@ -208,6 +208,8 @@
     "\n",
     "You can now see the Vitessce button show up on your dataset as in this [example dataset](https://lamin.ai/laminlabs/lamindata/artifact/HXJ4DDAw8012jVKwoxgd).\n",
     "\n",
+    "If your `VitessceConfig` object contains multiple datasets, the Vitessce button will appear next to a `Collection` that groups these artifacts.\n",
+    "\n",
     ":::"
    ]
   },
@@ -236,7 +238,7 @@
    "source": [
     ":::{dropdown} Upload speed\n",
     "\n",
-    "Here is [a note](https://lamin.ai/laminlabs/lamindata/transform/WDjio16cQsdW5zKv) on folder upload speed and we why chose not to use the `.export(to=\"s3\")` functionality of Vitessce.\n",
+    "Here is [a note](https://lamin.ai/laminlabs/lamindata/transform/WDjio16cQsdW5zKv) on folder upload speed and why `lamindb` does not use the `.export(to=\"s3\")` functionality of Vitessce.\n",
     "\n",
     ":::"
    ]