Hello,
A little background of this topic.
We are currently using SharePoint Search for crawling/indexing our web presence to create a website search experience on our site. Part of the functionality of SharePoint search provides "result sources". These provide for a, say, 'secondary' search field on a web page that allows a user to search for content only in that www.mydomain.com/page/ subdirectory. While at the same time, in the page header there is still the 'global' domain site search functionality.
A snip of this current functionality is attached.
Question:
We are using an Elastic Cloud deployment to replace the SharePoint Search appliance. Leveraging an App Search 'meta engine', is it possible to create an experience like above?
The below, standard CURL query works as a 'global' search starter, works fine:
curl -X POST 'https://deployment.ent.us-east-1.aws.elastic-cloud.com/api/as/v1/engines/meta-engine/search' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer search-hashed' \
-d '{"query": "text", page: { size: 2 }}'
To add the secondary search field to the page, I was reviewing documentation/Googling to add in a 'wildcard' field(?) for the URL to search in just that subdirectory. However, I don't think I am doing it properly. Full disclosure: I'm not a web dev and constructing this is new for me! Be gentle.
curl -X POST 'https://deployment.ent.us-east-1.aws.elastic-cloud.com/api/as/v1/engines/meta-engine/search' -H 'Content-Type: application/json' -H 'Authorization: Bearer search-hashed' -d '{
"query": "text",
"filters": {
"any": [
"type": "wildcard",
"field": "url",
"value": [
"https://www.mydomain.com/page/*"
]
}
]
}'