Opened 6 years ago

Last modified 5 years ago

#237 new Task

Common Dimension Names and Values

Reported by: Garth Braithwaite Owned by:
Priority: -Low Milestone: Unassigned
Component: Content Version: 3.0
Severity: Unknown Keywords:
Cc:

Description (last modified by Garth Braithwaite)

This ticket is to make sure that adopters understand when and why they want to name dimensions (name and values) the same and when not to.

When and Why to Name Dimension Names and Values the Same

The main reason to do this is that it provides a user the ability to apply a saved query definition to other query module criteria definitions and display selections. This makes it easier to do studies. This may or may not be more difficult for the backend IBISQ def and mappings - will depend on how the data are stored in SAS. For example all YEAR dimensions should have the same "Year" name and the same #### values. This makes it possible to apply a set of year selections to any query module.

From the release notes:

Added an enhanced query module “ibis:include” template that allows a developer to specify which configuration name(s) are associated with the include. If the “configuration-name-list “ attribute exists then the selected, current configuration name MUST match a name in the list. If no list attribute is specified then the include mechanism will work as normal with that file being included for all configuration names within that file. The list attribute can contain one configuration name or a list of comma and/or space separated configuration names. This provides a new mechanism to control dimension and section inclusions and allows common DIMENSION/NAME to be implemented within a given query module file that has multiple configurations with each configuration needing a different dimension value list. Put another way this provides a way to have commonly named dimensions that was not otherwise possible using the exclusion mechanism.

Usage Example (include different year XML files for different configurations within a given query module file) : <ibis:include href=”dimension/year_1980-2020.xml”

configuration-name-list="Count, Percent"

/> <ibis:include href=”dimension/year_even.xml”

configuration-name-list="Rate"

/>

In the above example the filenames are named uniquely (as they are now). The difference is that the 2 file's DIMENSION/NAME values are both "Year" with the values being a different list of same value type.

The current way the that the DIMENSION/NAME matches its filename

value. So the DIMENSION/NAME's of both are unique where as the new way they are the same but only included when the configuration name matches.

The conditional inclusion is probably a much cleaner solution when compared to the configuration exclusion mechanism. For "year" type dimensions this probably simplifies things. For others I'm not sure - it will be case by case.

When and Why to Name Dimension Values Different

The only reasonable use case is that there is too much content already developed and there is not enough time to refactor and test the changes.


NOTE: In an email that Garth sent 3/23/13, he stated that dim values might need to be unique across all dim values. This is NOT the case. The optional AUTHORITY element is attached the DIMENSION/VALUE element. The AUTHORITY for that module's dim value must be unique across ALL authorities in ALL QM dimension values but the dimension value can be generic.

Change History (9)

comment:1 Changed 6 years ago by Garth Braithwaite

Description: modified (diff)

comment:2 Changed 6 years ago by Garth Braithwaite

Description: modified (diff)

comment:3 Changed 6 years ago by Garth Braithwaite

Description: modified (diff)

comment:4 Changed 6 years ago by Garth Braithwaite

Description: modified (diff)
Summary: Record Level Security and Common Dimension NamingCommon Dimension Names and Values

comment:5 Changed 6 years ago by Garth Braithwaite

Description: modified (diff)

comment:6 Changed 6 years ago by Garth Braithwaite

Description: modified (diff)

comment:7 Changed 6 years ago by Garth Braithwaite

Component: View-AppContent
Type: IssueTask
Version: 2.2

comment:8 Changed 5 years ago by Garth Braithwaite

Version: 2.3

comment:9 Changed 5 years ago by Garth Braithwaite

Version: 2.33.0
Note: See TracTickets for help on using tickets.