Feature Wiki

Information about planned and released features

Tabs

DataCollection: Multiple Views for a DataCollection Table

Page Overview

1 Requirements
2 Additional Information
3 Discussion
4 Implementation

1 Requirements

A DataCollection table has the possibility to define, which fields should be listed in the table filter and appear as column.

We like to enhance this. It should be possible to define "Views" for tables. With "Views" it would be possible to configure more than one appearance for a table.

A "View" should have the following configurations possibilities

View Permission for Roles
Show / Hide in Table View-Selector

A "View" should have a direct link.

Relations

The following Feature-Requests are related to this, since they would be implemented as part of one concept (see below):

Concept_TableViews

2 Additional Information

Idea / concept: Martin Studer ms@studer-raimann.ch
Interest in funding: PHBern (partly funded)
Maintainer: (will be set by Jour Fixe / maintainer)
Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

Amstutz, Timon [amstutz] 31. March 2016: Please provide a few more details. How would one create multliple views? How are views to display selected? How does a user open a new view while seeing the table? Where are the settings entered for a specific view?

This FW needs some more conceptual work. If you are interested in funding the feature or the concept, please contact ms@stude-raimann.ch

JourFixe, ILIAS [jourfixe], May 23, 2015: Martin presented us the concept of the multiple views for a DC table (see PDF above). We see the need of this extension but have some questions:

We would like to have a clear vision on how the Detailed View is tackled by this concept: does every table view gets a proper detailed view (and is it edited in the table view settings?) Or do I assign an existing detailed view with one or more table views? How do we handle permalinks to detailed views if detailed views are role-sensitive?
The screen on page 11 has to be separated into one for the form and one for the table to avoid two submit buttons.
Martin and Matthias will have a VC to find a solution and present it at the next JF.

Studer, Martin [mstuder], Jun 02, 2016: Added new version of concept: Konzept_Table-Views_0_2.pdf

Studer, Martin [mstuder], [ttruffer] Jun 20, 2016: Added new version of concept: Konzept_Table-Views_1-1.pdf

JourFixe, ILIAS [jourfixe], June 20, 2016: Martin gave an follow-up and presented solutions for the open issues mentioned by JF. We highly appreciate this feature and schedule it for 5.2.

4 Implementation

The implementation diverges slightly from the concept since the structure of the GUI has changed with Feature Request Data Collection - Clear Distinction Between Table And Field Managing. However, this only concerns the navigation to the view management and doesn't change any functionality or usability. To understand the new navigation, read the mentioned FR.

Functionality

A precise description of the functionality can be found in the concept above. This is just an overview:

Add different views to a table and manage them (naming, ordering)
Define roles for each view, which will be granted access to this view
Define (for a view) for each field of the table: visibility, filterability, standardvalue of filter, changeability of filter
Create a detailed record view for each view

The ordering defines, which view will be shown by default.

A table cannot be 'shown' anymore, only its views. Therefore, each table contains at least one view.