bug in management GUI: after browsing to an element via the URI the export in sidebar fails

[MyPyDavid]

Description / Beschreibung

After browsing to an element via the URI (through the nested catalog) the export in sidebar fails.
The export URL of the sidebar contains a filter (e.g. ?uri_prefix=...) that was previously set in the overview, then the export returns a 404.

detail : "No OptionSet matches the given query."

Expected behaviour / Erwartetes Verhalten

in the single element detail, the sidebar exports works like normal.

Steps to reproduce / Schritte zum Reproduzieren

1. Go to management and filter for an uri_prefix
2. Click on nested view on a catalog
3. Scroll down to an element with another uri prefix and click on the URI
4. in the elements' detail page click on export XML in sidebar
5. See error 404

Context / Kontext

rdmo 2.3.2

References / Verweise

[MyPyDavid]

I dont think this is fixed in the current future release branches:

• rdmo/rdmo/management/assets/js/components/sidebar/ElementsSidebar.js

  Line 82 in 0ba965c

  <a href={`${exportUrl}?${exportParams}`}>{gettext('XML')}</a>

from 3.0.0-management:

• https://github.com/rdmorganiser/rdmo/blob/68b76d3a29942f8fb2a7b289d4855871590de27e/rdmo/management/assets/js/components/sidebar/ElementsSidebar.js#
• https://github.com/rdmorganiser/rdmo/blob/68b76d3a29942f8fb2a7b289d4855871590de27e/rdmo/management/assets/js/utils/filter.js#L50C15-L50C15

Is it a bug in the state of the query parameters for OptionSets? I can only reproduce it for those.

[jochenklar]

I think we need a check here https://github.com/rdmorganiser/rdmo/blob/2.3.3/rdmo/management/assets/js/components/sidebar/ElementsSidebar.js#L21 if elementId is set and elementAction is not nested (it could be null or copy) and set exportParams empty than.

[jochenklar]

@MyPyDavid did we fix this?