Skip to content
This repository was archived by the owner on Aug 10, 2020. It is now read-only.
Dave Miller edited this page May 8, 2018 · 10 revisions

This is intended to be a wordpress plugin specifically designed to collect election results from a BSA Order of the Arrow election

This plugin is still in development, and it not yet usable. If you know PHP and want to help, we'd welcome it.

Nataepu Shohpe Lodge's existing election results entry system utilizes a Contact Form 7 WordPress Plugin Form. We've run into some inconveniences using it which prompted investigating writing this plugin. Some of the initial planning is in the issue tracker at https://github.com/oa-bsa/election-manager/issues . Current "bugs" are problems with the existing system that we hope to rectify by writing this. Enhancements are additional things that would be nice to do.

Status as of June 2016: election season snuck up on us, and we discovered some new tricks with the CF7 plugin that made it easier to hack new things on top of it instead of writing self-contained code. Phase 1's objectives were reached for our purposes by adding some MySQL Views to CF7's data storage and a few new tables to copy data into as it was managed, and a small mini-plugin that implemented a few pages for managing the data in a more-compatible way than CF7 does. A couple election date tracking features (see Phase 3) were also obtained by a combination of CF7 forms and the SimpleCalendar plugin sitting on top of a Google Calendar. We'd still like to make it self-contained, as the base setup within CF7 itself and SimpleCalendar is not exactly straightforward so we'd rather not have them as dependencies. Not to mention it was written in a hurry and really feels like a hack. I hope to have the code we did write posted here somewhere shortly.

Status as of May 2018: The CF7 based system has continued to evolve - the code for that is at https://github.com/justdave/nslodge-wp-customizations

Phase 1

Implement a clone of the existing system, but with the bugs enumerated in the tracker fixed. This is the minimum required to have a usable system for the 2015-2016 election season. If we manage to implement anything from Phase 2 it'll be a bonus.

  1. Basic forms for data submission. Use the same back end for both UE and SM submissions, just set a flag in the data for which one it came from.
  2. No user logins for submission, just blind URLs like existing system (login required to view submissions)
  3. Troop data entered first instead of last, with each scout record linked to the troop record.
  4. Data export per-troop which is compatible with OALM.

Phase 2

  1. Prepopulated list of troops from ScoutNet data (troops only, no scout data)
  2. Assigned logins for each troop
  3. Allow a troop login to view/edit their submission after the fact.

Phase 3

  1. Unit Election crew logins
  2. Allow crews to claim (or be assigned) responsibility for an election
  3. Track election dates
  4. Nag people via email once an election date passes if results haven't been entered yet

Clone this wiki locally