Naming conventions for measures
Hi all,
PowerBI autodidact here working as a PowerBI guy for a small government inspection/authority. My analyses help inspectors supervise their domain with kpi, general domain statistics and signaling trends and outliers. Most numbers and visuals answer "how many X in the last Y days/months have occurred in domain Z", "TopN occurances in sector X", "average number of days past since Y"
For archival purposes and being able to hand over my work to others, I wanna up my naming conventions for DAX measures, while making most of the folder/subfolder options as well.
Main purpose is to able to recognise what a measure does by name and/or what folder it is in. I think I'm kinda on my way with by always starting with a collection of general aggregates of the main things I consider relevant to my model. I'll start my naming my measure with a general domain of said aggregate, abbreviates in 2 or 3 digits, then the actual column of unit that is being aggregated in full or PascalType, followed by an abbreviation of the aggregation type.
Starting with an 01 Main folder: "Inc_Incidents_Dcnt" for in the domain of incidents, this counts the distinct number of incident codes "Loc_InvolvedLocations_Dcnt" for the domain of locations, this dcounts the number of distinct locations an incident has occurred. "Inc_DelayedResolve_Sum" for the total number of days between an incident occuring and being resolved. This is the kind of measure that will get filtered down a lot into specific contexts like departments, time periods, incident types, etc.
Second, I'll go 02 Main measures time. Basically all the main measures, but with a particular timeframe filtered. Like "Inc_DelayedResolve_Sum_L30D", see above, but for the last 30 days.
Then I'll go 03 Department folder, where all my main and time measures get filtered for particular contexts, like a particular department or sector. Like an 03 Department folder / HR where a measure would be like "Loc_InvolvedLocations_Dcnt_L30D_HR", see above, but for all locations where HR is involved/relevant (as filtered through a relevant dim_Table).
I think I'm still missing something, like a way to recognize the distinction between general (fixed, non responsive to slicers) measures and context measures (those that respons to slicers). But adding another abbreviation as a prefix or suffix will bloat the measure-naming, won't it?
Am I on the right track or am I missing something blatantly obvious? Do you know any recourses for inspiration?