In general, when somebody asks to download their TRC data as a CSV, it’s often the wrong thing. Once you’ve exported to a CSV, you lose out on the benefits of TRC, including our mobile canvassing apps. It also causes problems like a) how do you keep the downloaded CSV in current with changes; b) how do ensure data collected from that CSV gets uploaded back to your account? And usually there’s a better way to accomplish their scenario…
Note that while Android and iOS release versions are coordinated, not every version is released on both platforms. Generally, the Android builds are a bit more frequent, due to the higher market penetration and the fact that I personally test it in the field daily.
Here is a quick summary of the changes introduced with each release:
Sep 5, 9:50 PM: Full rollout. (Promoted from beta 1.5)
– Added voter history into ListView voter description
– Added household count to ListView household icon
– Fixed NullReferenceException in DetailView
– Updated to latest CarouselView and Xamarin.Forms packages
– Replaced various 3rd-party plug-ins with Xamarin.Essentials
July 24, 2:30 AM: Full rollout. (Promoted from beta 1.4.2)
– Restored WebVew hosted in NavigationPage for login
– Added Log In menu command
– Updated to pre-release Xamarin.Forms (fixed issue #2393)
July 20, 11:22 PM: Full rollout. (Promoted from beta 1.4.1)
– New menu item to Share sheet with other users
– Added transfer token for Plug-ins button to bypass Web client login
– Switched to using App Center errors to report exception handling
– Switch to CarouselView from Andrei Misiukevich to work around Issue #2637
– Swiping in CarouselView will now wrap around
– Fixed delay in bringing up Settings panel
– Sort by distance is now updated live as position changes
July 7, 5:10 PM: Full rollout. (Promoted from beta 1.3.6)
– Pins now update color and opacity with incremental sync of voter records
Jul 3, 11:33 PM: Full rollout. (Promoted from beta 1.3.5)
– Manual upload to cloud now syncs changes in all sheets, not just current one.
– Alert now displayed when manual upload is unsuccessful.
– Fixed closest household button
– Handled phone number formatting overflow
– Streamlined conversion for string types
– Switched to chat keyboard for comments
– Refined voter detail panel
Jul 1, 9:05 PM: Full rollout. (Promoted from beta 1.3.3)
– App name change to Canvasser, with new adaptive icon
– Back button from main page navigates to parent sheet
– Added Plug-in button in SheetDetailPage
– Added detail section on VoterDetailPage for custom columns
– Preserves last visible region for each sheet
– Fixes missing map pins after extended load
– Updated logic for dimming households (visited or all members dimmed)
– Filtered voters now show as dimmed
– Added automatic sync after connectivity is restored or successful login
– Exception handling for failed OpenSheet (e.g. loss of permission)
– Fixed household member list opacity update
– Updated target URL for Learn More button in About
– Simplification of WebView-based login/logout, with new icon
Apr 24, 8:33 PM: Full rollout. (Promoted from beta 1.2.2)
– Reverting to CarouselPage to try to work around infrequent crash from ObjectDisposedException
– Maintains sorted order of household members when switching to voter detail page
Apr 19, 8:37 PM: Full rollout.
– Added SearchBar on List tab
– Added male and female avatars
– Fixed icon color update
– Sorts household members by age
– Possible fix for System.ObjectDisposedException
Apr 16, 8:30 AM: Full rollout.
– New buttons on voter detail page to dial phone number and send email
– Auto formatting of phone number (US only)
– Preferred virtual keyboard variants for phone number and email entry
– Upgrade to ProGuard 6.0.2 bytecode optimization
Apr 12, 4:57 PM: Full rollout. (Promoted from beta 1.1.3)
– Sync changes when app sent to background
– Scroll corresponding list item into view when pin selected on map
– Added completion percentage to the sheet Info page
– Fixed off-by-one bug when applying missed changes from other users
Apr 6, 10:20 PM: Full rollout.
– Rolled back to Xamarin Forms v184.108.40.2060555 to work around WebView login bug
Apr 6, 3:28 PM: Full rollout.
– Clears WebView cache after logout so that previous user’s cookies aren’t still present
– Fixes performance issues with CarouselPage by switching to CarouselView, which supports UI virtualization
– Fixes a crash when location services goes unexpectedly offline
– Fixed crash caused on some configurations by CarouselView linker error
Apr 3, 3:02 PM: Full rollout. (Promoted from beta 1.1)
– Swipe left or right in household or voter detail panels for next & previous
– My location button in household detail view to quickly index to closest address
– New default sorting of households is by address
– Exception handling for failed DateTime parsing
This article describes a best-practice for campaigns in using data for targeting voters and how you can achieve that with TRC.
The flow here is to start with getting initial public data from the county auditor, merge in microtargeting information, choose the targets, canvass, and iterate on the model.
Conceptually, we can think of data like a giant spreadsheet (CSV file). Each row is a voter, and columns are information about that voter. We’ll walk through the different phases with a small sample of 8 records, but TRC can help you do this with your entire district of 80,000 records
In previous posts we’ve looked at how our political system has become increasingly polarized, with our analysis of voting records showing that many self-styled moderates and independents are exhibiting much more partisan behavior when voting on the House or Senate floor. Having served for a few years now on a PDC open data advisory group, I realized that the same type of analysis could be done for organizational donors. Despite this being public data, not many people in Washington state know who the biggest political donors are, much less who they support.
So, are many of these “non-partisan” or “bi-partisan” organizational donors more partisan than they let on?
We can figure this out, and the methodology is pretty simple. The PDC Open Data Portal publishes all contributions to candidates and political committees back to 2008. For this first analysis, we looked at donations to partisan legislative and statewide candidates from businesses, unions and political action committees. The partisanship score for each donor is the difference in percentage of donations by party, giving each a range from 100 (exclusively Republican) to -100 (exclusively Democrat).
Most of the effort here is involved with the fuzzy matching algorithm, since candidates are very inconsistent on how they report the names of these organizations to the PDC. I use a trigram matching method, which isn’t perfect…but it does pretty well. Currently, contributions are grouped under the same donor if 80% or more of the trigrams match, but this is adjustable.
Here are the results:
If you visit WhipStat.com, you’ll now find an interactive and animated version of our organizational donor partisan analysis that allows you to filter by jurisdiction type and date range.
If you’d like to do further analysis, feel free to hit the Download button for a tab-delimited table of the charted data. Note that for now we don’t display or download the complete donor dataset, as that includes over 8,000 organizations.
A few things become apparent when reviewing the results:
- Some of the biggest legislative donors give heavily to candidates from both parties.
- About 6% more is given to Democrats than Republicans in legislative races, but that increases to 28% when looking at statewide races.
Up next: We’ll take a close look at hard money vs. soft money contributions.
TRC includes a map view that shows you the voters as pins on a map. This is a standard view similar to what you’d see in any canvassing app. Since it runs directly in the browser, there’s no additional installation step needed.
The map view is exactly the same underlying information as in the List View, so you’re encouraged to use whichever view makes you most productive. You can make changes in the map view, and then immediately switch to the List View and see them.
A common pattern is to use Geofencing to carve up a large region into smaller neighborhoods, and then you can use the map view to canvass those neighborhoods.
Using the map view
The pins are color coded by party ID. Hollow pins are doors that have already been visited. You can go back and edit answers on visited doors.
You can touch a pin to see the voters at that household:
If nobody is home, you can mark “Result Of Contact” for the door and move on. Else, you can select an individual to see their information and record the canvassing results.
Be sure to
- fill out the Party ID,
- fill out whether they’re a supporter, and
- result of contact.
- hit the “Save” button
Getting to the map view
You can get to the map view by touching the “View Map” buttons on the standard walking list.
The map view leverages HTML5 local storage support to provide an offline experience even though it runs in a browser.
This means that you can load the map view while you have an internet connection, and then canvass offline, and then upload the results when you’re done. However, it’s highly encouraged to canvass with a cel connection so that your results are immediately uploaded. Even if you temporarily lose connectivity, your results will be uploaded when you regain a connection.
To verify your results are all uploaded, on the main page, touch “Local Storage” in the upper right corner. That will take you to a page like this:
Hit the refresh button to pull the current status. If you have outstanding changes and running offline, you’ll see something like this:
Once you’re back online, hit the “Refresh” button again once online and verify the “Number of Changes not yet uploaded” is 0.
TRC has rich filter abilities that let you:
- Interactively explore your data.
- Determine a subset of targeted voters.
- Create a subsets that you can assign and share with others
- Use your filtered view with any other feature in like printing, exporting a mail list, and maps.
Accessing the Filter plugin
There are several ways to access the filter ability:
1. You can access the Filter plugin directly from here.
2. You can access filtering via the standard list view on a sheet. Click the filter icon in the top-left view:
3. You can also access Filter from the plugin list for your sheet.
Common things to filter on are:
- History – this is how likely somebody is to actually vote.
- Party Id – this is the party affiliation.
- Answers to questions like Result of Contact or Supporter
- Other microtargeting information.
Using the Basic View
There are several views for filtering. The “basic” tab lets you qickly filter on History, PartyId, and Age.
Using the Query Builder view
You can also switch to the “Query Builder” tab to create a more complex query.
Here’s a basic query to look for ‘social’ equals ‘hard left’, ie, social liberals. You can select the column, operator, and value to create a rule, and then click “run query”:
We can then build up the query to also require people over 55 years old. This is means “social liberal AND over 55”.
The “add rule” button adds a new rule to the current group. Note that we have ‘and’ selected which means both rules must apply.
If we meant “social liberal OR over 55” , then we can select ‘or’:
Tip: If you got 0 results, check that you didn’t confuse an ‘and’ with an ‘or’. For example, (Party == 1 and Party == 2) will give you 0 results. It should be (Party == 1 or Party == 2)
We can add multiple rules. This means social liberals between 45 and 55.
We can also click “add group” to create more complex expressions. This means “Social liberal AND (party is either 3 OR 4)”. Using groups is needed when you want to combine AND with OR expressions.
The other trick is to us the ‘history’ score (likeliness to vote) to narrow the number of targets. You can see the “Previous Results” tab at the right shows the results of queries you’ve made so far. For example, this query finds fiscal conservatives that are very likely (0.90 is 90% ) likely to vote. Note that is must be specified as a decimal between 0…1 and include the leading 0. (so “0.90”, not “.90”, not “90%”).
For example, this query is for any women with Party equal to 1 and that live in the specified zipcode or city.
In our case, it gives us 4900 voters. We can repeat the query with 0.70 instead, and gets 17000 voters.
Tip: If you want more data, you can upload it yourself via the data uploader or purchase additional data from a data vendor like Voter-Science.
Saving the filter
Once you run your query, you can set it as the targets or save it as a regular sheet:
The “Save Query” button will prompt you for a name for this filter. When you hit the back button to go back to the List View, you’ll see it on the sheet list. At this point, the filter acts just like any regular sheet, and you can share it, print it, or use it with any other plugin.
Click on “walking list” next to that filter, and you’re now viewing just within the filter.
You can click “share this” to share just this filter with another volunteer.
You can click “view entire walking list” to get back to the full list and possible create new filters.
Viewing on a map
You can also visualize a heat map for the results. For example, here’s a query of “Who are supporters that haven’t voted yet”. You can then map it, and chase them down:
Filtering creates a new “child” sheet that applies a filter-expression to extract a subset of the rows from the original (“parent”) sheet. The filter creates a a view that shares the same sandbox as the original sheet, so all changes in the child are instantly visible in the parent. However, the child sheet still maintains its own history tracking and audit logs.
TRC’s default view is the “ListView”, which looks like a digital clipboard. Names are organized by street. There are also other views, such as the common map view.
See http://bit.ly/1U1sgjJ for a youtube demo.
The view looks like this:
In the ListView, each row is a voter. Voters are grouped by address so that you can easily identify all voters at a single household when you’re at the door. You can collapse voters by streets for easy managing. The grouping is zebra striped (yellow / white + grey) for easy-reading. The stripe color is purely ascetic.
When you edit cells, they start off red, and then turn green when they’re uploaded to the server.
This provides immediate feedback on upload. Cells are colored red when you edit and green when their result is uploaded to the cloud, so you get immediate piece of mind that your changes are safely saved.
TRC supports collaborative editing: when multiple canvassers are walking the same precinct, other canvasser updates show up on your sheet in realtime.
The default view in TRC includes some standard columns:
- Voter address, name, age, gender – this is commonly from public Secretary of State Voter Database (VRDB)
- History – this is a percentage of likeliness to vote in the upcoming election. This is similar to the “how many of the last 4 elections did they vote in”. It’s computed via a predictive model and measurably more reliable than just a “4 score”.
- Party – this is a party identification.
- Supporter – Does the voter support your campaign? This likely correlates with party, but is very important in tracking cross-over voters and non-partisan races.
- Comments – – this lets a canvasser provide free-form notes.
See Pinned vs. Floating values for more details on where the data comes from.
TRC will bold the “targeted” voters to help canvassers prioritize who to visit. For example, a precinct may have 500 people but you only have time to talk to 50 voters. The “targeting” helps prioritize which ones to talk to. TRC uses a default targeting algorithm, or you can supply your own targets, or you can coordinate with Voter-Science to use analytics to get a special target list for your campaign.
We continue to show all the voters because if you happen to talk to a non-targeted voter, we want to make it easy to record that information. (Knowing who the opponents are makes it easier to guess who our guys are).
Washington State is vote-by-mail. That means that people are casting their votes 3 weeks before the election. During these ballot chase periods, names will also be crossed off as people have voted. Voter-Science collects the matchbacks from the county auditors. See Prepping for the ‘16 General for more details.