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
  • Formatting standards for display purposes
  • Number of people
  • Financial years
  • Full values
  • Subindicator ordering
  • Non-aggregatable
  • Default filter
  • Age bands
  • Sources

Was this helpful?

Export as PDF
  1. Common practices

SANEF election dashboard

Formatting standards for display purposes

Number of people

  • Ensure any data pertaining to people are rounded to the nearest whole number.

  • Do not use "M" and "k". Use full figures with thousands-separator.

  • Examples:

    • data entry refers to 104678.9 people --> this should be displayed as 104,679.

    • data entry refers to 109987789.49 people --> this should be displayed as 109,987,789.

Financial years

Full values

Prefer full financial years, as in 2016-2017 rather than 2017 or 2016-17. This is because

  • Most people don't know that in the municipal sphere (unlike national) 2017 means 2016-2017

  • Many people won't realise that the -17 means the next year - writing it in full is much easier to understand correctly the first time.

Subindicator ordering

Order financial years in subindicator groups in reverse chronological order - that is 2018-2019 and then 2017-2016. People are most often interested in the latest financial year.

Non-aggregatable

Always mark the financial year column as non-aggregatable. Summing over financial years usually doesn't make sense for an abritrary number of financial years and can easily lead to surprises for users.

Default filter

When the financial year column is not the variable, add a default filter to match the latest financial year. Marking financial year as non-aggregatable will already add a filter for it, but adding default filter configuration will ensure that a sensible value is selected in the filter.

Age bands

The reasoning for our preferred age bands is as follows:

  • Ideally bands should align with voting age

  • Ideally bands should align across datasets e.g. demographics should align with election data

  • perhaps 0-18, 18-19, 20-29, 30-39, 40-49, 50-59, 60+

Sources

Label data sources as {{ dataset title }} - {{ organisation }}so that users can more easily find the right data source.

as opposed to

PreviousGeneralNextAfrica Data Hub

Last updated 3 years ago

Was this helpful?