Posted by Joe Ross at 2/4/2001 4:10 AM EST
Engineer on team #330, Beach Bot, from Hope Chapel Academy and NASA/JPL , J&F Machine, and Raytheon.
In Reply to: Re: Point…
Posted by Mike Soukup on 2/3/2001 12:12 PM EST:
I agree that it is too late to do a common scouting system for this year. But, I do have a few ideas for next year.
The way that I see it, there are many different databases, each with its own specialty and quirks. This obviously has its disadvantages. It also has many advantages because there are certain things that ateam looks for in a database. By doing their own, a team can get exactly what they want.
I have an idea for how to combine the best of both systems. It all relys upon a common database that is shared among all teams.
This database would have to encompase all the different features of the each team’s this year. This means that it has to have detailed robot info entered by the team, have much scouting data, and also have detailed match information.
This database would be what everything revolves around. the database, with its commmon format, would then be availible for anyone to make any type of interface.
For example, Nate Smith seems to be very good at programming a palm. He could create a data entry system for the palm/visor. Once he is finished, he could release it to the rest of the FIRST community for use for entering data into the database.
Some other team may make a really cool application for entering in match data. Another team might make a web interface for searching the robot section of the database, and someone else might make a cool way to look at the match data. Another team might design a wireless network that could be used to enter data.
By using each teams strengths, we could make a killer system.
The biggest problem with this system is the design and maintenence of the database. It would take a while and a lot of input so that the database has everything that everyone would be interseted. Then we also would need a central location to host the database. Each team would be able to update it, but there would need to be one copy that is considered the main one.
This is where the person who isn’t affiliated with a team comes in. That person would be in charge of the maintenece of the database. It wouldn’t have to be someone not affiliated with a team, but there would need to be one person who would step up and take charge of the database.
In short, what I am proposing is a common databases with many different UIs.
That is my 3 cents.