Closed rye closed 10 years ago
I like that idea. If we use it, I would like to enact a name
field so that there is a convention for robots that have names.
That's fine.
Okay, I will add this model eventually. If anybody does not like Robot
being the name of the model, please speak up.
Participations now exist again.
Operating under the assumption that robots are the only thing that we will want to pre-scout (both now and in the future), that model name is acceptable. I recommend that we close this issue since discussion has shifted from "Modification of Record model to support pre-scouting." (And, if necessary, create a new one for the Robot
model discussion, though that's not the point of issues [ahh, Gitter ;)]).
I was going to close it once the Robot model is made (it is currently next up in my Robotics to-do list).
Has any progress been made on this?
Nope. Making the Robot model is really easy though since I don't think it has any special properties to account for.
Currently there's not really a model for pre-scouting. I'd like to suggest that we change the Record model to support pre-scouting.
I think that all that needs to get done is we should not require
match_number
ormatch_id
to be present and instead enable the use of arecordType
dynamic attribute that would always get set. IfrecordType
were present and equal tomatch
, we would throw an error unlessmatch_number
were present. If it were equal toprescout
, we would ignore that and just create the record without amatch_id
.Alternatively, we could create a new model for storage of prescouting data, or associate it with teams. If we associate it with teams, however, we'll need to overwrite existing pre-scouting data as new information is obtained, which would prevent having multiple records of pre-scouting data for redundancy and comparison.
Also, we need to add support for images. We can upload images and store them on the server, but we need to implement that.