Maintain Online/Offline Status for Objects Within Containers after Export/Import

1 Initial Problem

Currently, imported objects are always set to offline. While this is useful in general, it becomes annoying for users who regularly import container objects that contain several different objects with varying status. It is a lot of work to set all objects online again after importing e.g. a course.

2 Conceptual Summary

When copying a container with embedded objects, all embedded objects keep the online/offline status they had during export. Only the top container object - the copied course, group etc. - is set offline to avoid immediate access to this object. This would allow a course admin to modify the copied course according to his needs before setting it online. All embedded wikis, tests, learning modules, ... are still online (when they were online before) and could be used straight away when the course itself is set online.

(I am writing this after a positive signal concerning the issue from JF in Mantis. Basically, I stole this description from a similar feature request for COPIED objects that was introduced as a usability fix.)

3 User Interface Modifications

3.1 List of Affected Views

None.

3.2 User Interface Details

None.

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: Kruse, Fabian [Fabian]
• 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}.