From 2c9bfc8e18bed29ec69a639c8a45e461b52c5e66 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 5 Feb 2024 10:58:41 +0000 Subject: [PATCH] Addressing docs translation glitch #7687- fixes adding-static-pages and configuring-search-fields --- .../adding-static-pages.md | 18 +++++++++--------- .../configuring-search-fields.md | 4 ++-- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/manual/docs/customizing-application/adding-static-pages.md b/docs/manual/docs/customizing-application/adding-static-pages.md index d1c31a506f7..0d0fd982b9a 100644 --- a/docs/manual/docs/customizing-application/adding-static-pages.md +++ b/docs/manual/docs/customizing-application/adding-static-pages.md @@ -8,13 +8,13 @@ This feature allows to store the HTML content for static pages and show the link - Each page can be in 3 states: - - `EN`: visible to administrator. - - `TE`: visible to logged users. - - `IC`: visible to everyone. + - `HIDDEN`: visible to administrator. + - `PRIVATE`: visible to logged users. + - `PUBLIC`: visible to everyone. -- Pages can be added to different page sections. Currently the sections implemented are `OP` (top menu of the main page) and `ER` (footer of the main page). +- Pages can be added to different page sections. Currently the sections implemented are `TOP` (top menu of the main page) and `FOOTER` (footer of the main page). -- Only the administrator can edit the pages and see the pages in `EN` status. +- Only the administrator can edit the pages and see the pages in `HIDDEN` status. - The creation and the management of the content is done via the API. @@ -80,10 +80,10 @@ curl -X DELETE "http://localhost:8080/geonetwork/srv/api/pages/eng/contactus?for The status of the page can be changed with the method PUT `/api/pages/{language}/{pageId}/{status}` where status could assume these values: -- `IC` - Visible to every user -- `LY` - Visible to not logged users -- `TE` - Visible to logged users -- `EN` - Hidden to anyone +- `PUBLIC` - Visible to every user +- `PUBLIC_ONLY` - Visible to not logged users +- `PRIVATE` - Visible to logged users +- `HIDDEN` - Hidden to anyone Other methods in the API are to change/delete a page and to GET the list of the pages or the info of a specific one. diff --git a/docs/manual/docs/customizing-application/configuring-search-fields.md b/docs/manual/docs/customizing-application/configuring-search-fields.md index c03b2184ba8..266e107b046 100644 --- a/docs/manual/docs/customizing-application/configuring-search-fields.md +++ b/docs/manual/docs/customizing-application/configuring-search-fields.md @@ -195,7 +195,7 @@ curl -X POST "localhost:8080/geonetwork/srv/api/search/records/_search" \ To customize how the field is indexed see `web/src/main/webResources/WEB-INF/data/config/index/records.json`. -To return it in the search response, use the `ce` parameter of the query. See . +To return it in the search response, use the `_source` parameter of the query. See . ## Boosting at search time @@ -248,4 +248,4 @@ By default, the search score is defined as (see `web-ui/src/main/resources/catal ## Language analyzer -By default a `rd` analyzer is used. If the catalog content is english, it may make sense to change the analyzer to `sh`. To customize the analyzer see `web/src/main/webResources/WEB-INF/data/config/index/records.json` +By default a `standard` analyzer is used. If the catalog content is english, it may make sense to change the analyzer to `english`. To customize the analyzer see `web/src/main/webResources/WEB-INF/data/config/index/records.json`