wtg / elections Goto Github PK

The RPI Elections dashboard for GM Week and Freshman Elections.

Home Page: https://elections.union.rpi.edu

License: GNU Affero General Public License v3.0

CSS 4.26% HTML 34.08% JavaScript 57.13% Shell 0.02% TypeScript 4.51%

elections's Introduction

Elections

A modern platform for managing elections, designed specifically for GM Week and other student government elections at RPI.

Features

Simpler nominations
Accessible candidate and party information
Modern web goodness

Deployment

This website is built in a modified MEAN stack (MariaDB, Express.js, Angular.js, and Node), and can be deployed using the following steps:

Clone this git repository by running the following command in a Git-enabled terminal:
- > git clone https://github.com/wtg/elections.git
Navigate into the directory of the application:
- > cd elections
If Node is installed on your computer, skip this step.
- Install Node here.
Install all necessary dependencies by running the following commands:
- > npm install
If MySQL is installed on your computer, skip this step. Install MySQL or MariaDB (the open-source equivalent).
Make a copy of devconfig.example.js and name it devconfig.js. Provide details about the database connection (host, port, username, password), as shown in the example.
- This could be completed in the terminal by running: > cp devconfig.example.js devconfig.js
- Blank configuration variables are provided in the file.
Run the server: npm start. This command will also create the database for the site if it doesn't currently exist.

Note: if NODE_ENV is "production", npm start will serve static files from the dist folder, which you can have Webpack build by running npm run build. If NODE_ENV is "development", npm start will automatically run Webpack and serve assets from memory.

Navigate to localhost:3000 in your browser, and pat yourself on the back—your instance is deployed.

Credits

This project was created by the Web Technologies Group.

Developers

The core development team consists of:

A list of all contributors can be found here.

elections's People

Contributors

Stargazers

Watchers

elections's Issues

Create basic file structure and site structure

Marking party officer as highest / leader

Disabling an office causes a 500 error

bin/testdata cannot find db.js

Line 7 of bin/testdata looks for a db.js file that doesn't exist:

var connection = mysql.createConnection(require('../db.js'));

Preferred name not given preference in candidate card on offices page

Profile page

Candidates (signed in) can enter personal information, a photo, social media, etc
Anyone can see a candidate’s nominations, party affiliation, candidate assistants, and other pertinent information about the candidate

Adding party officers

Video url can’t be entered on candidate profiles

Delete event

Sanctions view

Create a view where sanctions, warnings, and violations are listed. They will have an associated candidate, and will have a text and a category. Admins will be able administer, edit, and delete sanctions, but they will be publicly accessible.

Party page

Where students can see what candidates are in that party, show a party platform, and (maybe?) a party photo

Sentry (raven) integration

Not enough validation on New Office form

"Required Nominations" and "Number of Openings" can both be set to negative numbers. This probably shouldn't be allowed.

Error: unable to delete candidates because of assistant foreign key

Error: ER_ROW_IS_REFERENCED_2: Cannot delete or update a parent row: a foreign key constraint
fails (`elections`.`assistants`, CONSTRAINT `assistant_fk1` FOREIGN KEY (`candidate_rcs_id`)
REFERENCES `candidates` (`rcs_id`) ON DELETE NO ACTION ON UPDATE NO ACTION)

Random candidate on homepage doesn't take preferred name into account

Removing party officers

Candidate view displays major even if not set

If a candidate hasn't defined a major, it should be hidden under the "Candidate Facts" section. See screenshot.

Ask me anything system

Improve Code Climate GPA

See https://codeclimate.com/github/wtg/elections

Calendar page

Where RnE can enter dates for informational sessions, voting day, and other events that’ll occur during the race

Display candidate running for multiple positions in one view

Nominations entering

Allow for members of the Rules and Elections Committee for manual entry
Allow for candidates to open an page where students can enter their RINs and initials, kiosk style.

Election archives

Past elections should be viewable. The site should preserve and make accessible the information that was entered during elections.

500 error displayed on UI when on office edit view

No corresponding error found in the console

Users cannot enter an office filter category when creating an office

Implement cms-api node module for consistency

https://www.npmjs.com/package/cms-api

Nomination case for all undergraduates only doesn't exist

Rules page

For the elections handbook. Should be entered in as text for table of contents and so that students can search through it

Image uploads

The site needs a system for photo uploads: every user can upload two images - profile image and cover image.

The desired flow would be:

user uploads image
the filename is changed the randomly generated value, and stored in public/usr_content/
the randomly generated filename is subsequently added as new row of an images table, with an image_id and filename
the image_id is added to the candidate_data row for the candidate, as profile_photo or cover_photo, appropriately.

Overall settings page / manage elections page

Needed features (known so far):

Create, edit, and delete elections
Set the currently active election
Hide / show the entire website
Edit the homepage content

Double horizontal rule appearing after last office

Page: Offices

Create new event

AMA listing does not filter answered/unanswered correctly for different tabs

Sessions should be stored persistently

Right now they're stored in memory, which means everyone gets logged out whenever the server is restarted. They should be stored in a database or something similar.

Offices / Races page

Where students can see who’s running for what positions, and see specifications / requirements for each position.

Integration with RPI's CAS Authentication

Edit events page

One-time image downloads

Candidate images are currently hosted by third-parties and simply linked to. Once the image upload system is in place, we should initiate a one-time download of linked images and insert them into the site as if they were uploaded. This will ensure that they will be accessible even if the links stop working in the future.

Candidate expense digital logging system

Email and site notifications

Create an automated, candidate-customizable notification system for candidates: either by email, visible on the site, or both.

Notifications could include:

Nominations added
Candidate assistant added
New AMA question posted
New contact (changing contact from a mailto link to a form)

List all events on events page

Add and remove candidate assistants for candidates

Only admins should be allowed to do this, not candidates

Remove hashbang from URLs

Switch Angular $location to HTML5 mode to get nicer URLs. This requires the app to serve index.html regardless of request path.

See https://docs.angularjs.org/guide/$location

Manual override nomination

User should enter the desired amount to set the nominations to, which would override the nominations table, regardless if nominations are added for the candidate through the table subsequently

Populate candidate profile with real data

Ensure office categories are taken into account for nominations

Needs to match the office type:

"All offices" -- any student can nominate
<year> -- only that year (either by credit or by entry), and coterminal students when they're senior candidates can nominate
"Graduate" -- only graduate students and coterminal students can nominate
"Greek" -- only greek students can nominate
"Independent" -- only greek students can nominate

Edit candidate profile, available to to the candidate or admins

Random candidate API endpoint incorrectly returning empty list

/api/candidates/random occasionally returns an empty list instead of a random candidate even when there are valid candidates to return. I think the issue is that candidates for inactive elections are not filtered out until after a random candidate ID is chosen by the backend.