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
Is your feature request related to a problem? Please describe.
The bulk export can only be triggered when the entityType filterfacet is configured on the discovery configuration. As a repository manager i might configure this facet on the default/site configuration, but not on relation boxes which mostly include only one entity type per tab. If the filterfacet is missing the export button will be shown with the available export formats, but in the modal the user will get some warning message. This is annoying for the user, because as an user i would expect that when there is some export button it offers me the possibility to export somethin.
No filters configured for configuration (entries exist)
Publication button is shown:
Modal shows message:
Describe the solution you'd like
We would like some additional configurable property to hide filterfacets to be shown on specific search configurations. The facets are still calculated and delivered through the Rest-API, but simply not shown.
On the backend this could be achieved by some new list of DiscoverySearchFilterFacethiddenSidebarFacets on the DiscoveryConfiguration itself which contains the beans which are not shown. This information is added and passed through the REST API as some extra property isHiddenOnSidebar on the SearchFacetEntryRest.
On the frontend this property is mapped in the search-filter-config.model and if the property is set than the filterfacet is hidden in the search-filters.component .
Describe alternatives or workarounds you've considered
check the current available entities for the query together with the list of available export formats.
Hide the export button when there are no entries
Additional context
The text was updated successfully, but these errors were encountered:
floriangantner
changed the title
remove entityType filterfacet from bulkExport functionality
hidden entityType filterfacet for bulkExport functionality
Mar 6, 2024
At least in our current installation of 2023.02.03 it seems to be enough to configure the entity-type filter as a searchFilter only and not as a sidebarFacet for the export to work. This way the entity-type filter only shows up on the corresponding search page in the dropdown next to the search field. This is still not optimal but much less better than having a redundant filter-facet in the sidebar.
One Exception are the Publications of a person and Publications of an Orgunit Pages. Here the export-Button does not work at all, even when the entity-type filter is added as a visible sidebar facet. This might be a separate bug, though.
Is your feature request related to a problem? Please describe.
The bulk export can only be triggered when the entityType filterfacet is configured on the discovery configuration. As a repository manager i might configure this facet on the default/site configuration, but not on relation boxes which mostly include only one entity type per tab. If the filterfacet is missing the export button will be shown with the available export formats, but in the modal the user will get some warning message. This is annoying for the user, because as an user i would expect that when there is some export button it offers me the possibility to export somethin.
No filters configured for configuration (entries exist)
Publication button is shown:
Modal shows message:
Describe the solution you'd like
We would like some additional configurable property to hide filterfacets to be shown on specific search configurations. The facets are still calculated and delivered through the Rest-API, but simply not shown.
On the backend this could be achieved by some new list of
DiscoverySearchFilterFacet
hiddenSidebarFacets
on the DiscoveryConfiguration itself which contains the beans which are not shown. This information is added and passed through the REST API as some extra propertyisHiddenOnSidebar
on the SearchFacetEntryRest.On the frontend this property is mapped in the
search-filter-config.model
and if the property is set than the filterfacet is hidden in thesearch-filters.component
.Describe alternatives or workarounds you've considered
Additional context
The text was updated successfully, but these errors were encountered: