Transfer Repository to KS Tree

1 Initial Problem

With the page layout revision a new tree was introduced (e.g. see Media Pool, Tree for General Layout and Menu Revision). The repository tree could not yet be transferred, because some features of the current tree are not yet available in the new tree.

2 Conceptual Summary

The following missing functions should be added to the new tree so that the current repository tree can be transferred:

• Search function within a tree
• Show more action after a certain number of objects

2.1 Limit Items in Tree

With the function "Limit Items in Tree" the number of displayed items in the tree can be limited. A search field under the main node allows you to search for and find specific (now not displayed) items.

Once the search has been started, only the results relating to these keywords will be displayed below.

Settings: Administration > Repository and Objects > Repository > Settings

Behaviour until now

FW: Tree Behavior for Categories with Huge Amounts of Data

3 User Interface Modifications

3.1 List of Affected Views

• Repository > Tree View

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

Uses KS Tree element.

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, Zenzen, Enrico [ezenzen]
• 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.

• …

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