More self-determination and organisation in the dashboard

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

Some functions from the personal desk under ILIAS 5 are missing. In order to create a truly personal dashboard, further functions would be helpful.
 
1. Clean Dashboard
Some lecturers do not want to work with tasks and would like to hide this field in the dashboard. Especially since many of the task boxes are pretty empty and therefore unnecessary. Other lecturers do not require the news and some generally are confused by the many boxes on the Dashboard and so they only want to see the favourite objects.

-> For more self-determination in the dashboard, individual entries (whole blocks) such as calendar, tasks and news should be able to be hidden.
 

2. Sorting in favourites
For better organisation within the favourites some lecturers would like to have the most important and recent favourites at the top and the least important at the bottom.

-> For better organisation within the favourites, they should be sortable. Sortable in the dashboard and not only in the slate (https://docu.ilias.de/goto_docu_wiki_wpage_6295_1357.html


3. Useless/obsolete tasks
Courses/materials can still be relevant for exams after a year or more and so the courses are still online. In some cases, students have to ask lecturers to delete exercises or unpublished blog entries from this still needed but old online course.  

-> An entry already exists for this issue: Remove Tasks from Task List
https://docu.ilias.de/goto_docu_wiki_wpage_6354_1357.html
 

4. Sorting options in the tasks
Some tasks have a defined submission date, others are open. Sorting by type into with and without deadline would be helpful. For the tasks with a deadline, sorting by date would provide more clarity. So, the soon to be deadlines appear at the top. A manual sorting would allow personal weighting independent of the set deadline. 

-> For better organisation the task should be sortable by deadline and manual. 
 

5. Missing to-dos
I cannot create my own tasks (like milestones or calendar entries). (Milestones deadlines are also tasks but do not appear under the tasks!)

• Creating own entries in „tasks “.

2 Conceptual Summary

1. For more self-determination in the dashboard, individual entries (whole blocks) such as the calendar, tasks and news should be able to be hidden.
2. For better organisation within the favourites, they should be sortable. (https://docu.ilias.de/goto_docu_wiki_wpage_6295_1357.html    not only in the slate)
3. An entry already exists for this issue: Remove Tasks from Task List (https://docu.ilias.de/goto_docu_wiki_wpage_6354_1357.html)
4. For better organisation in the tasksthey need more sorting options
5. Missing tasks-> Creating own entries in „tasks “.

3 User Interface Modifications

3.1 List of Affected Views

• Dashboard
  
• Tasks
  

3.2 User Interface Details

3.2.1 Clean Dashboard „Ausblenden“ von Blöcken

The option "Hide" (Ausblenden) should appear in the actions menu of all dashboard elements. Here by the example of the tasks, the calendar, the news:

Here an ILIAS 5 GUI shows a hidden mailbox. The actions menu is available and the box can be displayed again via "Show mail / Mail anzeigen":

This should be implemented in ILIAS 7 again.

3.2.2 Sorting in favourites in the DASHBOARD

For the slate:
https://docu.ilias.de/goto_docu_wiki_wpage_6295_1357.html
Here for the Dashboard
The option of manual sorting in the actions menu via "Sort manually":

The manual sorting is then analogous to the sorting in the categories/courses. The position within the list is determined via numerical values:

3.2.3 For better organisation in the “Tasks” (To-Dos): sorting options

Sorting by type (with and without deadline) would be helpful. For the tasks with a deadline, sorting by date would provide more clarity. So, the deadlines that are due soon appear at the top. A manual sorting would allow personal weighting regardless of the deadline set. 
Actions menu in the dashboard:

Actions menu in the GUI Tasks/To-Do:

3.2.4 Creating own entries in the GUI „Tasks“

In the Dashboard, the new entry "Create Tasks" appears in the actions menu. In the tasks GUI, the actions menu would have to be inserted. Here, in addition to “Add entry”, “Sort by Date”, “Sort by Type” and “Remove Multiple Tasks” functions could appear. 

When a new task is created, users are directed to a new page:

3.3 New User Interface Concepts

Creating Tasks
The GUI Create New Task

In the GUI „Create New Task“ you can enter a title and an optional description for the user. An end date does not have to be entered (analogous to an unpublished blog post). If you want to enter an appointment, you have the choice between an all-day appointment or an appointment with a selected time (analogous to an appointment in the calendar). Similar to the links to the exercise or to the blog, the self-entered tasks should also be able to link to an ILIAS object. This is very useful for example, if a test has to be completed by day/time. The process of linking works like all internal linking. Its also possible to ad an description.

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ 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

{ 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: Nicole Haack CCE UzK
• 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.

• not funded yet

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