nmcdavid
commented
1 year ago @baboyma - responses in bold
Consider replacing < with lt (eg: lt3m) and + with gt eg:(gt6m). You don't want the "<" or "+" in the wide template headers.
- is this for the variable name in the wide templates in rows 1 and 3 or the variable labels in Row 2? We can abbreviate the < and + in the variable names (rows 1 and 3) if it's more useful on the processing side. I don't think it would be a good idea to use the abbreviations in the variable labels since that could make interpretation harder for users
- For substitutions we've used <=u for under, +=o for over. will also be consistent with HFR templates and a bit more intuitive
Also remove "supported" from non-PEPEFAR and PEPFAR options. "supported" is inherited from the Disagg Group says (Key Pop/Site Support Type).
- I opted to keep "supported" so that it's consistent with the nomenclature in the Ind Ref Guide and users wouldn't get confused. Happy to drop if it's okay with @BBetz907
Could also remove "Site" from "Key Pop/Site Support Type" and change "Key Pop" to "KeyPop" Note: this column seems to be an exact copy of "other disagg".
- I think it might be best to keep "Site" here since "support type" can refer to a site support type or program support type.
- Can definitely remove the space in "Key Pop". I think that's consistent with MSD
- @baboyma Which column is the exact copy of "other disagg"? Population drop-down options should only the key pop groups. I might have to correct the drop down lists if there are errors
Consider using a modified version of Other disagg (trimmed). Eg: "Individual models - Community based" => Ind-Mod-Com. You don't want the non-word characters in the header: eg: <, +, /, ', ), (, etc. Exception: -, _ and .
- if this is for rows 1 and 3 in the wide templates we can consider abbreviations for the variable names. I would opt out of using trimmed other disaggs for variable labels (wide row 2 or drop downs in the long and semi-wide) to avoid misinterpretations. some country teams use the templates for other analysis and worry using abbreviations/modifications in variable labels could encourage confusion
- Will replace <=u for under, +=o for over, /=_, ( = remove from variable name and opt for abbr, ) = remove from variable name and opt for abbr.
BBetz907
Consider replacing < with lt (eg: lt3m) and + with gt eg:(gt6m). You don't want the "<" or "+" in the wide template headers.
Also remove "supported" from non-PEPEFAR and PEPFAR options. "supported" is inherited from the Disagg Group says (Key Pop/Site Support Type). Could also remove "Site" from "Key Pop/Site Support Type" and change "Key Pop" to "KeyPop" Note: this column seems to be an exact copy of "other disagg".
Consider using a modified version of Other disagg (trimmed). Eg: "Individual models - Community based" => Ind-Mod-Com. You don't want the non-word characters in the header: eg: <, +, /, ', ), (, etc. Exception: -, _ and .