Incorrect data points showing when selecting Master datasets second time

[visead]

I'm not sure what's causing this, but it appears to be supersead related. I am also not entirely sure that it is a problem, but wanted to flag it for more investigation (Phil & Love?).

When filtering by Master dataset, the first filter application works as expected:

Adding an additional master dataset to the selected items works correctly:

Removing the first selection from the list does not always work, and either leaves the set there or even adds more data. Below I added each master dataset, then removed the Wood one, but the latter remained. , but the latter remained.

Problem exists in both Firefox and Edge.

[johanvonboer]

As far as I can tell this is a backend issue so I moved it to sead_query_api repository

[roger-mahler]

Sorry for late reply, but I haven't been able to reproduce this problem. I thing worth mentioning is that each request result returned to the client contains the actual SQL that was generated by the query engine. It would simplify debugging if the client had a feature to display this query, and the configuration sent to the query engine.

It is quite easy, though, to retrieve this information using the web browsers developer tools. For Chrome, the procedure would be:

Press F12 to open the developer tools.

Pressing F12 in the browser opens the developer tools as a side-by-side window.

To information about a API request (as made when e.g. the user selects an item in the facet) is found under the Network tab (2). This tab shows all the requests made by the browser, and updates whenever new requests are made. A load of a facet is names "load" in the list, which corresponds to a /facets/load API call. The request is a POST request meaning that the client request has accompanying data (request payload).

Find the facet load request data

Press the load request (1) you are interested in. Press the Headers tab (2), scroll down to Request Payload (3) and press view parsed. The JSON displayed is the data sent from the client for the selected request, and contains the chain of facets and the user picks for each facet (if any). A specific facets configuration (i.e. JSON data) should give the same result - unless the underlying data in the database is unchanged. Please copy out this JSON and attach it to any Github issue that requires further investigation.

Find the facet load response data

[johanvonboer]

I believe this turned out to be a frontend issue that is now fixed - I forgot I had moved this issue here, sorry!