Hitachi Vantara Pentaho Community Forums
Results 1 to 4 of 4

Thread: [Mondrian] Using global dimension, but applying local level names

  1. #1
    Diethard Steiner Guest

    Default [Mondrian] Using global dimension, but applying local level names

    Hi,
    It's extremely convenient to use global dimensions. In my case, I have one
    global date dimension and reuse it about 28 times.
    The problem though is, that while I can assign a local dimension name, the
    levels will still have the same name as the global level name.

    In example:
    global:
    Date/Monthly Calendar/Year/Month/Day in Month
    local:
    Registration Date/Monthly Calendar/Year/Month/Day in Month

    What I'd like to see in a GUI like Analyzer is:
    Registration Date/Registration Date - Monthly Calendar/Registration Date
    - Year/Registration Date- Month/Registration Date - Day in Month

    Otherwise if somebody does a search for month, they will get returned 28
    "months" ... so there is not way to differentiate them ("Registration Date
    - Month", "Cancellation Date - Month" would be more meaningful).

    Is there a way to achieve this by making some modifications to the schema?
    Thanks,
    Diethard

    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  2. #2
    Julian Hyde Guest

    Default Re: [Mondrian] Using global dimension,but applying local level names

    No way to do that currently.

    A few thoughts.

    1. The following Mondrian feature would solve the problem. Allow details of a dimension to be changed when it is used. For example,

    <DimensionUsage source='Time' name='Registration Date'>
    <Hierarchy name='Monthly Calendar'>
    <Level source='Year' caption='Registration Date - Year'/>
    <Level source='Month' caption='Registration Date - Month'/>
    <Level source='Day in Month' caption='Registration Date - Day in Month'/>
    </Hierarchy>
    </DimensionUsage>

    Note that this doesn't fully re-specify the dimension, just allows you to override particular metadata attributes.

    If you think this would help, please log a jira case.

    2. It also doesn't seem appropriate for Analyzer to assume that level names are unique within a cube. Maybe it should qualify them if the levels being displayed are not unique. Benny, what do you think?

    3. A cube that has 28 uses of the same global dimension has some issues. Is this a hacky workaround to some other problem or missing feature? What's the underlying problem.

    Julian


    On Nov 3, 2011, at 6:47 AM, Diethard Steiner wrote:

    > Hi,
    > It's extremely convenient to use global dimensions. In my case, I have one global date dimension and reuse it about 28 times.
    > The problem though is, that while I can assign a local dimension name, the levels will still have the same name as the global level name.
    >
    > In example:
    > global:
    > Date/Monthly Calendar/Year/Month/Day in Month
    > local:
    > Registration Date/Monthly Calendar/Year/Month/Day in Month
    >
    > What I'd like to see in a GUI like Analyzer is:
    > Registration Date/Registration Date - Monthly Calendar/Registration Date - Year/Registration Date- Month/Registration Date - Day in Month
    >
    > Otherwise if somebody does a search for month, they will get returned 28 "months" ... so there is not way to differentiate them ("Registration Date - Month", "Cancellation Date - Month" would be more meaningful).
    >
    > Is there a way to achieve this by making some modifications to the schema?
    > Thanks,
    > Diethard
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian


    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  3. #3
    Diethard Steiner Guest

    Default Re: [Mondrian] Using global dimension,but applying local level names

    Hi Julian,
    Many thanks for your feedback! Suggestion (1) looks good to me, I'll set up
    a jira case.
    Ok, 28 was a bit exaggerated , but it's quite high. There is quite a lot
    of date related user profile data in my example (registered, cancelled,
    etc).
    Thanks,
    Diethard

    On Thu, Nov 3, 2011 at 5:25 PM, Julian Hyde <jhyde (AT) pentaho (DOT) com> wrote:

    > No way to do that currently.
    >
    > A few thoughts.
    >
    > 1. The following Mondrian feature would solve the problem. Allow details
    > of a dimension to be changed when it is used. For example,
    >
    > <DimensionUsage source='Time' name='Registration Date'>
    > <Hierarchy name='Monthly Calendar'>
    > <Level source='Year' caption='Registration Date - Year'/>
    > <Level source='Month' caption='Registration Date - Month'/>
    > <Level source='Day in Month' caption='Registration Date - Day in Month'/>
    > </Hierarchy>
    > </DimensionUsage>
    >
    > Note that this doesn't fully re-specify the dimension, just allows you to
    > override particular metadata attributes.
    >
    > If you think this would help, please log a jira case.
    >
    > 2. It also doesn't seem appropriate for Analyzer to assume that level
    > names are unique within a cube. Maybe it should qualify them if the levels
    > being displayed are not unique. Benny, what do you think?
    >
    > 3. A cube that has 28 uses of the same global dimension has some issues.
    > Is this a hacky workaround to some other problem or missing feature? What's
    > the underlying problem.
    >
    > Julian
    >
    >
    > On Nov 3, 2011, at 6:47 AM, Diethard Steiner wrote:
    >
    > > Hi,
    > > It's extremely convenient to use global dimensions. In my case, I have

    > one global date dimension and reuse it about 28 times.
    > > The problem though is, that while I can assign a local dimension name,

    > the levels will still have the same name as the global level name.
    > >
    > > In example:
    > > global:
    > > Date/Monthly Calendar/Year/Month/Day in Month
    > > local:
    > > Registration Date/Monthly Calendar/Year/Month/Day in Month
    > >
    > > What I'd like to see in a GUI like Analyzer is:
    > > Registration Date/Registration Date - Monthly Calendar/Registration Date

    > - Year/Registration Date- Month/Registration Date - Day in Month
    > >
    > > Otherwise if somebody does a search for month, they will get returned 28

    > "months" ... so there is not way to differentiate them ("Registration Date
    > - Month", "Cancellation Date - Month" would be more meaningful).
    > >
    > > Is there a way to achieve this by making some modifications to the

    > schema?
    > > Thanks,
    > > Diethard
    > > _______________________________________________
    > > Mondrian mailing list
    > > Mondrian (AT) pentaho (DOT) org
    > > http://lists.pentaho.org/mailman/listinfo/mondrian

    >
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian
    >


    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  4. #4
    Julian Hyde Guest

    Default Re: [Mondrian] Using global dimension,but applying local level names

    On Nov 3, 2011, at 11:04 AM, Diethard Steiner wrote:

    > Many thanks for your feedback! Suggestion (1) looks good to me, I'll set up a jira case.


    I saw you logged http://jira.pentaho.com/browse/MONDRIAN-1035. Thanks for that.

    Julian


    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2017 Pentaho Corporation. All Rights Reserved.