Project

General

Profile

Feature #2

Notification for new feedback

Added by Stefaan Vanbillemont almost 10 years ago. Updated about 7 years ago.

Status:
New
Priority:
Low
Assignee:
-
Start date:
16/10/2009
Due date:
% Done:

0%

Estimated time:
Complexity:
Normal

Description

Extend the "what's new"-functionality to show a icon if there is new feedback added to a content object publication.

History

#1

Updated by Sven Vanpoucke almost 10 years ago

  • Assignee set to Sven Vanpoucke
#2

Updated by Yannick Warnier almost 10 years ago

Please make sure you consider efficiency as a main priority here. If we want to show what's new to someone since his last visit, and have to see first if the visitor has access to the object (before showing anything), then the time taken by the whole query might be a real problem.

Ordering the objects by modification date, using the user's last connexion time then filtering it by access would probably reduce the query to a relatively small list of objects, but only the objects IDs should be returned to PHP (to avoid overloading the network in case of a remote MySQL server). Probably a good place to implement a stored procedure, if this is possible with MDB2 (apparently possible through executeStoredProc(), but possibly limiting the number of database systems that can be used with the system). Stored procedures greatly improve query execution times.

#3

Updated by Sven Vanpoucke over 9 years ago

I do think this can be a problem because now when there are new publications we only have 1 icon per tool that has new publications. It redirects then to the tool, not to the publication. If we need to check if there is a new feedback for EACH and EVERY publication and need to make an icon to that publication we'll have to much icons in our list.

Though we could extend the check to show an icon if either a publication has changed, or a feedback has been given to the publication. This icon will still redirect to the tool itself and thus making sure that only as many icons can be shown in the list as there are tools (instead of publications which could raise to thousands)

#4

Updated by Sven Vanpoucke over 9 years ago

  • % Done changed from 0 to 20

Prepared the feedback system to have a modification and creation date so we can check on these dates for new notification
http://websvn.chamilo.org/revision.php?repname=Chamilo&rev=23421

#5

Updated by Sven Vanpoucke over 9 years ago

  • Assignee deleted (Sven Vanpoucke)
#6

Updated by Stefaan Vanbillemont over 8 years ago

  • Project changed from Chamilo LCMS Connect to Repository
  • Category deleted (22)
#7

Updated by Stefaan Vanbillemont over 8 years ago

  • Target version changed from 7 to 2.1.0
#8

Updated by Stefaan Vanbillemont about 8 years ago

  • Target version changed from 2.1.0 to 55
#9

Updated by Stefaan Vanbillemont about 8 years ago

  • Target version changed from 55 to Backlog (default)
#10

Updated by Stefaan Vanbillemont about 7 years ago

  • % Done changed from 20 to 0

Also available in: Atom PDF