Modern political campaigns are famous for their ability to collect data on and target their campaigns to individual voters, but students running USG campaigns or referendum elections don't even have the tools to start. Or rather, they didn't until Quickcanvass. Quickcanvass provides a mechanism for campaign managers at Princeton to manage their volunteers, collect and organize their data on canvassed students, and to perform precise searches to single out particular regions of their electorate. With Quickcanvass, you will no longer face the problems of not knowing which doors to knock on for your campaign, you will no longer hit the same door twice, and you'll be able to tailor your campaign in response to changes in the electorate - changes that you'll pick up on, because you can download the responses of the students you've canvassed at anytime.
The Creation of Quickcanvass
This project status page is to serve to keep y'all updated on new successes and failures. If you are looking for the official site, check out the "QC" button above or click the link.
Otherwise, check out some sweet blog posts, and look below for a sneak peek into the rest of the project timeline!
Product Guide
Final Report
Our Team
Jessica Ji Our President
Jessica works mainly on back-end and keeping the rest of us on task.
Grace Turner Front-End Specialist
Grace works on making the UI experience as smooth and as beautiful as possible.
Samuel Russell Database Specialist
Sam enjoys troubleshooting and making the database queryable.
Luisa Goytia Full-stack Programmer
Luisa works both front-end and back-end, depending on the problems of the week.
Timeline
-
Consolidate Project Idea
MARCH 5
WHO: Everyone
Brainstorming session to select a project.
Upon project selection, specificy functionality.
-
Design UI framework and distribute tasks
MARCH 20
WHO: Everyone
Specify desired front-end to match back-end functionality.
Divide project into subtasks that can be distributed among members of the group.
Assign deadlines for each subtask.
-
Create Project Status Website
MARCH 27
WHO: Grace
Create page to record our milestones.
-
CAS Login/Logout
MARCH 27
WHO: Luisa
Implement CAS authentication for login and logout of QuickCanvass.
-
Create user Databases
MARCH 27
WHO: Sam
Create databases that will hold all the information needed for accounts.
-
Finalize general UI
April 8
WHO: Grace and Luisa
Specify desired front-end to match back-end functionality.
Divide project into subtasks that can be distributed among members of the group.
Assign deadlines for each subtask.
-
Deploy website on Google App Engine
APRIL 8
WHO: Jessica
Figure out how to deploy website.
-
Everyone on the same page
APRIL 8
WHO: Everyone
Connecting everyone's local machine to Google Cloud Platform services.
-
Begin to link front-end with the Cloud SQL database
APRIL 8
WHO: Everyone
-
Create logo
APRIL 10
WHO: Luisa
-
Complete login/logout and user database storage
APRIL 15
WHO: Sam and Jessica
-
Create campaigns
APRIL 15
WHO: Jessica and Sam
Incorporate the ability to create a campaign.
-
Goodbye Google. Hello Python!
APRIL 21
WHO: Sam
Use pythonanywhere.com for deployment instead of Google App Engine.
-
Finish user dashboards
APRIL 22
WHO: Everyone
Complete frontend and backend for volunteer and manager dashboard.
-
Create surveys
APRIL 22
WHO: Everyone
Allow manager to add a survey to the campaign.
-
Go survey!
APRIL 22
WHO: Jessica and Sam
Allow volunteer to use the survey available in the campaign.
-
Complete search
APRIL 29
WHO: Sam
Debug search function and clean up database irregularities related to students in eatings clubs and living off-campus.
-
Add volunteers by username
May 3
WHO: Jessica
Allow managers to add volunteers by using the volunteers' username instead of the campaign code.
-
Improve Error Messages and Finalize CAS
May 7
WHO: Sam
Give detailed error messages when users try to do things they shouldn't and get CAS working for real this time.