Improve registry documentation for new users (#392, #391, #393, #394) (#502)

This commit addresses multiple documentation issues to better support new PDS users:

**Issue #391 - Add links to component documentation:**
- Added link to registry-client external docs from Registry Client section
- Added links from Registry Manager to update_status, delete_data, and create_reg pages
- Added link from Harvest section to load1.html user guide

**Issue #393 - Improve documentation consistency and ordering:**
- Reordered components: Harvest → Registry Manager → Registry Client → OpenSearch → Registry API
- Made Authentication/Authorization a subsection of OpenSearch
- Renamed "API" to "Registry API (PDS Search API)" for clarity and consistency
- Added note about archive status affecting API visibility
- Clarified archive status values with descriptions:
  * archived - publicly visible
  * certified - publicly visible
  * restricted - not publicly visible
  * staged - default, not publicly available
- Fixed inconsistent terminology: changed "uploaded" to "loaded" in load1.rst

**Issue #394 - Update registry-manager documentation:**
- Updated parameter documentation to reflect current CLI (2 required, 2 optional)
- Replaced deprecated -es with -registry parameter
- Updated examples to use new parameter names
- Fixed "registered" to "certified" in Registry API section

These changes improve discoverability and clarity for users new to the PDS Registry system.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: jordanpadams

docs/source/about.rst

@@ -23,33 +23,6 @@ The PDS Registry Application
 The core functionality for the PDS Registry Application is satisfied by `OpenSearch <https://opensearch.org/>`_.
 
 
-API
-----
-
-Provides read-only REST APIs to search and access PDS data. You can call REST APIs directly or
-use Python or Java clients.
-
-The most popular client library is `peppi <https://nasa-pds.github.io/peppi>`_.
-
-For direct access, the API is documented `here <https://nasa-pds.github.io/pds-api/guides/search.html>`_.
-
-
-
-
-OpenSearch
------------
-
-`OpenSearch <https://opensearch.org/>`_ is a NoSQL database based on Apache Lucene project,
-optimized for text search. All metadata extracted from PDS4 labels is stored in the OpenSearch database provided by AWS as `OpenSearch Serverless Managed Service <https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless.html>`_.
-
-
-Authentication/Authorization
------------------------------
-
-The access to the OpenSearch service is restricted using Cognito username and passwords provided by Engineering Node to the other PDS nodes.
-Using their login, discipline node can write in their own OpenSearch indexes and read from all the other indexes.
-
-
 Harvest
 --------
 
@@ -58,15 +31,17 @@ extracted information into OpenSearch.
 
 This command-line tool doesn't require complex installation and configuration.
 
+For more information, see `Loading Data into Registry <./user/load1.html>`_.
+
 
 Registry Manager
 -----------------
 
 A command-line tool to perform admin tasks on a Registry, such as:
 
- * Update product archive status.
- * Delete products.
- * Create or delete registry indices in OpenSearch (by Engineering Node administrators).
+ * `Update product archive status <./user/update_status.html>`_.
+ * `Delete products <./user/delete_data.html>`_.
+ * `Create or delete registry indices in OpenSearch <./admin/create_reg.html>`_ (by Engineering Node administrators).
  * Manage registry data dictionary (by Engineering Node administrators).
 
 
@@ -76,3 +51,30 @@ Registry Client
 
 A command-line tool which provides full access to the OpenSearch API to handle operations not supported by the previous tools.
 The application takes care of the authentication of the user and signs the queries as required by the AWS OpenSearch Serverless Managed Service.
+
+For more information, see the `Registry Client documentation <https://nasa-pds.github.io/registry-client/>`_.
+
+
+OpenSearch
+-----------
+
+`OpenSearch <https://opensearch.org/>`_ is a NoSQL database based on Apache Lucene project,
+optimized for text search. All metadata extracted from PDS4 labels is stored in the OpenSearch database provided by AWS as `OpenSearch Serverless Managed Service <https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless.html>`_.
+
+
+Authentication/Authorization
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The access to the OpenSearch service is restricted using Cognito username and passwords provided by Engineering Node to the other PDS nodes.
+Using their login, discipline node can write in their own OpenSearch indexes and read from all the other indexes.
+
+
+Registry API (PDS Search API)
+------------------------------
+
+Provides read-only REST APIs to search and access PDS data. You can call REST APIs directly or
+use Python or Java clients. The archive status of the data affects its visibility to the Registry API; see `Update Archive Status <./user/update_status.html>`_ for more information.
+
+The most popular client library is `peppi <https://nasa-pds.github.io/peppi>`_.
+
+For direct access, the API is documented `here <https://nasa-pds.github.io/pds-api/guides/search.html>`_.

docs/source/user/load1.rst

@@ -107,7 +107,7 @@ You can see additional harvest options by running:
 
 The harvest job configuration file provides also additional options described in :doc:`/user/harvest_job_configuration`.
 
-You can validate the products uploaded in the registry using `registry-client <https://nasa-pds.github.io/registry-client/>`_.
+You can validate the products loaded in the registry using `registry-client <https://nasa-pds.github.io/registry-client/>`_.
 
 .. warning::
     Due to refresh rates and indexation delays, it may take up to a few hours before the data becomes visible.

docs/source/user/update_status.rst

@@ -10,12 +10,12 @@ When a product is ingested into PDS Registry, its archive status is set to *"sta
 
 You can change that value to any of the following:
 
- * archived
- * certified
- * restricted
- * staged
+ * **archived** - Product has been archived and is publicly visible through the Registry API (PDS Search API).
+ * **certified** - Product has been certified and is publicly visible through the Registry API (PDS Search API).
+ * **restricted** - Product has restricted access and is not publicly visible.
+ * **staged** - Product is ingested but not yet publicly available (default status when ingested).
 
-Status *"archived"* and *"certified"* make the products visible to the public, currently through the PDS Web API.
+Status *"archived"* and *"certified"* make the products visible to the public through the Registry API (PDS Search API).
 
 You can use either Registry Manager or Harvest Client (Scalable Harvest deployments only) for this task.
 
@@ -34,13 +34,16 @@ Set status
 
 To set product archive status, execute Registry Manager's "set-archive-status" command.
 
-The following parameters are required:
+The following parameters are **required**:
 
  * **-status <status>** - New status. Pass one of the following values: "archived", "certified", "restricted", "staged".
  * **-lidvid <id>** - LIDVID of a product to update. If the product is a collection product,
    all primary references from the collection inventory will be also updated.
    If the product is a bundle product, all bundle's collections will be also updated.
- * **-es <url>** - link to the connection configuration file described in :doc:`/connection-setup`
+
+The following parameters are **optional**:
+
+ * **-registry <url>** - URL to the OpenSearch registry endpoint (replaces deprecated -es option). See :doc:`/connection-setup`.
  * **-auth <file>** - OpenSearch authentication configuration file. See :doc:`/connection-setup`.
 
 **Examples:**
@@ -50,7 +53,7 @@ On **MacOS/Linux**:
 .. code-block:: bash
 
    registry-manager set-archive-status \
-       -es file://path/to/registry_connection.xml \
+       -registry https://your-opensearch-endpoint.example.com \
        -auth /my/path/auth.cfg \
        -status archived \
        -lidvid "urn:nasa:pds:kaguya_grs_spectra:document::1.0"
@@ -62,18 +65,18 @@ On **Windows**:
 
     .\registry-manager.bat set-archive-status
         -auth 'C:\Users\loubrieu\Documents\es-auth.txt'
-        -es 'file:///C:\Users\loubrieu\Documents\mcp_dev.xml'
+        -registry 'https://your-opensearch-endpoint.example.com'
         -lidvid 'urn:nasa:pds:insight_rad:data_derived::7.0'
         -status archived
 
 
 
 The connection and auth files are described in :doc:`/connection-setup`
 
-Registry API
-************
+Registry API (PDS Search API)
+******************************
 
-Once data has been ingested and archive status is set to `archived` or `registered`, it is accessible using the Registry
+Once data has been ingested and archive status is set to ``archived`` or ``certified``, it is accessible using the Registry
 API which is `documented here <https://nasa-pds.github.io/pds-api/guides/search.html>`_.
 
 The base URL of the API https://pds.nasa.gov/api/search/1 also provides an online documentation.