ObjectSelector as field type

1 Initial Problem

In general, this is about relating objects explicitly to other objects. Specifically, we have a use case in which an organisational unit shall be marked as responsible for a course.

We would like to see this implemented as custom meta data field, since there is a wide range of potential application for this feature.

The use of integer fields holding ref_ids is inacceptable for non-technical users. Thus, we second the proposal for a Selector Input,  simultaneously omitting the limitation to repository objects.

2 Conceptual Summary

A new type OBJECT_SELECT should be added to ilAdvancedMDFieldDefinition.
Selectable types from the objects' tree should be configurable for the field, including both repository object types and organisational units.

On editing the object bearing the meta-date, an interface akin to the one described in the request mentioned above, will be offered to the user.

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

4 Contact

• Author of the Request: Nils Haagen, CaT Concepts and Training GmbH (Haagen, Nils [nlz])
• Maintainer:  Stefan Meyer, Leifos GmbH (Meyer, Stefan [smeyer])
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

5 Funding

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

• ...

6 Discussion

Klees, Richard [rklees] Discussion with Stefan Meyer: Use dropdowns for type selection, not text edits. Manual sorting won't be required, types should be sorted according to appearance in "New Item" menu. Selection in the Form should be according to the selection when creating course references. In the repo list, a standard goto link should be used. The field should only be shown in the repo item list if user has sufficient permissions the referenced object. The field should not be searchable.

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