Files
notifications-admin/.gitignore
Chris Hill-Scott 8ea3f0141c Give estimates of the number of phones in a broadcast area
We need to give people a better feel for the consequences of
broadcasting an alert. We’ve seen in research that some users will
assume it is subscription based, or opt-in, rather than going to every
phone in the area.

I reckon that the most effective way to communicate this is to put some
numbers next to the areas, to give people an idea of how many people
will get alerted.

We can estimate how many phones are in an area by:
- taking the population of all electoral wards in that area
- multiplying it by the percentage of people who own an internet
  connected phone[1]

The Office for National Statistics publish both these datasets.

The number of people who own an intenet connected phone varies a lot by
age. Since the population data for each ward is broken down by age we
can factor this in. Simplified, the calculation looks like this:
- take the _Abbey_ ward of _Barking and Dagenham_
- in this ward there are 26 people aged 80
- 40% of people over 65 have an internet-connected phone
- therefore 10 of these 80-year-olds would be likely to receive a
  broadcast
- (repeat for all other ages)

These numbers won’t be exact, but should be enough to give people a feel
for the severity of what they’re about to do. We can see if they acheive
this aim in user research.

1. This is a proxy for the number of people who are likely to have a 4G
   capable phone, because only 4G capable phones will be receiving
   broadcasts to begin with
2020-09-14 16:26:09 +01:00

116 lines
2.2 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
## We dont allow committing certain file types that risk containing users personal information
## If you are sure that a file is OK, you can explicitly add it to the list of allowed files
*.pdf
*.PDF
*.csv
*.CSV
*.doc
*.DOC
*.docx
*.DOCX
*.xls
*.XLS
*.xlsx
*.XLSX
## Non user files allowed to be commited
!tests/test_pdf_files/no_eof_marker.pdf
!tests/test_pdf_files/multi_page_pdf.pdf
!tests/test_pdf_files/big.pdf
!tests/test_pdf_files/one_page_pdf.pdf
!tests/non_spreadsheet_files/actually_a_png.csv
!tests/spreadsheet_files/newline_windows.csv
!tests/spreadsheet_files/newline_unix.csv
!tests/non_spreadsheet_files/actually_a_png.xls
!tests/spreadsheet_files/EXCEL_95.XLS
!tests/spreadsheet_files/excel_97.xls
!tests/non_spreadsheet_files/actually_a_png.xlsx
!tests/spreadsheet_files/excel 2007.xlsx
!app/broadcast_areas/source_files/Lower_Tier_Local_Authority_to_Upper_Tier_Local_Authority__December_2019__Lookup_in_England_and_Wales.csv
!app/broadcast_areas/source_files/MYE1-2019.csv
!app/broadcast_areas/source_files/Mid-2019_Persons_England_Wales.csv
!app/broadcast_areas/source_files/Mid-2019_Persons_Scotland.csv
!app/broadcast_areas/source_files/Ward-2014_Northern_Ireland.csv
# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
# C extensions
*.so
# Distribution / packaging
.Python
env/
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
*.egg-info/
.installed.cfg
*.egg
venv/
# PyInstaller
# Usually these files are written by a python script from a template
# before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec
# Installer logs
pip-log.txt
pip-delete-this-directory.txt
# Unit test / coverage reports
htmlcov/
.tox/
.coverage
.coverage.*
.cache
.pytest_cache
coverage.xml
test_results.xml
*,cover
# Translations
*.mo
*.pot
# Django stuff:
*.log
# Sphinx documentation
docs/_build/
# PyBuilder
target/
.idea/
.DS_Store
.vscode
# Frontend dependencies and compiled assets
.sass-cache/
cache/
node_modules
bower_components
npm-debug.log
environment.sh
.envrc
# CloudFoundry
.cf
package-lock.json
# Files/folders created by build so not present in .cfignore
app/version.py
app/static
app/templates/vendor