Show Advanced KnowledgeHide Advanced Knowledge

Usability Improvement of Trash

1 Initial Problem

Finding an object some specific user deleted is taking ages. The info is not available but only a location-based approach can be taken. 

2 Conceptual Summary

The section "Repository, Trash and Permissons" should be re-labeld to "Trash". 

The Trash should bet a new tab that is not goverened by the repository tree but displays a flat list that presents deleted objects. The title of the Table should be Trash. As the User Accounts table it should be limited to 800 entries max.  The flat list should include parent containers and encompassed children as individual and separate entries. 
The flat list should offer a column Path. The column Path presents the title of the immediate parent object followed by (deleted) if the immediate partent was deleted.

There is a need for a flat list in the Trash offering cloumns

• Deleted by (searches only Login)
• Deleted on

It should be possible to filter the new list. Filters should be 

• Deleted by (searches only Login)
• Deleted on
• Object Type 
• Title

If the flat list includes all deleted objects and not only containers, then it might occur that one chooses to restore an encompassed objekt WITHOUT restoring the encompassing container. The user deleting the object has to select a new repository location because the old location does not exist anymore. 
A new function Restore to New Location is required to restore a deleted object which resided in an encompassing container that was deleted as well but is not restored along with it's child.  A respository selector has to be presented to select a target container.

Several conflicts may occur

• Many objects are checked in the flat list, some have valid parents some do not. A simple "Restore" is not possible. A message is presented "You selected objects that cannot be restored to their original location, because their parent objects were deleted. Please uncheck the respective object in the table or select the Restore to New Location instead." 
• Furthermore "Restore to New Location" for multiple objects in ONE step is permitted only for objects not containing each other.

3 User Interface Modifications

3.1 List of Affected Views

• General Administration > Repository Trash and Permissions > List of Trash Objects (new)

3.2 User Interface Details

3.3 New User Interface Concepts

none.

4 Technical Information

5 Contact

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

• Helmut-Schmidt-Universität / Universität der Bundeswehr Hamburg

7 Discussion

Meyer, Stefan [smeyer], 08 Oct 2018: I support this request but want to discuss the following changes

Currently no information is stored who deleted an object. The username of the person who deleted the object should be stored in the database.

• To receive more predictable results the filter elements shouldn't search in multiple fields
  • Login (deleted by) searches login only
  • Title searches only for the title of the deleted object
• An additional filter "Period of deletion" should allow filtering by "Delete date"
• The column "Last Change" could be deleted.
• An additional column "subitems" shows the number of subitems of the object (container).
• The title column additionally presents the path (breadcrumb) of the location of the deleted object

The view "Restored Objects" will remain unchanged.

JourFixe, ILIAS [jourfixe], 08 OCT 2018 : We appreciate this improvement of the trash in general, incl. Stefan's additional suggestions. But have an open issue with the presentation of the feature in the current administration node for "Repository..." because the list of trash objects is outside the current tree-oriented view of the feature. We might need to move the current tabs to sub-tabs and introduce two new tabs "Tree View" and "List of Trash Objects". Matthias and Stefan will discuss a possible solution and add the proposal to the agenda again once a solution is available. Additionally, a solution for presenting the breadcrump per object within the table is necessary.

Lauener, Hansjörg [lauener], 1. Feb 2019: Highly appreciated. Additionaly, a "repository-tree filter" would be helpful. Our teacher do know in which course they deleted an object, but they do not remember exactly the name of the object.

JourFixe, ILIAS [jourfixe], 11 FEB 2019 : We highly appreciate this suggestion and schedule it for ILIAS 6.0 with the following changes:

• the view for tab "Trash" needs a tab navigation, too
• for the "Repository View" we prefer to have the sub-tab labels "Existing Objects" and "Deleted Objects" and the page title " Existing / Deleted Objects at Node 'XYZ' "

JourFixe, ILIAS [jourfixe], 23 SEP 2019 : We accept the suggestion to merge the view of objects in trash of current node and of current node and below by adding an additional filter setting "Show only deleted objects of this node". This filter should be off by default. Navigation through tree and trash should only be the tree in slate (no repository picker to prevent concurrent navigation patterns). Please clarify labels: better say "Deleted objects in and below "Repository"" for example.

Mela, Alix [ILIAS_LM] 2019-11-11:
Argh, I am too late... As we often have to restore objects people deleted accidentally it would have been nice, the trash bin would be accessible in the repository(, too?). So a course administrators would be able to restore their deleted file in the course themselves.
But maybe this will be considered in a follow-up! :-)

To the current feature: I am happy we finally get names and filters! (Admins often blame other people to delete their stuff... ;-)) So thank you, Helmut-Schmidt-Universität Hamburg.

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed on 2019-10-11 byTödt, Alexandra [atoedt]

• 31908 : Papierkorb öffnen
• 31909 : Papierkorb filtern
• 31910 : Objekte am Originalort wiederherstellen
• 31912 : Objekte vergeblich versuchen am Originalort wiederzuherstellen

Approval

Approved at 24.10.2019 by Uwe Tesche (Helmut-Schmidt-Universität Hamburg).