We need a set o tools for monitoring user activities on a Plone site. This presentation is a quick overview on what we have now and what we want for the future.

1. Plone Analytics
A set of tools to analyze your Plone site usage
Simone Orsi - simone.orsi@abstract.it

2. Who Am I
Simone Orsi aka #simahawk
Python Web Developer
@ Abstract
Abstract for PLOG 2013

3. Customer needs: track users' activity.
● View users' last login time;
● View items published since users' last login;
● View items published since users' registration date;
● View items published between a specific date range;
● more?
Abstract for PLOG 2013

4. Customer needs: visualization and
manipulation.
● View / build graphics on users' stats;
● Export or expose data (CSV, XLS, JSON, etc)
Abstract for PLOG 2013

5. WHAT DO WE HAVE?

6. ALMOST NOTHING COMPLETE :)

7. collective.contentstats by Raphael Ritz
"A configlet for Plone showing some content statistics (type/state)"
Last release: 1.0.1 (2011-05-09)
Features:
● Works on catalog data exclusively - no content is touched;
● Only lists portal types that are used;
● Only lists review states used;
● Works with custom add-ons right away;
● Supports CSV export of summary data;
Limits: no search. Only display info on review state.
Abstract for PLOG 2013

8. collective.pygal.plonestats by Christian Ledermann
"collective.pygal.plonestats is mainly meant to demonstrate the
ease of use and integration of pygal into plone."
Last release: 0.1 (2012/04/02)
Features:
● Keywords;
● Content by Creator;
● Content by types;
● Review states;
● Created items by year;
● Created items by month;
Limits: no search. Prove of concept.
Abstract for PLOG 2013

9. quintagroup.analytics
"Plone site's statistics."
Last release: 1.1.1 (2012-05-31)
Features:
● Content Ownership by Type;
● Content Ownership by State;
● Content Types by State;
● Site Portlets;
● Legacy Portlets - information about legacy assigned throughout site sections;
● Properties stats - information on certain property values for all site objects, such as
titles, descriptions, etc.
Limits: no search. Some not-needed features.
Abstract for PLOG 2013

10. WHAT DO WE WANT?

11. Advanced search.
Search by:
● user properties (name, fullname, email, etc);
● date filter on range (compared to last login time, registration date, etc);
● content types;
● review state;
● path;
● more?
Abstract for PLOG 2013

12. Visualization.
Show:
● table;
● chart;
Some good starting point could be pygals and daviz.
Abstract for PLOG 2013

13. Export / Expose.
To:
● CSV;
● XLS;
● JSON;
● Open data;
Abstract for PLOG 2013

14. Flexibility.
● Add / remove columns to views and exported data;
● Custom visualization manipulators for converting
value / labels to be displayed;
● Custom export manipulators for converting value /
labels to be exported;
● Custom configuration of graphics (ala Daviz).
All of this should be possbile both from FS code and TTW scripting /
TALES expressions.
Abstract for PLOG 2013

15. Sprint.
The goal of the sprint is to come up with a draft of a suite of packages
for providing a pluggable set of tools.
1. indentify real must-have features;
2. outline architecture;
3. cherry picking features from existings packages;
4. code!
Abstract for PLOG 2013

16. QUESTIONS / SUGGESTIONS?

17. Thanks for your attention.
Simone Orsi
simone.orsi@abstract.it
@simahawk
#simahawk
Abstract for PLOG 2013