Configurable Behaviour of Link to an ILIAS module field type

1 Initial Problem

In former version, fields of the 'Link to an ILIAS module' type offered a field for a search term - and presented search results in a list.
Currently (ILIAS 5.4.x), they are offering an overview of the repository.

This way, users have to know where some object is located in the repository which might apply in some cases but far not in any case.
From the perspective of a user who only knows the title of an object, the current implementation is not really usable.

2 Conceptual Summary

We suggest to re-implement the old behaviour as one of two possible settings for fields of this type:
Depending on the setting, the field either offers a repository overview or a search field.
Additionally, the search results should be presented in separate lines (instead of one long string as it was in former versions).

3 User Interface Modifications

3.1 List of Affected Views

• "New Field" form in a table of a data collection (unfortunately, there is no screen id for that view)
• dcl/id_records/ (view after clicking "Add New Entry" or selecting "Edit" from the corresponding "Actions" menu)

3.2 User Interface Details

• "New Field"
  As soon as the 'Link to an ILIAS module' option is selected, an additional sub-option "Type" is presented:
  A radio button each for "Search Field" and "Repository Overview".
• dcl/id_records/
  Depending on the chosen setting, the field either presents a) some text field with "Search" link or b) both of the "Select" and "Reset" links of the current implementation.
  In variant a), after submitting some search text ILIAS displays results in a list of clickable lines.

3.3 New User Interface Concepts

(none)

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 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• 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.}

6 Funding

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

• THW

7 Discussion

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