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
I think we didn't pursue this issue because it was linking to staging where we didn't expect the search to work, but now that we've updated the data in staging, it's more apparent. The see more link submits the http-encoded version of the search string:
sys.collection%3a%22%7b9B7778AC-DE79-287A-2A79-F05863C8A212%7d%22
which the EDG search apparently can't handle properly (unless it's in an actual URL being interpreted as a REST query) so when triggering a search on the search page, the "See More" link needs to submit this equivalent version:
sys.collection:"{9B7778AC-DE79-287A-2A79-F05863C8A212}"
The text was updated successfully, but these errors were encountered:
I think we didn't pursue this issue because it was linking to staging where we didn't expect the search to work, but now that we've updated the data in staging, it's more apparent. The see more link submits the http-encoded version of the search string:
sys.collection%3a%22%7b9B7778AC-DE79-287A-2A79-F05863C8A212%7d%22
which the EDG search apparently can't handle properly (unless it's in an actual URL being interpreted as a REST query) so when triggering a search on the search page, the "See More" link needs to submit this equivalent version:
sys.collection:"{9B7778AC-DE79-287A-2A79-F05863C8A212}"
The text was updated successfully, but these errors were encountered: