This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Dev Todo list
qwertya15 edited this page Mar 9, 2019
·
31 revisions
- Remove temporary hackiness - 'data1' references in \routes\reports.js and \views\reports\teamintel.pug (no longer need historical views)
- When the pit scouting data is being changed, repopulate the inputs/drop-down menus with old data
- Change scouting.js get pit to get the event key and then the pit data_
- Send the pit data to the view
- Update view to pre-populate the fields with the pit data
- Change link text(s) to [buttons] (or at least a link that looks like one e.g. add an underline or change the color) to demonstrate clickability
- Manual match schedule / scores - see details
- Update pit scouting data in place (with prior values visible)
- Upload photos of robots during pit scouting (look this up) > may need Express Generator or Formidable
- ToDo Image uploads
- https://www.w3schools.com ➞ uses Formidable
- https://scotch.io/tutorials ➞ uses Express
- Improve data displays (D3.js?)
- Alliance selection process
- Change data retrieval to push rather than polling
- Make it easier to click button to update latest match data from TBA
- Generate pseudorankings for early on when there are no matches & no rankings from TBA (so team pick list works)
- User creation: Make it so that creating a support/exec user doesn’t destroy the server lol???
- Alliance selection process
- Keep track of who is cap in each slot
- Keep track of who is available
- Keep track of who said no, can't be picked
- Analyses: In playoffs, relevance of AQ & FB to winning?
- In match scouting data, relevance of auto-scale to winning?
- Use OPR data to make match predictions?
- Ability to swap out/in pit scouts
- Free-text options for pit scouting
- Admin page to approve each free text input
- Add a “completed matches” page for list of all team stats from each match
- Allow multiple teams to login (jordan’s idea notes: https://i.imgur.com/d74gvhE.png notes: https://i.imgur.com/dFHXxJr.png )
- Create color palettes for each year
- Add alliance color to match scouting page
- Style Per-Team Stats page to be more legible (Sub-categories of auto, teleop, end)
- Update styling responsiveness so pages look OK on desktop as well as mobile
- Help info for pages
- Add team nicknames to other screens
- Match scouting list
- Match scouting page
- Pit scouting page
- Dashboard
- Align info readouts along vertical axis?
when "textblock"
div(class="w3-row")
div(class="w3-col w3-right-align w3-cell-middle" style="width:48%")
h4(class="gear-text-white") #{element.label}
div(class="w3-col" style="width:4%")
|
div(class="w3-col w3-left-align w3-cell-middle" style="width:48%")
h4(class="gear-text-white") <b>#{data[element.id]}</b>
Admin options:
- See a scout’s upcoming assignments
- Be able to periodically rotate match scouting assignments (?)
- Audit match submissions - logs first, DB second, tabular view in UI eventually
- Help for scouters
- Adjust TBA match data ingestion to write numeric
- Enable TBA pushing data rather than manual on-demand pull
- reports/ (view folder)
- audit.js
- adminindex.js
- */admin/generatedata necessary still? - yes until we have volumes of scouting data
- allianceselection.js
- checkauthentication.js
- current.js
- dashboard.js
- externaldata.js
- Index.js
- Login.js
- manualinput.js
- reports.js
- scouting.js
- scoutingpairs.js
- teammembers.js
- images.js
- AvatarStorage.js
- Change all getCurrent stuff to just use req.event.key and req.event.name
- “What did you change?” option for pit scouting
- TBA - Statuses data
- Past matches & upcoming matches for each team should be in the same place
- Colors of buttons are not clear
- (Idea) Let users view data from previous years; save color palettes and logo from old years for viewability
- db.scoutingdata.updateMany( {event_key: "2018mrcmp"}, { $rename: { "data": "data1" } } )
Example formatting
- Not yet done
- Done