We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When wms resource is added to the metadata by using default NHAP template.
There is a little error pops up "feature not index". This is caused by.
https://github.com/geonetwork/core-geonetwork/blob/36951d179d5b63b2e9134cf84987dc402acda86b/web-ui/src/main/resources/catalog/components/index/IndexRequest.js#L168
when querying /index/features?_=_search with zero hits back from the response
Then the JS cannot read the properties
var indexInfo = response.data.hits.hits[0]._source;
I am wondering if HNAP metadata is lack of some information to pass to feature indexing?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When wms resource is added to the metadata by using default NHAP template.
There is a little error pops up "feature not index". This is caused by.
https://github.com/geonetwork/core-geonetwork/blob/36951d179d5b63b2e9134cf84987dc402acda86b/web-ui/src/main/resources/catalog/components/index/IndexRequest.js#L168
when querying /index/features?_=_search with zero hits back from the response
Then the JS cannot read the properties
I am wondering if HNAP metadata is lack of some information to pass to feature indexing?
The text was updated successfully, but these errors were encountered: