Expand Copy Wizard With Settings

1 Initial Problem

When copying study programs, the usual wizard for copying container objects in ILIAS is used, i.e., a target position is selected as well as the child objects to be copied/linked.

On the other hand, there is no way to choose the settings to be adopted.
This isn't the case with other container objects, either. However, these other container objects adopt almost all of the settings of the copied object and its child objects when they are copied (with a few exceptions, such as the online status of child objects), while almost all of the settings are lost in the study programme (status, points, deadlines , ...).

This makes copying study programmes a tedious job, especially when it has many and deeply nested sub-elements.

2 Conceptual Summary

A third view is added to the copy wizard for study programmes, allowing to choose which settings of each node are to be adopted.

3 User Interface Modifications

3.1 List of Affected Views

• none (feature request proposes a completely new view)

3.2 User Interface Details

The additional view in the copy wizard is structured as follows:

• It is a table containing a row for each child object of the "study programme" type that were selected in the previous view to be copied (linking is not possible anyway).
  Other objects (like course links) don't appear in that view, even if they were selected in the previous view to be copied.
• The first column of the table shows the titles of the affected objects.
  Further columns follow for the following settings to possibly be adopted:
  • Status
  • Points
  • Processing Period
  • Validity of achieved Qualifications
  • Restart
  • E-mail Renewed Participation
  • E-mail Reminder Restart
  • E-mail in Case of Failure
• The columns for the settings to be adopted have a checkbox for each column and row (not selected by default), as well as information about how the settings were configured in the original object.
• Settings with sub-options (e.g. "Processing Period" with the option "Processing time is determined inividually" and the number of days as a sub-option) are displayed as one configuration item.
  The sub-options are appended in brackets, e.g., a table cell there might read:
  "Processing time is determined inividually (90)"
• The option and its sub-option(s) can only be adopted together, e.g.:
  In case you choose to adopt "Processing time is determined inividually", the number of days must be adopted as they were in the original object (however, of course it can be changed afterwards in the settings of the study programme).
• With checkboxes marked, selected settings are adopted from the original objects when the form is sent.
  Otherwise, the copying process is the same as before, i.e., the settings aren't adopted but behave as if a completely new study programme had been created.

3.3 New User Interface Concepts

The view doesn't substantially differ from the previous one (where objects can be selected to be copied).
There are some differences, however, they presumably don't arise the need for a "new UI concept":

• There are checkboxes instead of radio buttons in the table cells.
• There is text next to the checkboxes.
• There aren't bulk options on the bottom of the table (like "Copy All").

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

(none)

7 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• Maintainer: Klees, Richard [rklees]
• 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.

• …

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