Merge pull request #174 from ESA-APEx/rename-catalogue

chore: renamed APEx Algorithm Services Catalogue

Author: JanssenBrm

_quarto.yml

@@ -82,7 +82,7 @@ website:
                     text: Ingesting STAC metadata in APEx Product Catalogue
                   - href: guides/catalog_openeo.ipynb
                     text: Linking APEx Product Catalogue with an openEO service
-              - section: APEx Algorithm Services Catalogue
+              - section: APEx Algorithm Catalogue
                 contents:
                   - href: guides/algorithm_services_catalogue.qmd
                   - href: guides/algorithm_services_catalogue_benchmarks.qmd

eo_service_usage/openeo_usage.md

@@ -2,36 +2,43 @@
 title: openEO based services
 ---
 
-Context: use of APEx services that expose the [openEO](https://openeo.org/) interface standard, when implemented as openEO processes.
+Context: use of APEx services that expose the [openEO](https://openeo.org/) interface standard, when implemented as openEO
+processes.
 
+In general, services can be executed through the tools that are provided by the APEx supported platforms ("processing platforms"
+hereafter).
+For OpenEO based services, this is supported by an online user interface, web editor, Client Libraries (JavaScript, Python,
+R) and API.
 
-In general, services can be executed through the tools that are provided by the APEx supported platforms ("processing platforms" hereafter).
-For OpenEO based services, this is supported by an online user interface, web editor, Client Libraries (JavaScript, Python, R) and API.
+There are several ways to discover how a service can be executed. When publishing a service on the
+[APEx Algorithm Catalogue](../guides/algorithm_services_catalogue.qmd), a service provider can choose to provide the
+following information in the service details:
 
-There are several ways to discover how a service can be executed. When publishing a service on the APEx Algorithm Services Catalogue, a service provider can choose to provide the following information in the service details:
-
-* An executable link which redirects the user to the user interface of the processing platform. If this is the case, an **Access app** button will appear when opening an EOplaza service.
+* An executable link which redirects the user to the user interface of the processing platform. If this is the case, an
+**Access app** button will appear when opening an EOplaza service.
 * Sample code in the service description on how to execute a service.
 
 ## openEO backends
 
 An APEx openEO service is always associated with one or more openEO backends that have been validated to produce the correct
 results. So using one of these backends is the recommended approach. Thanks to openEO interoperability and standardization,
-it may certainly be possible that other backends can run the same service, but do make sure to validate the results in that case.
+it may certainly be possible that other backends can run the same service, but do make sure to validate the results in
+that case.
 
 To ensure a smooth experience, backends need to be compliant with [APEx guidelines](../interoperability/algohostingenv.md).
 The currently known list of compliant backends is:
 
-- [CDSE openEO federation](https://openeofed.dataspace.copernicus.eu)
-- [openEO platform](https://openeo.cloud)
+* [CDSE openEO federation](https://openeofed.dataspace.copernicus.eu)
+* [openEO platform](https://openeo.cloud)
 
 Both are federations, which means that they in fact are backed by multiple openEO instances. This increases the convenience
 for the APEx user, avoiding to interact with a high number of backends.
 
 ## Online user interface
 
 OpenEO provides an online user interface where users can execute services directly in a web browser.
-Through the graphical user interface, users can execute, link, and configure different services. More information on the usage of the online applications is presented in the table below.
+Through the graphical user interface, users can execute, link, and configure different services. More information on the
+usage of the online applications is presented in the table below.
 
 | OpenEO                                                                     |
 |----------------------------------------------------------------------------|
@@ -40,15 +47,18 @@ Through the graphical user interface, users can execute, link, and configure dif
 | [Documentation](https://openeo.org/documentation/1.0/#introduction)        |
 
 ::: {.callout-tip}
+
 ## Pro-tip: discovering API requests
 
 This interface provides a great way to find out how to interact with an openEO backend at the level of the HTTP API.
-Just use the 'developer tools' of your favourite browser and inspect HTTP requests to the backend to find out the various options.
+Just use the 'developer tools' of your favourite browser and inspect HTTP requests to the backend to find out the various
+options.
 :::
 
 ## Client libraries
 
-OpenEO provides client libraries to support the creation and execution of JavaScript, Python and R services. The full client libraries documentation is available on the official OpenEO support pages:
+OpenEO provides client libraries to support the creation and execution of JavaScript, Python and R services. The full
+client libraries documentation is available on the official OpenEO support pages:
 
 * [JavaScript](https://openeo.org/documentation/1.0/javascript/)
 * [Python](https://openeo.org/documentation/1.0/python/)
@@ -104,7 +114,8 @@ taskmap_job = taskmap.save_result(format='GTiff').send_job()
 taskmap_job.start_and_wait().get_results()
 ```
 
-To execute a service from the APEx through one of the OpenEO client libraries, it is important to use the *datacube_from_process* function.
+To execute a service from the APEx through one of the OpenEO client libraries, it is important to use the
+*datacube_from_process* function.
 This accepts the ID and namespace of the service.
 Both are made available in the service description on the EOplaza.
 The full documentation on using the function is available on the official [OpenEO documentation](https://open-eo.github.io/openeo-python-client/datacube_construction.html#datacube-from-process).
@@ -114,11 +125,12 @@ Examples are available in the [OpenEO GitHub repository](https://github.com/Open
 
 ## API
 
-OpenEO provides a fully documented API for a more advanced way to integrate features in any existing application or workflow. The API can also be used to execute EOPlaza services. The documentation is available at:
+OpenEO provides a fully documented API for a more advanced way to integrate features in any existing application or workflow.
+The API can also be used to execute EOPlaza services. The documentation is available at:
 
 | OpenEO |
 |---|
-| https://openeo.org/documentation/1.0/developers/api/reference.html |
+| <https://openeo.org/documentation/1.0/developers/api/reference.html> |
 
 The following example showcases how to use the OpenEO API to execute a synchronous request for the BioPAR service:
 

guides/eoap_writer_guide.md

@@ -23,7 +23,7 @@ Note that all the guidance material provided hereafter has APEx in mind, but can
 Observation applications. All APEx recommendations are made to support the FAIR principles, ensuring that your service
 can be easily shared within a broader community. These guidelines also facilitate the integration
 of your service into
-the [APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue).
+the [APEx Algorithm Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue).
 
 For best practice illustrations and examples, on how to package Earth Observation applications, the **EOAP Guide** is
 published here:\

guides/udp_writer_guide.qmd

@@ -43,7 +43,7 @@ graph. They can:
 Keep in mind that APEx offers [Algorithm Porting](../propagation/porting.md)
 and [Algorithm Onboarding](../propagation/onboarding.md) support to help you with transforming your algorithm into an
 openEO UDP, onboarding it onto an [APEx-compliant hosting platform](../propagation/platforms.md), registering it in the
-[APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue) and its onboarding onto
+[APEx Algorithm Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue) and its onboarding onto
 the [ESA Network of Resources](https://portfolio.nor-discover.org/).
 :::
 
@@ -53,7 +53,7 @@ User defined processes (UDPs) are one out of two standardised options that APEx
 service. This guide gives some concrete steps and guidelines to ensure that your UDP works well for your users. These
 guidelines are written with APEx in mind, but can also serve as a general guide for openEO UDPs. Where needed,
 recommendations and choices are made to increase uniformity across
-the[APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue).
+the[APEx Algorithm Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue).
 
 For more background on UDP's, or a basic tutorial on creating them, the open source Python client provides
 [a good starting point](https://open-eo.github.io/openeo-python-client/udp.html).
@@ -110,7 +110,7 @@ a limited set of parameters, and write a single UDP for each piece.
 
 This section provides some recommendations on how to name parameters in your UDP. While these are not mandatory, we
 recommend to consider them to avoid that users of the
-APEx [Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/) would be confused by variations in
+APEx [Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/) would be confused by variations in
 process parameter names.
 
 Please [let us know](https://github.com/ESA-APEx/apex_documentation/issues) if you encounter a parameter that could use