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
Currently, a user copies the url from a search query and pastes this into the "saved search" url field. The reasons this isn't ideal are:
migrating saved searches data from one instance to another (e.g. dev to prod) carries the baggage of the different host names (which then must be manually changed)
the url only contains query parameters for GET requests -- longer requests (involving geojson filtering) may get made as POST, thus not showing up in the url parameters due to character limits
the http encoding of the url can make the search request very hard to visually parse; a better representation would be key: value a la json object
*As a side note, a related issue with the saved searches UX is that it reloads the entire page. Search is basically a progressive web app, so it should just mutate the query based on whatever the saved search query params were, not reload the entire page.
What might a potential solution be?
A user with high enough permissions could click a button labeled "Make saved Search" which copies the current query parameters to a json object, storing that in the saved search tile.
The text was updated successfully, but these errors were encountered:
whatisgalen
changed the title
Create a way to "Make Saved Search" from the Search UI
Create a better way to "Make Saved Search" from the Search UI
Oct 30, 2024
Currently, a user copies the url from a search query and pastes this into the "saved search" url field. The reasons this isn't ideal are:
*As a side note, a related issue with the saved searches UX is that it reloads the entire page. Search is basically a progressive web app, so it should just mutate the query based on whatever the saved search query params were, not reload the entire page.
What might a potential solution be?
A user with high enough permissions could click a button labeled "Make saved Search" which copies the current query parameters to a json object, storing that in the saved search tile.
The text was updated successfully, but these errors were encountered: