2 thoughts on “The lighter side of reporting”

  1. Hi Matt

    The adhoc tool and pentaho metadata look very useful and are certainly a great step forward for open source reporting.
    Does pentaho metadata take care of finding and warning about things such as fan traps and chasm traps in the abstraction layer?

    Thanks

    H

  2. Hi Hugo,

    That’s an excellent question. It would take us too far on this humble blog to explain everything, but the design idea behind Pentaho Meta Data is to allow the (ICT) designers to create small bite-sized data model snippets to exactly avoid those traps. We added an inheritance model in PMD to make management of those snippets easier.

    Looking at it differently I strongly believe that any semantic layer where a customer can’t just drag any and every single item on a report without getting in trouble, is not worth its money. In a former life I used to be somewhat of a Business Objects specialist and my finding was that reporting was way too hard using BO. The end users had to know far too much about the underlying data models to be able to create more complex reports. My conclusion back then was that self-service reporting was just not possible while using a single “Universe” view of the data warehouse.

    End-users should not have to know about any types of traps, contexts or whatever. They just want to report. PMD reflects that design decision in the Domain / View philosophy.

    HTH,

    Matt

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.