Adopt Content: Option to omit only container

1 Initial Problem

When selecting a container (group, folder etc.) to be omitted during the copy process step 2, all child items of the container are omitted as well. There is no option to omit the container, but to still copy or link child items of the container to the target location.

2 Conceptual Summary

2.1 RFC 2119

2.2 Requirements

The copy screen is updated with a second option for omitting items for containers "Container only". This will mark the container to be omitted, but keeps the selection open for child items. In case a child item is copied or linked without its direct parent, the object will be created at the root node of the target location, i.e. if the target is a course, the object will be created on the top level of the course.

3 User Interface Modifications

3.1 List of Affected Views

• ilobjectcopygui

3.2 User Interface Details

An option "omit only container" is added to the table containing the items of the selected source container for all container items (course, group). Selecting this option keeps all child items to be copied/linked. Items are copied/linked to the root level of the target location.

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

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 Privacy

None.

6 Security

No security implications.

7 Contact

• Author of the Request: Sesterhenn, Fabian [sesterhenn]
  
• 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.}

8 Funding

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

• TH Köln

9 Discussion

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