link to Croissant JARs, suggest dir for exporters #10341

pdurbin · pdurbin · commit 87c0f58420e7 · 2024-04-30T14:22:59.000-04:00
diff --git a/doc/sphinx-guides/source/installation/advanced.rst b/doc/sphinx-guides/source/installation/advanced.rst
@@ -145,9 +145,12 @@ Croissant (``croissant``)
 
 `Croissant <https://github.com/mlcommons/croissant>`_ is oriented toward machine learning and exposes variable-level metadata. When enabled, it replaces the Schema.org JSON-LD shown in the ``<head>`` of a dataset page, as described under :ref:`schema.org-head` in the Admin Guide.
 
-You can download the Croissant exporter JAR from FIXME.
+You can download the Croissant exporter JAR from the following locations:
 
-The source can be found in the `"croissant" <https://github.com/gdcc/dataverse-exporters/tree/main/croissant>`_ directory of the exporters repo.
+- released/stable: https://repo1.maven.org/maven2/io/gdcc/croissant/
+- unreleased/snapshot: https://s01.oss.sonatype.org/content/groups/staging/io/gdcc/croissant/
+
+The source and additional information can be found in the `"croissant" <https://github.com/gdcc/dataverse-exporters/tree/main/croissant>`_ directory of the exporters repo.
 
 MyJSON (``dataverse_json``)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/doc/sphinx-guides/source/installation/config.rst b/doc/sphinx-guides/source/installation/config.rst
@@ -3111,9 +3111,9 @@ dataverse.spi.exporters.directory
 
 For some background, see :ref:`external-exporters` and :ref:`inventory-of-external-exporters`.
 
-This JVM option is used to configure the file system path where external exporter JARs should be loaded from.
+This JVM option is used to configure the file system path where external exporter JARs should be loaded from. For example:
 
-``./asadmin create-jvm-options '-Ddataverse.spi.exporters.directory=PATH_LOCATION_HERE'``
+``./asadmin create-jvm-options '-Ddataverse.spi.exporters.directory=/var/lib/dataverse/exporters'``
 
 If this value is set, Dataverse will examine all JARs in the specified directory and will use them to add new metadata export formats or (if the machine-readable name used in :ref:`export-dataset-metadata-api` is the same) replace built-in metatadata export formats.
 
