45 lines
1.3 KiB
Markdown
45 lines
1.3 KiB
Markdown
|
||
|
||
I360 features
|
||
|
||
|
||
|
||
1- Store voter data with tags per data entry
|
||
|
||
2- Search function based on tags/voter info:
|
||
|
||
- individual voter lookup (name address age)
|
||
|
||
- Group search with tags (combine tags, exclude tags, add new tags to current search, see in map {buggy})
|
||
|
||
- Basic map grouping feature for search (draw a shape and it selects the voters inside it on the map, limited use)
|
||
|
||
|
||
3- create survey+script with that custom search
|
||
|
||
4- automatic mapping of walkbooks (sucks though)
|
||
|
||
5- friendly user interface that doesn’t crash (quite good but non customizable)
|
||
|
||
6- export/import csv voter data (export survey results - supporters to texting software)
|
||
|
||
7- daily leaderboard page with some results per knocker to see how the day is going (not detailed enough and quite buggy)
|
||
|
||
8- oversee the surveys from the back end as they go to see general results and assign walkers to different areas
|
||
|
||
|
||
|
||
|
||
What could be improved in those features?
|
||
|
||
|
||
|
||
-Ai dictation to select and exclude tags when doing a survey - gets so complicated it takes forever to target -
|
||
|
||
- Ability to change or tailor survey per voter type (tags)
|
||
|
||
- Customize blockwalker app interface for most relevant voter info/tags/colors
|
||
|
||
- color coded map for analysis of city areas (partisan affiliation/religion etc)
|
||
|
||
** |