Closed rlaemmel closed 11 years ago
Perhaps, we should take the view that "age" and "gender" as data fields are an integral part of the report feature rather than a) making it part of the basic data model or b) having an extra data extension feature (extra from basic data model and the bonus feature).
@ydupont also agreed, I think :-)
Perhaps we could package up the report feature also to add job roles (see #49) because it may not be very interesting to have this as a separate feature. If we do this, then, of course, the reporting feature would need to do something with job roles (even if it is trivial).
Over to @ydupont
I need reporting for the fpcourse and accordingly get started on this. @ydupont let's chat soon to see how we move towards closure of this feature. Shouldn't be too hard.
I checked pyplot last week and created a sample implementation using MySQLOne which looked quite promising. Tomorrow I will attend to the meeting so we can discuss further.
Sounds good.
This is the base feature for reporting.
http://101companies.org/wiki/Feature:Reporting
Working on the subfeature "Grouping".
Looking at everything you wrote and the notes from the subbotnik.
Some sort of report such as ...
Some sort of grouping or categorization, e.g., by ...
Some candidate proposals:
We might position some of this already as BI. This could also be used a starting point for data warehousing, if then the timeline is perhaps added additionally.
Sort of related: #45