Show Advanced KnowledgeHide Advanced Knowledge

Statistics of Views of Terms

1 Initial Problem

Understanding how often and long individual terms in a glossary are visited is not possible. However this information is valuable for further developing the content. 

2 Conceptual Summary

A new tab 'Statistics'. This tab should offer a table listing all terms of this glossary. 

• Usage (on per default)
• ∑ Users (on per default)
• ∑ Access Number (on per default)
• Ø Access Number / User

There is no need to track individual people. 
The columns can be shown or hidden. 

• What is about virtual glossaries? Will those terms be counted here? How about the views in those other contexts? 
• Is it neccessary to abandon the Presentation Mode "Table Form"? If not: how can accesses be counted if all ist presented on the same screen? 

3 User Interface Modifications

3.1 List of Affected Views

• New tab statistics

3.2 User Interface Details

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 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: {Please add your name.}
• 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}.