Do you know how your repository is used?

Does your Alfresco repository support a business process? Is it a collaboration environment? Do people use it as you intended? Who use it? Do users just create, or do they modify content too? For each Site, who are top-contributors? Which Sites store most MegaBytes? When was content (in a Site) last created/modified? How many cases of type XYZ are rejected every month?

Business Reporting is for the Business

Business Reporting should be handled by the Business. Therefore reporting should use an existing tool and plain and simple SQL. Currently, reporting in Alfresco is not that easy, and many alternatives are tech-driven. This project allows the business to use their reporting suite of choice against 'plain tables' containing your Alfresco business objects. As a 'proof', Pentaho Reporting and JasperSoft (iReport) reports are supported to generate reports, on a regular automated manner (if you like). But feel free to use any BusinessObjects, Cognos, Clickview.

This project is build on 2 parts.

1. Generate a reporting database based on business entities like Document, Case, Folder, Site etc. Each of these entities should contain all possible attribute values (even with Alfresco's Aspect feature providing flexible, runtime extensions) This reporting database can be filled from scratch, or incrementally since last update. Any Lucene query can define the content of the tables. (Think Aspects, Types, property values.)

2. Given a reporting database, report execution can be scheduled. The result can be a pdf, xls or html file that will be stored in the Alfresco repository. Currently Jasperreports and Pentaho reporting are supported reporting engines.