You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have performed an installation of the latest version, 2.7.2.1.
When performing a search operation on or modifying (e.g. via uploading a new .xml metadata file) the index, there is an item with the id "_search" added to the index. If this "_search" item is removed manually, it reappears with the next index-operation. There is only one "_search" item at a time, i.e., if it already exists it is not re-added.
When geoportal prints the total number of items on the Catalog page, the number is one (1) higher than the actual registered geoportal items. This is seemingly because geoportal includes the “_search” item in the count. It should also be noted that "_search" is not displayed as an actual item on the catalog page, it does not appear here.
When a filter (e.g., spatial, temporal, keywords etc.) is employed from the Catalog, the "_search" item is not included in the count, resulting in a correct number being displayed.
The same issue occurs using both Elasticsearch and OpenSearch, regardless of whether they are running on containers locally or through AKS.
To Reproduce
Upload a metadata item, e.g. an xml file, to an otherwise empty index.
Note that the number of "items" is 2 instead of 1.
See that there is an item "_search" in the index.
Expected behavior
We would expect only actual manually registered, items to be included in the total item count print
The text was updated successfully, but these errors were encountered:
Describe the bug
We have performed an installation of the latest version, 2.7.2.1.
When performing a search operation on or modifying (e.g. via uploading a new .xml metadata file) the index, there is an item with the id "_search" added to the index. If this "_search" item is removed manually, it reappears with the next index-operation. There is only one "_search" item at a time, i.e., if it already exists it is not re-added.
When geoportal prints the total number of items on the Catalog page, the number is one (1) higher than the actual registered geoportal items. This is seemingly because geoportal includes the “_search” item in the count. It should also be noted that "_search" is not displayed as an actual item on the catalog page, it does not appear here.
When a filter (e.g., spatial, temporal, keywords etc.) is employed from the Catalog, the "_search" item is not included in the count, resulting in a correct number being displayed.
The same issue occurs using both Elasticsearch and OpenSearch, regardless of whether they are running on containers locally or through AKS.
To Reproduce
Expected behavior
We would expect only actual manually registered, items to be included in the total item count print
The text was updated successfully, but these errors were encountered: