KS-Entry: Novelty Counter

1 Guideline

• Name: Novelty Counter
• DOM, LESS, JS / Screenshot:

• PHP Class: None (!)
• PHP Example:
• External library: Bootstrap Badge
• Status of Entry: Proposed
• Status of Implementation: to be implemented
• Description:
  • Purpose: Novelty counters inform users about the arrival or creation of new items of the kind indicated by the accompanying glyph.
  • Composition: The Novelty Counter is an obtrusive counter.
  • Effect: They count down  / disappear as soon as the change has been consulted by the user.
• Background:
• Context: Novelty Counters are found in the Mail in the Top Navigation. Novelty Counters indicate new Comments.  
• Rules:
  • Usage:
    1. MAY be used together with the Status Counter.
  • Interaction:
    1. There MUST be a way for the user to consult the changes indicated by the Counter.
    2. After the consultation, the Novelty Counter SHOULD disappear or the number it contains is reduced by one.
    3. Depending on the content, the reduced number MAY be added in an additional Status Counter.
  • Style: 
    1. The Novelty Counter MUST be displayed on the top at the ‘end of the line’ in reading direction of the item it accompanies. This would be top right for latin script and top left for arabic script.  
    2. The Novelty Counter SHOULD have an obtrusive background color such as red or orange.
• Relations:
  • Is A: KS-Entry: Counter

2 To do for ILIAS 5.2

• KS-Todo: CounterGUI: The number for the Novelty Counter of the Comments Glyph can currently not be reduced even if the comments are consulted. They should be changed into the Status Counter. Better display all not consulted messages with the Novelty Counter and all other with the Status Counter.
• KS-Todo: CounterGUI: In ratings, the Novelty Counter is currently used to display the total amount of ratings, this should be done with a Status Counter.

3 Status

• Effective from release: ILIAS 5.2
  
• Approved by Jour Fixe at: JourFixe-2015-12-07
• Implementation status: needs implementation
  
• Funding for streamlining existing features: { name of organisation }
• Implementation of guideline: { all developers | name of responsible developer }

4 Components that are not compliant with the Guideline

• …

5 Discussion

JourFixe, ILIAS [jourfixe], Dec 07, 2015: Accepted by Jour Fixe. Related feature requests should be added to wiki (todo...) and presented to JF for final acceptance.