Move Search Results Presentation to KS

1 Initial Problem

The presentation of search results is outdated. The clarity of the search results suffers from this. In order to improve the usability, the existing elements are to be transferred to KS components. In addition, the displayed information will be discussed so that search results are more clearly structured and understandable.

Search Result Presentation

• Consider list as an alternative format to replace the table presentation. 
• Consider information presented
  • "Last Update" would be more pertinent than "Created On" however it cannot be known because of changes in mediapools / content snippets and linked objects. This should be abandonned. 
  • "Relevance" makes users wonder and ist visually very prominent. This should no longer be presented. 
• What sorting mechanisms would be helpful? Consider a view control offering relevance as sortation criterion.
• What purpose does the action menu serve? 
• Consider list as an alternative format to replace the table presentation. 

2 Conceptual Summary

Each individual search result ist displayed as an individual item.

• Each item carries an icon of the found object. 
• The item is comprised of a linked Title, the text snippet is presented in the description.
• Properties are
  • Comprised in encompassing object
  • Path
  • Created on 

3 User Interface Modifications

3.1 List of Affected Views

• Search Form in Slate opened via Metabar entry 
• Search Results Presentation 

3.2 User Interface Details

• New Filter Element Date Time
• New Filter Element Repository Picker 

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

The search results presentation get checked via "access".

• Online and offline is checked
• The permissions visible, read and join are to be checked. These checks need to made available by the object service. How will this be done
• Preconditions are not checked, if there are preconditions and the clicks on the object, the user will be just presented with the information about precondistions on the respective Info screen 

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Tödt, Alexandra [atoedt], Zenzen, Enrico [ezenzen]
• Maintainer: Meyer, Stefan [smeyer]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

Engländer, Ferdinand [fenglaender], 14 March 2022: Are there any decisions or plans yet which UI compenent will be used to display a search result item? Or will a new UI component be developed that could take slightly different appearances depending on the nature and requirements of an individual item?

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.