Difference between revisions of "History of Member-Voted Expenditures"

From Hive13 Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
Status Update on 20191227 = This page is a current work-in-progress.  The general goal is to start a sequential summary list, beginning with recent votes for convenience, then go back in time as far as possible, and also go forward into the future in a standard fashion to show the history of member-voted expenditures.   
 
Status Update on 20191227 = This page is a current work-in-progress.  The general goal is to start a sequential summary list, beginning with recent votes for convenience, then go back in time as far as possible, and also go forward into the future in a standard fashion to show the history of member-voted expenditures.   
  
* Each vote documented in the sequential summary list would tie to the meeting minutes of any given week.
+
The list is to included the following objectives:
 +
* Each vote documented in the sequential summary list would tie to the meeting minutes from the given week of the vote
 
* Each vote would have an assigned id number in the form (yyyymmdd)
 
* Each vote would have an assigned id number in the form (yyyymmdd)
 
* If there were multiple votes on a single meeting night the assigned ID number would include a suffix letter (a, b, c, ...) in the form yyyymmdda, yyyymmddb, yyyymmddc, etc.
 
* If there were multiple votes on a single meeting night the assigned ID number would include a suffix letter (a, b, c, ...) in the form yyyymmdda, yyyymmddb, yyyymmddc, etc.
 +
* The list would identify each vote.  There would be a status field or fields showing the YES/NO outcome, and if YES, then added detail such as IN-PROCESS, COMPLETED, etc. with dates
 
* The record would include a link to the google group discussion thread for reference.
 
* The record would include a link to the google group discussion thread for reference.
* The record would initially include a link to current in-process realization implementation progress
+
* The record would initially include a link to current in-process realization implementation progress over time
 
* The current in-process realization implementation progress will be edited to become the final financial realization
 
* The current in-process realization implementation progress will be edited to become the final financial realization
 
* Actual implementation may resemble a spreadsheet
 
* Actual implementation may resemble a spreadsheet

Revision as of 17:05, 27 December 2019

Status Update on 20191227 = This page is a current work-in-progress. The general goal is to start a sequential summary list, beginning with recent votes for convenience, then go back in time as far as possible, and also go forward into the future in a standard fashion to show the history of member-voted expenditures.

The list is to included the following objectives:

  • Each vote documented in the sequential summary list would tie to the meeting minutes from the given week of the vote
  • Each vote would have an assigned id number in the form (yyyymmdd)
  • If there were multiple votes on a single meeting night the assigned ID number would include a suffix letter (a, b, c, ...) in the form yyyymmdda, yyyymmddb, yyyymmddc, etc.
  • The list would identify each vote. There would be a status field or fields showing the YES/NO outcome, and if YES, then added detail such as IN-PROCESS, COMPLETED, etc. with dates
  • The record would include a link to the google group discussion thread for reference.
  • The record would initially include a link to current in-process realization implementation progress over time
  • The current in-process realization implementation progress will be edited to become the final financial realization
  • Actual implementation may resemble a spreadsheet
  • The final financial realization for each vote in the list will tie to the monthly financial accounting records and the updated budgets

The initial look-and-feel for this list will be begin to be shown below and will follow in the next few days...