Freehub-next-gen

From The Bike Kitchen
Revision as of 19:38, 5 April 2010 by Slchorne (talk | contribs) (Created page with '= Things we should add to with freehub = == objectives == * centralise data * address the important stuff * make it functional for people, so we don't force them to use other s…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Things we should add to with freehub

objectives

  • centralise data
  • address the important stuff
  • make it functional for people, so we don't force them to use other systems

remodel the data

better definition of the member types :

  • patron
  • staff
  • youth (under 18)

add additional daily states

  • Visiting
  • Volunteering
  • Staff mechanic

add additional services

  • Staff in training
  • Volunteer hours, can we track their individual hours ?

better tracking of memberships

  • identify when a memberships is a renewal or a new membership
  • enforce some required fields. ZIP and PHONE (or email)
  • add a Youth (under 18) field.
  • flag to show if the liaiblity form was signed

better tracking on the "in the shop today" list

  • Highlight people on the day who are Staff mechs for that shift

Better Tracking on notes

  • auto enter the date on a note
  • flag a note as IMPORTANT so it always shows in the daily sign in list

better reporting

explain the columns on the 'summary report'.. 'Patron' overlaps with other values. break them out as : TOTAL, Staff, MEMBERs , non-members