Feature Wiki
Tabs
Rearrange Calendar Selection
Page Overview
[Hide]This feature request is a part of the Calendar Revision II.
still in progress
1 Initial Problem
In courses and groups, the calendar is activated by default. As a result, the personal calendar (Personal Desktop > Calendar) can contain course and group calendars that do not contain appointments.
The problem here is the lack of clarity in the "Calendar Selection" list:
- You have a large list of calendars, but they are not really in use (no appointments, last appointment in the past, f.e. past courses).
- Calendars that are in use (i. e. containing current or future appointments) disappear in such a long list and are hard to find.
The aim is to offer possibilities to navigate through the large list of personal, course and group calendars faster.
2 Conceptual Summary
- do not display calendar categories in calendar selection without any item.
- Possible solution: Deactivate Calendar in Course, if not in use??
- E.g. Personal Desktop / Calendar / Selection of Calendars on the right
Currently,
- calendars are divided into a "personal" and "other" group (in addition, there are "Consulting Hours" and "Current Course/Group" group in courses/groups).
- Within these groups the calendars are sorted alphabetically.
- The icons indicate whether it is a course or group calendar.
- Selection can be changed between "Selected Items" and "My Memberships".
Evt. arrangieren wie in Repository?
2.1 Collapsible Groups
To get a better overview of the existing calendar groups (personnel, others), these are to be defined as collapsible items (similar to taxonomies).
2.2 Division of "Other" Group
The group "Other" should be divided into two groups:
- Present (means "Current or future dates available")
- Past (means "No current or future dates")
3 User Interface Modifications
3.1 List of Affected Views
- Personal Desktop > Calendar
- Course > Calendar
- Group > Calendar
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
{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}
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: Seiler, Yvonne [yvseiler], Amstutz, Timon [amstutz], 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.}
6 Funding
If you are interest in funding this feature, please add your name and institution to this list.
- …
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}.
Last edited: 26. Apr 2018, 14:11, Seiler, Yvonne [yvseiler]