There are some areas that try to anonymise data, we should add some support for this directly into the event base class.

There are multiple potential problems and questions such as:

• should we add new property and column to the log stores?
• do we need dynamic anonymous calculation based on userid/caps?

Possible solutions:

1/ add event::was_anonymous() method - the problem is that we may not have enough information to decide who can see what, also this would not work for deleted activities, also the data can be easily disclosed by filtering reports, expensive, cannot work in external systems that have access to data only

2/ add event->anonymous property and database table column - fast, simple and reliable, access needs to be granted at the report level if necessary, cannot change in time

3/ another option is to add PAGE->set_anonymous() and copy the value to the default in each event. See comment at https://moodle.org/mod/forum/discuss.php?d=256614 by Mark.