|
Hi all,
I would like to migrate the "business intelligence" component ("bi") from framework to specialpurpose; in the process I would also like to migrate all the artifacts (dimension and fact entities and star schemas, and reports) from all the applications to the "bi" component. Then I would also like to set this component as "disabled" by default. When I initially design and contributed this component I have placed it in the framework to let application use some of its low level services to build their own reports: however over time I noticed that the need to configure the olap data model caused some confusion to users (especially the ones that do not use this feature); moreover, the definition of dimensions, facts and schemas is currently widespread over several components (whose boundaries don't match very well with the domains for business intelligence) and this makes more difficult to understand the bi data model. After the migration I am proposing here we will have all the bi data model in one place (the bi component). Regards, Jacopo |
|
Jacopo, all,
That is a good idea. This will bring everything (regarding BI - extensive reporting) to one place and it will surely help users and contributors to avoid looking all over the place when evaluating, implementing and/or extending the functionality. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Thu, Nov 20, 2014 at 10:44 AM, Jacopo Cappellato < [hidden email]> wrote: > Hi all, > > I would like to migrate the "business intelligence" component ("bi") from > framework to specialpurpose; in the process I would also like to migrate > all the artifacts (dimension and fact entities and star schemas, and > reports) from all the applications to the "bi" component. > Then I would also like to set this component as "disabled" by default. > When I initially design and contributed this component I have placed it in > the framework to let application use some of its low level services to > build their own reports: however over time I noticed that the need to > configure the olap data model caused some confusion to users (especially > the ones that do not use this feature); moreover, the definition of > dimensions, facts and schemas is currently widespread over several > components (whose boundaries don't match very well with the domains for > business intelligence) and this makes more difficult to understand the bi > data model. After the migration I am proposing here we will have all the bi > data model in one place (the bi component). > > Regards, > > Jacopo |
|
Administrator
|
In reply to this post by Jacopo Cappellato-4
+1 Sounds good to me
Jacques Le 20/11/2014 10:44, Jacopo Cappellato a écrit : > Hi all, > > I would like to migrate the "business intelligence" component ("bi") from framework to specialpurpose; in the process I would also like to migrate all the artifacts (dimension and fact entities and star schemas, and reports) from all the applications to the "bi" component. > Then I would also like to set this component as "disabled" by default. > When I initially design and contributed this component I have placed it in the framework to let application use some of its low level services to build their own reports: however over time I noticed that the need to configure the olap data model caused some confusion to users (especially the ones that do not use this feature); moreover, the definition of dimensions, facts and schemas is currently widespread over several components (whose boundaries don't match very well with the domains for business intelligence) and this makes more difficult to understand the bi data model. After the migration I am proposing here we will have all the bi data model in one place (the bi component). > > Regards, > > Jacopo > |
|
In reply to this post by Jacopo Cappellato-4
+1
Thanks -- Divesh Dutta On Thu, Nov 20, 2014 at 3:14 PM, Jacopo Cappellato < [hidden email]> wrote: > Hi all, > > I would like to migrate the "business intelligence" component ("bi") from > framework to specialpurpose; in the process I would also like to migrate > all the artifacts (dimension and fact entities and star schemas, and > reports) from all the applications to the "bi" component. > Then I would also like to set this component as "disabled" by default. > When I initially design and contributed this component I have placed it in > the framework to let application use some of its low level services to > build their own reports: however over time I noticed that the need to > configure the olap data model caused some confusion to users (especially > the ones that do not use this feature); moreover, the definition of > dimensions, facts and schemas is currently widespread over several > components (whose boundaries don't match very well with the domains for > business intelligence) and this makes more difficult to understand the bi > data model. After the migration I am proposing here we will have all the bi > data model in one place (the bi component). > > Regards, > > Jacopo |
|
In reply to this post by Jacopo Cappellato-4
+1
Adrian Crum Sandglass Software www.sandglass-software.com On 11/20/2014 9:44 AM, Jacopo Cappellato wrote: > Hi all, > > I would like to migrate the "business intelligence" component ("bi") from framework to specialpurpose; in the process I would also like to migrate all the artifacts (dimension and fact entities and star schemas, and reports) from all the applications to the "bi" component. > Then I would also like to set this component as "disabled" by default. > When I initially design and contributed this component I have placed it in the framework to let application use some of its low level services to build their own reports: however over time I noticed that the need to configure the olap data model caused some confusion to users (especially the ones that do not use this feature); moreover, the definition of dimensions, facts and schemas is currently widespread over several components (whose boundaries don't match very well with the domains for business intelligence) and this makes more difficult to understand the bi data model. After the migration I am proposing here we will have all the bi data model in one place (the bi component). > > Regards, > > Jacopo > |
|
In reply to this post by Jacopo Cappellato-4
+1
Makes perfect sense. Best regards, Pranay Pandey HotWax Media On 20 Nov 2014 15:16, "Jacopo Cappellato" <[hidden email]> wrote: > Hi all, > > I would like to migrate the "business intelligence" component ("bi") from > framework to specialpurpose; in the process I would also like to migrate > all the artifacts (dimension and fact entities and star schemas, and > reports) from all the applications to the "bi" component. > Then I would also like to set this component as "disabled" by default. > When I initially design and contributed this component I have placed it in > the framework to let application use some of its low level services to > build their own reports: however over time I noticed that the need to > configure the olap data model caused some confusion to users (especially > the ones that do not use this feature); moreover, the definition of > dimensions, facts and schemas is currently widespread over several > components (whose boundaries don't match very well with the domains for > business intelligence) and this makes more difficult to understand the bi > data model. After the migration I am proposing here we will have all the bi > data model in one place (the bi component). > > Regards, > > Jacopo |
|
In reply to this post by Jacopo Cappellato-4
+1 no more comments needed !
Le 20/11/2014 10:44, Jacopo Cappellato a écrit : > Hi all, > > I would like to migrate the "business intelligence" component ("bi") from framework to specialpurpose; in the process I would also like to migrate all the artifacts (dimension and fact entities and star schemas, and reports) from all the applications to the "bi" component. > Then I would also like to set this component as "disabled" by default. > When I initially design and contributed this component I have placed it in the framework to let application use some of its low level services to build their own reports: however over time I noticed that the need to configure the olap data model caused some confusion to users (especially the ones that do not use this feature); moreover, the definition of dimensions, facts and schemas is currently widespread over several components (whose boundaries don't match very well with the domains for business intelligence) and this makes more difficult to understand the bi data model. After the migration I am proposing here we will have all the bi data model in one place (the bi component). > > Regards, > > Jacopo |
|
In reply to this post by Jacopo Cappellato-4
Hi,
+1 And thanks for the explanation and history ! To have it as an option is great ! Gil On 20/11/2014 10:44, Jacopo Cappellato wrote:
--
|
|
In reply to this post by Jacopo Cappellato-4
+1
Thanks Sharan |
|
In reply to this post by Jacopo Cappellato-4
Thanks for the feedback, I did the refactoring in rev. 1642027
Jacopo On Nov 20, 2014, at 10:44 AM, Jacopo Cappellato <[hidden email]> wrote: > Hi all, > > I would like to migrate the "business intelligence" component ("bi") from framework to specialpurpose; in the process I would also like to migrate all the artifacts (dimension and fact entities and star schemas, and reports) from all the applications to the "bi" component. > Then I would also like to set this component as "disabled" by default. > When I initially design and contributed this component I have placed it in the framework to let application use some of its low level services to build their own reports: however over time I noticed that the need to configure the olap data model caused some confusion to users (especially the ones that do not use this feature); moreover, the definition of dimensions, facts and schemas is currently widespread over several components (whose boundaries don't match very well with the domains for business intelligence) and this makes more difficult to understand the bi data model. After the migration I am proposing here we will have all the bi data model in one place (the bi component). > > Regards, > > Jacopo |
| Free forum by Nabble | Edit this page |
