Make copying issues more visible

1 Initial Problem

Copying container objects was implemented in 2007. Since then there has been no revision or improvement of the copying mechanism. Looking roughly 150 bugs on copying (including fixed ones, closed ones, not-course-related ones) has shown that the many, many bugs result actualy in non-course components but the bug is put to the bug-category "course": Because copying is processed in the background user cannot determine where things went wrong without analysing the log file. 

2 Conceptual Summary

• Errors in copying get proper messages presented in the GUI. 
• Errors messages in copying are as informative as possible. 

3 User Interface Modifications

3.1 List of Affected Views

• List GUI in repository

3.2 User Interface Details

New Error messages on top. Exactly like normal error messages. 

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 Privacy Information

No new personal data that will need to be stored or processed to implement this feature. 

6 Security Implications

We do not see any special security relevant changes.

7 Contact

• Author of the Request: Meyer, Stefan [smeyer]
• Maintainer: Meyer, Stefan [smeyer]
• 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}.