Or something.

We should render question marks instead of scores of negative one.

Apparently some EventTeams lack events

http://www.thebluealliance.com/team/2033

Traceback (most recent call last):
File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/init.py", line 515, in call
handler.get(*groups)
File "/base/data/home/apps/tbatv-prod/1.348062665901379930/controllers/team_controller.py", line 50, in get
events = [a.event for a in team.events if a.year == year]
AttributeError: 'NoneType' object has no attribute 'events'

Probably need to not include Teams, Matches until a Details query.

http://tbatv-prod.appspot.com/event/2008ma

Something is making us build this index:
year= ▲ , first_eid ▲

"year=" is not a property of Events. "year" is.

Probably an error with the bulkloader input data.

Affected events: 2007gl, 2008rr, 2007fl, 2007il, 2007pit, 2007roc, 2008ios

46 affected matches.

Keep serving sig badges off current TBA.net path, but fetch the data from the TBA.com API

Once site is serving off tba.com, add Like buttons.

assigned to chris

Probably put it in HTML comments for debug purposes for now.

Display something other than an empty match table when there are no matches.

We should probably set a "match_played" boolean on matches and flip it when we set scores. Then after events end, we should delete all their unplayed matches.

Create a new scraper for the event page to get award.

Insert award information on event details and team details page. Possibly the left side-bar will be a good place for it to live?

When a Team object doesn't exist (IE, the team has stopped existing and we didn't make a Team object), EventTeam objects get created with team fields. This is bad. If the Team object doesn't exist, create a stub during EventTeam creation.

This is a cover bug for memcache implementation.

Our custom Google Search is fancy, but it lacks in a lot of areas.

If you search for a team number we should notice that and jump right to the team's detail page. This should be the only time we should use a "I'm Feeling Lucky" feature. It'll become a lot harder to deal with if we ever get into FTC or FLL teams/events.

Set up jwplayer to do this properly.

Probably using Custom Google Search

I wasn't sure how useful this would be, just throwing the idea out on the table. If the event is currently in progress only then we should display the live video link (and if its from ustream we could embed the video).

This would require admin users to enter in the link to the video feed. Either that or we could create standard ustream accounts for broadcasting events...which will be very difficult to implement for just a few events.

Just idea.

Right now the outcome is:
Red Alliance: Score: Blue Alliance: Score:

Any ideas on how to make this easier to read for humans?

We have some Match data that doesn't have all of it's Teams, so we're rendering some hyperlinks to broken Teams.

A) We should manually add these Teams.
B) We should handle Team 404s without an Exception.

This is a cover bug for the API.

FIRST has updated Team TPIDs for 2011. 2010 TPIDs no longer work.

Serve page off tba.com, rather than appspot.com

Dump more information on Datafeed HTML output to better debug issues with scraper and parser.

Example:
http://tbatv-prod.appspot.com/team/195/2003

Galileo Q33: Score of 40 beats 101.

Team 177 doesn't have them.

Errors from new_team not having a team_number.

Probably not parsing USFIRST page correctly, probably because it's a non-2011 TPID. Need to get older TPIDs for team first?

Should at least not throw an exception, should probably enqueue TPID fetching, or something.

Icons are overlapping on stuff.

FIRST's tpid system is year-dependent, so you need to know what year your tpid is currently associated with. Then based on what year that is, you need to generate a session key associated with that year, and use that to fetch the team info.

Possible solutions:

• Store all historic Tpids for a team
• Store the tpid, and the year of the tpid, then fetch using the right urls/session_keys at fetch time
• Just store the latest Tpid, and use bulkloading to get old data in

I think storing the year of the tpid is the best idea, and then old teams just store of can stagnate until they have new data again. This problem is complicated. :-/