Filter and Default Setting for Copy Process

1 Initial Problem

The copy process for containers sets all child items to be copied by default. The user is only able to change the action for all items to copy or link via bulk action. For big containers with a lot of content this is only half the way. After deciding if the majority of items should be copied or linked, you then have to go through this long list of items and change the action for a lot of items.

Consider this:

A tutor tries to adopt content from an old course over to a new one. The course contains many PDF files, but also tests, forums etc. The PDF files should be linked to avoid using unnecessary system resources and to allow the editing/management from another, linked location in the repository. Some item types like tests, forums etc. need to be copied though. The tutor then can set all items to be linked via a bulk action but then has to tediously go through the list and set all tests and forums to "copy" manually.

2 Conceptual Summary

2.1 RFC 2119

2.2 Requirements

The copy process screen is enhanced with a filter box to enable users to quickly filter objects by type. This allows to then quickly switch the action from copy to link by item type etc. Additionally a "Reset Action" button is added with which users can restore the default action for all item types.

3 User Interface Modifications

3.1 List of Affected Views

• ilobjectcopygui

3.2 User Interface Details

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

The proposed changes should not introduce new accessibility implications.

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

Not relevant.

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