Reference Fields Avoid Selection of Duplicates

1 Initial Problem

In Data Collections, you can insert "Reference" fields, and you can define fields in a way that duplicate entries aren't allowed.
Especially in this combination, in the way it's like now, users have to guess until they find the options not selected yet.

2 Conceptual Summary

A lot of usability could be gained by some additional programming: "Reference" fields with no duplicates allowed should either hide the options already selected in other data sets, or they could deactivate them, so they cannot be selected anymore.

3 User Interface Modifications

3.1 List of Affected Views

dcl/id_records/

3.2 User Interface Details

"Reference" fields with no duplicates allowed should either hide the options already selected in other data sets, or they could deactivate them, so they cannot be selected anymore.

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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: {Please add your name.}
• 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.

• …

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