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

3.2 User Interface Details

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 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

The search results presentation get checked via "access".

4.3 Privacy

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

4.4 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. }

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Tödt, Alexandra [atoedt]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 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?

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.