We want to collect subjective data for each alliance team. This will be done by a different set of scouts. There will be 6 regular scouts per match - 1 scout per team. For the subjective data there will be 4 more super scouts. Two super scouts per alliance, one for ranking defense and one for ranking driving skills.
Details
This PR only has the UI components so we can view the look and feel. Once we agree on the look and feel we can add the fields to the match database table and wire it up to the new component.
This PR also contains some small cleanup: commenting out the drop table statements in schema.sql to prevent accidental disaster (developers can uncomment it temporarily/locally as needed), remove admin requirement from match component.
Timing
The super scouts will enter match number, alliance color and play (defense vs driving). The drop-downs for teams will be populated from existing match table rows. This will require a change to the match content component - the match row will need to be inserted as soon as the basic required data (competition, match, team, alliance) is entered (the first "Next" button). Then the remaining scout data will be handled as an update and the super scout data will always be an update operation.
Next Steps
Let's discuss this UI. Then we can update the match content component to insert the match table row early so that the alliance team nums will be available to super scouts.
Summary
We want to collect subjective data for each alliance team. This will be done by a different set of scouts. There will be 6 regular scouts per match - 1 scout per team. For the subjective data there will be 4 more super scouts. Two super scouts per alliance, one for ranking defense and one for ranking driving skills.
Details
This PR only has the UI components so we can view the look and feel. Once we agree on the look and feel we can add the fields to the match database table and wire it up to the new component.
This PR also contains some small cleanup: commenting out the drop table statements in schema.sql to prevent accidental disaster (developers can uncomment it temporarily/locally as needed), remove admin requirement from match component.
Timing
The super scouts will enter match number, alliance color and play (defense vs driving). The drop-downs for teams will be populated from existing match table rows. This will require a change to the match content component - the match row will need to be inserted as soon as the basic required data (competition, match, team, alliance) is entered (the first "Next" button). Then the remaining scout data will be handled as an update and the super scout data will always be an update operation.
Next Steps
Let's discuss this UI. Then we can update the match content component to insert the match table row early so that the alliance team nums will be available to super scouts.