Feature Request/Idea: Allow additional search results views as tabs via plugable components

Overview of the Feature Request

The curent search results display shows a list of the results 'top-level' (citation) metadata.
There are cases where putting emphasis on a specific set of metadata values to display the reuslts and allow to navigate (browse) them makes sense. Our primary use-case for this is showing the Dataset locations (coordinates) on an intecative geographical map (#580). The map allows the user to see the relation of the dataset location with respect to other datssets and also with respect of the environment - nature or human constructions in the landscape - in a spatial (2D) way.

Other possibilities are:

1. A timeline view showing the results on a timeline using the date metadata information.
   This is specially useful for archaeology and historic research, where dating objects and human activety periods is important The ordering on a timeline would be way to make the relation in time; sequence of events and distribution (frequency) more clear.

2. A view of the content with more emphasis on the collections (sub-verses) which can be an extensive hierachy (tree structure). The information about the file content and other facets could be visualised in a way that is similar to what is done for the metrics; using graphs. One could even imagine an interface that allows for the content of collections, datasets and files in a way that is similar to navigating a directory structure. This could even be done with a 3D view.

3. An interactive 'research graph' with nodes and edges displaying the relations between authors (and other 'agents') to the datasets. This might reveal clusters of co-authorship and cooperation.

4. Search result metadata export. As soon as researchers have narrowed down their search query it might make sense to keep the result for later use in their own research. Downloading a specified set of metadata blocks for each dataset in the result and saving it to various formats (csv, json, xml) allows them to do analysis on that with their own tools. This is more flexible than the OAI export.

Any open or closed issues related to this feature request?

• https://github.com/IQSS/dataverse-frontend/issues/580
• https://github.com/IQSS/dataverse/issues/12533

Start by reviewing the current search-results UI and the related issues #580 and #12533. Determine how additional result views could be exposed as tabs and what a pluggable component boundary would require. Done should include an agreed scope and design for at least the proposed map, timeline, graph, or metadata-export views.