Differences

This shows you the differences between two versions of the page.

--- projects:vote:vote [2024/10/11 03:49] – jhagstrand
+++ projects:vote:vote [2024/10/20 07:34] (current) – jhagstrand
@@ Line 4: / Line 4: @@
 todo:
-  * x delete rfk
-  * create popup
+  * clean up Help: "no-spoiler",  "anti-spoiler"
-  * x push to gitlab
+  * back button come back to about from wikipedia, browserhistory return to last used page
-  * Require login before castballot
+  * add Register button to Login form and vice-versa
-  * clean up results page, remove "instan...", display details on request, add decision at top
+  * display url on ballot
   * add, edit, delete, approve decisions
+    * if userid = ownerid, show pencil as edit link
+    * allow delete from edit screen
+    * give everyone the insert link: compose, add, insert, new
+      * a "new" link at the bottom of the list
   * add, edit, delete, approve candidate
-  * AI to match duplicate questions and answers
+  * AI to match duplicate decisions and candidates
-  * display url on ballot
-  * popup
-    * issue:
-      * adding a new candidate writes him to the database immediately
-      * choosing a listed candidate writes to the database only on "cast ballot"
-  * immediate ballot db updates, but with a "Cast" flag
-    * remove "Cast Ballot" button
-    * add a new button called "count votes"
-    * but we need the user to understand that his votes take effect immediately
-    * add a cast true/false flag to the rank record
-    * force user to acknowledge vote before leaving page
-      * when leaving ballot page, if has not cast ballot, warn about losing data
-        * "You have not yet "cast" your ballot.  Any changes you have made will be lost."
-        * Do you wish to cast your ballot now? (if not, all your rankings will be lost."
-        * put the ballot in a popup box.
-      are you going to allow him to save votes or not?
+  * encryption: only the voter can see his own ballot
-      You can't say "you will lose your data" if you've already saved the shit to the db
-    * screen architecture
+  * authentication: each voter is a member of the jurisdiction of the decision
-      * decision list, two buttons on each
+    * Add jurisdiction table, as ID, title, user ID.
-        * ballot popup, two ways out: Cast Ballot or Cancel
+    * Had jurisdiction user table as jurisdiction ID user email.
-          * on cancel:
+    * Add Eli to add change delete jurisdiction records
-        * results popup -> "counting..." spinner - display results, Close
+    * Add jurisdiction ID column to decision table
+    * Filter decision lookup to users that belong to that jurisdiction.
-    * rename table rank to ballot
-      * because that's what it's doing, saving a user's ballot
-      * ballot: id,userid,decisionid,ranks,iscast, isdirty