[Potential Feature] Extending Arches search results sort order component for additional and custom sorts #11780
Labels
Audience: Developer
The audience for the issue is a software developer
Audience: End User
The audience for the issue is an end user of the instance
Original user story/request: "We would like to be able to search for our results in a specific order of resource models, for example show all Monuments first, then Activities, then Sources etc."
Intially, we began looking at modifying the
SortResults
component to implement our own elasticsearch DSL query, replacing the default. This worked fine, but of course was quite invasive to core Arches. When trying to make it an improvement/expansion to the core feature, we used the config field to provide information to the component, but even this seemed to be too narrow or specific of an improvement and opened up a few other questions.Thinking how this could benefit all users of Arches, we think it could be a very nice feature if the SortResults component could be extended to support custom queries, while not impacting the current sorting of the display name within Arches.
At the moment, the sort order of search results is a bit all or nothing, with no option to move between different sort options in the UI, other than ascending and descending on the Primary Descriptor. One idea could be to introduce a new 'sort by' drop down in the UI with some common options e.g. 'Name' (the current default), maybe a 'Date created' (although this opens another can of worms as edit/creation dates aren't in the ES resources index at present), maybe move unsorted in here as well etc., with the config being used to add any additional custom options (e.g. 'Graph - custom order'). This new custom order would then appear as a dropdown option. Asc and desc could also be a separate dropdown, flexible to only show if the selection isn't unsorted.
To put the ideas in lists...
Requirements:
Desirables:
Needs further discussion/approval:
The text was updated successfully, but these errors were encountered: