Show Advanced KnowledgeHide Advanced Knowledge

Link Linked Objects When Container Is Copied or Content Adopted

1 Initial Problem

Consider the follwoing scenario:

You have a test that has been linked into a group. This group servers as a "copying" template because you need 30 of them.

When you copy the group, the test is by default selected for being copied, and not linked, which breaks the link and produces a copy of the linked object. In the copy process, users have to manually select the radiobutton "Link" for each linked object when a container is copied.

Problems:

• The current behaviour is in 99% of all cases not the desired outcome.
• The suer has no chance to distinguish objects with and without linked "twins" from each other on the Copy screen (Step 2)

These problems extsis for all container objects in ILIAS and occur for the Actions "Copy" and "Adopt Content".

2 Conceptual Summary

I propose two changes in behaviour of "Copy" and "Adopt Content" for container objects in ILIAS to solve the above stated problems.

1. New default behaviour for objects with have linked twin objects: preselect "Link" instead of
2. Show number of existing links of this object beneath object title in the list.

Example:

"Test for Awesomeness"                                            |     (   ) Copy      |  ( o ) Link      |  (   )  Omit
Links of object in other contexts: 12

"Survey of Degrees of Individual Lunacy"                |     ( o ) Copy      |  (   ) Link      |  (   )  Omit
 

"Important File with Info"                                          |     (   ) Copy      |  ( o ) Link      |  (   )  Omit
Links of object in other contexts: 587

3 User Interface Modifications

3.1 List of Affected Views

Course (Action Menu) > Copy Course (Step 2/2)
Group (Action Menu) > Copy Group (Step 2/2)
Folder (Action Menu) > Copy Folder (Step 2/2)
Category (Action Menu) > Copy Category (Step 2/2)
Learning Sequence (Action Menu) > Copy Learning Sequence (Step 2/2)

{Course / Group / Folder / Category / Learning Sequence} > Content > Manage > Adopt Content > Step (2/2)
{Course / Group / Folder / Category / Learning Sequence} > Content > Manage > Copy > Step (2/2)

Add New Item {Course / Group / Folder / Category / Learning Sequence} > Copy { ~ } > Step (2/2)

3.2 User Interface Details

see above

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: Glaubitz, Marko [mglaubitz]
  
• 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.

• Universität Freiburg

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