Twitter URLs in imported CSV were not converted to Twitter usernames

[wbushey]

Relaying this feedback that somebody provided at a recent Open Twin Cities meetup. It was pointed out that a few candidates in the St. Paul Your Next Rep have Twitter user names that are actually URLs to their Twitter profiles, which leads to broken generated Twitter URLs. This was traced back to the spreadsheet that was imported to seed St. Paul data, in which some of the candidates' Twitter usernames are URLs. Your Next Rep is good at handling Twitter URLs when entered though the UI, I'm guessing that same validation/processing needs to be applied to CSV imports.

[mhl]

Arguably this problem is in elections/st_paul_municipal_2015/management/commands/st_paul_load_candidates.py - we can't easily add custom model validation just for the Twitter ID field, since it's stored as the generic django-popolo ContactDetail. We're likely to change how Twitter usernames are stored anyway, as part of #271 and that will inevitably fix this issue as a side effect (if we can't find a numeric Twitter ID, then there's no ID to store)