Feature Wiki
Tabs
Search Current Course
Page Overview
[Hide]1 Initial Problem
There is no convenient way to search locally and fast within a course object. The local search in the meta bar is often times quite challenging for the user.
2 Conceptual Summary
In course-objects a secondary panel "Search Course" will be integrated, which contains a searchbox. This searchbox will appear in the same manner as the searchbox in ILIAS wiki and forum objects. This searchbox can be (de)avtivated in the "setting" tab.
The search in the current course should re-use the general search mode currently activated (especially lucene should be used if activated). The presentation of search results should be implemented by the search component and be similar to the standard results screen. Sub elements should be listed on the top level in this case, each entry should get a relevance bar (if lucene activated).
3 User Interface Modifications
3.1 List of Affected Views
- Course-Object-Content
- Course-Object-Settings
3.2 User Interface Details
Course-Object-Content
Course-Object-Settings
3.3 New User Interface Concepts
All added elements are existing KS components
3.4 Accessibility Implications
There should not be any new accessibility implications, since only existing views / KS elements are being used.
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: Spirou, Ilias [ispirou]
- 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
UI Clinic, 16.08.2022 (Seiler, Yvonne [yvseiler], posted on 15.01.2023): Thanks for your request and the meeting in the UI Clinic. Questions about this feature were discussed in the UI Clinic on 16.8.2022. The collected discussion points can be viewed in the following data collection entry as a PDF: https://docu.ilias.de/goto_docu_dcl_8186_166_7613.html
Concerns came up in the UI Clinic on several points that may be relevant to the discussion of this feature moving forward:
- Currently, there is no argument to distinguish one secondary panel from another secondary panel to make it a "top" secondary panel (e.g. it remains open why search in a wiki is more important than wiki navigation).
- The distinction between local and global search is considered difficult for users. People with screen readers need quick access to the search; it is feared that the search in the secondary panel will be visible "too late". Users must also recognise at every point in ILIAS whether a local search is available or not. It is recommended to consider whether the local search can be better integrated into the global search (better than the current "at current position"). Basically, ILIAS needs an improved global search so that users receive better search results; the requirements for a local search could also be integrated here (e.g. "Search User" questionable whether it is still helpful and there is a need for it).
- It is suggested to consider whether the search as a secondary panel is really the right solution and should remain as such, or whether it is e.g. a filter that is already displayed in the content area at the beginning of a page.
As next steps, it was decided that these points would be brought to the group dealing with this topic. We thank you for the interesting exchange at that meeting.
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}.
Last edited: 17. Jan 2023, 11:35, Spirou, Ilias [ispirou]