Wazimap profile curation handbook
  • Start Here
    • Introduction
  • Point Mapper
    • What is Point Mapper?
    • Shaping Data for Point Collections
    • Uploading Point Collections
    • Creating Themes for Profile Collections
    • Creating Profile Collections from Point Collections
    • Uploading additional points to an existing Point Collection
    • Editing existing Point Data in Django
    • Bulk updates to an existing point collection
    • Navigating Point Mapper
  • Profile Admin
    • Creating Datasets
    • Sub-Indicator groups (columns)
    • Creating Universes
    • Creating Variables
    • Creating Point Collections
    • Creating a Profile Highlight
    • Creating Profile Indicators
    • Creating a Profile Key Metric
    • Managing Categories and Sub-Categories
    • Managing Point Themes and Profile Collections
    • Profile configuration options
  • Curation Concepts
    • Geography Codes
    • Zero-values vs missing data
    • Glossary
  • Common practices
    • General
    • SANEF election dashboard
    • Africa Data Hub
    • Data handling tips
  • Promotion and usage
    • Analytics
Powered by GitBook
On this page
  • Reordering subindicators
  • Non-aggregatable columns

Was this helpful?

Export as PDF
  1. Profile Admin

Sub-Indicator groups (columns)

PreviousCreating DatasetsNextCreating Universes

Last updated 3 years ago

Was this helpful?

Reordering subindicators

It might be that you want to change the order in which the sub-indicators are shown. For example, you may want to swap Agree and Disagree in the chart below

In the Admin Suite, find SubindicatorsGroups

Find the relevant indicator:

Then drag the subindicators into the desired order:

The order should now be changed on the front-end. In order to see it you will need to hard-refresh your browser - ctrl + shift + R (this will be fixed soon).

Non-aggregatable columns

Values are summed over all dimensions other than the indicator variable by default. That means an indicator on the column "financial year" from a dataset with columns "financial year" and "income source" will disaggregate by financial year, and show the sum of the different income sources, unless the user adds a filter on income source.

It sometimes doesn't make sense to sum values over a dimension. For example

  • If you don't know how many years are in a dataset, the total across years doesn't mean anything

  • If your data contains overlapping categories to support differing standards, e.g. ages 15-24 and 15-35, summing over these would lead to double-counting.

You can mark a column as non-aggregatable by un-checking the Can aggregate check-box. It is checked by default as most columns are fine to aggregate over.

This will mean that indicators from this dataset will automatically have a filter for this subindicator group, unless this group is used as the indicator variable (in which case it is already disaggregated).

Unlike user-added filters, filters added to disaggregate non-aggregatable columns can not be removed.

You can . E.g. to ensure that the latest financial year is the default value filtered against. Users can still choose other options if they wish.

specify which value should be the default to be matched in the filter in indicator config
"Can aggregate" unchecked.
A filter for non-aggregatable "age goup" and user-added gender filter