Variable Naming Conventions | GideonSoft Support
Welcome to our Knowledge Base
< All Topics
Print

Variable Naming Conventions

With the large number of data points gathered and analyzed in GideonSoft, utilizing a logical and consistent naming convention helps make reporting and analysis much more efficient. Variables must adhere to the standard hierarchical naming convention (Dimension, Factor, Sub-factor, and Item) used by the GideonSoft Whole Person model of human performance.

 

GideonSoft’s Variable Name Generator assists in the naming process, and attempts to help conceptually relate variables to each other and to the GideonSoft data model, using drop down suggestions.

  • Every Variable must have a unique Name. The Naming Generator will not allow a duplicate variable to be created.
    • Sometimes you may not need to name a variable using all four components. In these cases, it is a best practice to use zeros for each unused component.
    • When using the pop-up name generator, each of the four fields has a 10 character limit.
    • Other than the underscore character, special characters can be used, though it is recommended to use them sparingly as they can cause problems in data analysis and reporting tools.
  • Score variables also have a Label, which can be whatever you want. This is usually what is displayed in reports and analysis. This does not need to be unique, though we recommend making it clearly communicate the concept this variable represents.
  • Person variables do not have a Label, but do have a Description. This can be used to provide context or more information about the Descriptive.
  • Ultimately, it is important for you to maintain a standard naming convention that works best for you and your organization.

 

Here are some examples that  may guide you in developing your naming conventions:

 

Example 1:

  • You may have the following two questions on a supervisor (instructor/coach/etc) survey:
    • Question 1 Label = “Rate this student’s mental perseverance during event 01”, with a variable name of “BEHA_TOUG_MEPE_001”.
    • Question 2 Label = ”Rate this student’s mental perseverance during event 02”, with a variable name of “BEHA_TOUG_MEPE_002”.
      • BEHA = Behavioral (Dimension)
      • TOUG = Toughness (Factor)
      • MEPE = Mental Perseverance (Sub-factor)
      • 001, 002 = (Item)
  • A score variable that calculates an average of these ratings could be named “BEHA_TOUG_MEPE_SUP-AVG” with the label “Mental Perseverance Average Instructor Rating”.
  • The Label easily identifies the intended concept of the score variable, while the name ties the concepts to the GideonSoft data model:
    • BEHA = Behavioral (Dimension)
    • TOUG = Toughness (Factor)
    • MEPE = Mental Perseverance (Sub-factor)
    • SUP-AVG = Average of Supervisor ratings (Item)

Example 2:

  • You may have the following questions like this for an athlete’s strength test:
    • “Enter the athlete’s bench press”, and name the variable “PHYS_STRE_BENCH_001”.
      • PHYS = Physical Ability (Dimension)
      • STRE = Strength (Factor)
      • BENCH = Bench Press (Sub-factor)
      • 001= (Item)
  • A score variable that identifies the athlete’s current data could be named “PHYS_STRE_BENCH_MR” with the Label “Most Recent Bench Press”.
    • PHYS = Physical Ability (Dimension)
    • STRE = Strength (Factor)
    • BENCH = Bench Press (Sub-factor)
    • MR = Most Recent

 

Example 3:

  • Not all variables may be measured at the sub-factor level, therefore that section of the variable name may not be needed:
    • Peer Survey Question Label = “Rate this student’s Toughness during event 01”, with a variable name of “BEHA_TOUG_000_001”.
      • BEHA = Behavioral (Dimension)
      • TOUG = Toughness (Factor)
      • 000 = (No Sub-Factor Present)
      • 001 = Item
    • A score variable that calculates an average of peer ratings of the person’s toughness could be named “BEHA_TOUG_000_PEER-AVG” with the label “Toughness Average Peer Rating”.
      • BEHA = Behavioral (Dimension)
      • TOUG = Toughness (Factor)
      • 000 = (No Sub-Factor Present)
      • PEER-AVG = Average of peer ratings (Item)

 

By using consistent naming conventions, it becomes easier to see how Examples 1 and 3 could be rolled up into the Behavioral Dimension (and the Toughness Factor). So a score of Behavioral Toughness (“BEHA_TOUG_SUM”) might sum BEHA_TOUG_MEPE_SUP-AVG and BEHA_TOUG_000_PEER-AVG, which you could then use to rank everyone in that Instance.

 

 

= = = = =

Version(s): 17.2 and later

Table of Contents