Feature Wiki
Tabs
Identify existing Material Assignments of Objects of an Item Group
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
1 Initial Problem
All objects in the parent container are available for assigning an object to an item group.
This applies to objects that have already been assigned in an item block and to those that have not yet been assigned - which is generally a good thing. This also makes it possible for an object to belong to several item groups.
Unfortunately, however, it is not possible to recognise whether an object has already been assigned to one or more item groups. This overview is particularly useful if you have a large number of objects (>10 and significantly more) in a container.
In order to understand whether all objects have been assigned in the meantime, you have to leave the item group again and again and check.
2 Conceptual Summary
The display of the assigned materials should be supplemented by a column with further information.
- Option A) a Boolean field (checked-/unchecked-Glyph) under the column title “Already assigned to other Item Group”.
- Option B) a list of the other item groups to which this material has already been assigned. column title “Already assigned to other Item Group”.
Option B is favored. The screen offers sufficient space. The information about which other assignment or which other assignments exist is valuable.
3 User Interface Modifications
3.1 List of Affected Views
- 'Materials'-Tab of an Item Group
3.2 User Interface Details
An UI Data Table is to be used as part of the modification.
Columns: Checkboxes | 'Item' (Object Icon and Title) | 'Assigned to the Item Group' (Glyph unchecked/checked) | 'Already assigned to other Item Group' (Bullet Point Listing (empty, one or more Item Group Title)) — Columns should be sortable.
3.3 New User Interface Concepts
None.
3.4 Accessibility Implications
Nothing specific or new.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Killing, Alexander [alex]
- Authority to Sign off Code Changes: Killing, Alexander [alex]
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }
4.3 Privacy
Nothing specific or new.
4.4 Security
Nothing specific or new.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Samoila, Oliver [oliver.samoila].
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: 3. Mar 2025, 13:15, Samoila, Oliver [oliver.samoila]