Internal Search for Metadata

1 Initial Problem

On each page in a wiki, there's a search bar in the top right corner that allows users to search for key words. The results list all articles that contain that key word in the title and/or text body. However, the results do not show articles where the key word was entered as one of the data points in the metadata. In other words, it is not possible to use the search bar to find articles with specific metadata.

2 Conceptual Summary

The wiki-internal search bar should be able to search for metadata keywords. The relevance display in the search results should include "metadata". Metadata is at least as important for search results as the term in the title.

It would be helpful to display the metadata found in the search results (e.g. as a separate column "Metadata"). The presentation of metadata in the search results should be considered in the efforts to Move Search Results Presentation to KS should be taken into account.

3 User Interface Modifications

3.1 List of Affected Views

• Wiki > Page > Secondary Panel "Search"
• Search Results Presentation

3.2 User Interface Details

The visual representation itself is not changed. The current search workflow will in future include metadata keywords in the search results (as the global search currently already does).

3.3 New User Interface Concepts

No new UI-Concepts.

3.4 Accessibility Implications

The additional information on metadata in the search results must be labelled accordingly, so that e.g. screen readers can output it optimally (i.e. when it is read out, it should be clear that it is a metadata that is being read out here).

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

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: Seiler, Yvonne [yvseiler], Thiel, Anja [athiel] Universität Bern
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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.

• Universität Bern

9 Discussion

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