Drag and Drop for Session Materials

1 Initial Problem

Sessions are strong as containers for materials. Adding materials to a session or moving them from one session to another currently requires long click paths.

This involves the following actions:

• Add a new file
• Moving objects from one session to another
• Assigning course content objects to a session

2 Conceptual Summary

Following actions should be shortened with a drag and drop function. Therefore the handling of materials in sessions should be simplified.

2.1 Add a new file

A file can be dragged and dropped from the computer to a session (similar to file drag and drop for folders or courses). The session is highlighted so that it is clear that the object can be placed here. This uploads the file to ILIAS and attaches it directly to the session.

2.2 Moving objects from one session to another

An object that is already assigned in a session can be grabbed with the mouse and dragged and dropped onto the session. The session is highlighted so that it is clear that the object can be placed here. The object is thus removed from the previous session and assigned to the new session. No copy operation takes place.

2.3 Assigning course content objects to a session

An object that is present in the course ("Contents" block) can be grabbed with the mouse and dragged and dropped onto the session. The session is highlighted so that it is clear that the object can be placed here. The object will be assigned to the session. No copying process takes place.

2.4 Drag and Drop as additional function

This Drag and Drop functionality is the alternative to the previous procedure: Actions > Assign Materials > Select Object > Assign
The previous procedures remain in place. The drag and drop functionality is additional to the existing processes.

2.5 Trigger and Highlight

To trigger the Drag and Drop function it is recommended to set the area around the icon of the object as trigger.
It must be defined whether Drag and Drop should be enabled only in the list view or also in the tile view or not.

To visualize the "drop zone" it is recommended to use the variant as it is currently used for files, folders and courses.

The page editor with its movable elements can also serve as a model.

2.6 Across Browser Windows

If the drag and drop function also worked across browser windows, it would make it much easier to manage materials in sessions, e.g. to drag and drop materials from a previous course into the new session.

3 User Interface Modifications

3.1 List of Affected Views

• Course / Group / Folder: Content

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

The pattern drag and drop for files is already available for container elements in ILIAS and nothing new. The UI elements for the drop zone are already introduced in ILIAS.

But it is necessary to "attach" a trigger to ILIAS objects so that they can be packed and moved. This is not yet available in ILIAS.

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Seiler, Yvonne [yvseiler], Universität Bern
• 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.

• Universität Bern

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