The good Google Script giveth and the good Google Script taketh away.
I can access Yahoo but only once. After that I’m locked out again. The credentials being created work off the bat but like a deep flyout to center field die on the way down. Somehow I’m missing the step that maintains access. What is the Google Script equivalent of cialis for oAuth connections? Where do I find digital bathtubs?
I’ve finally successfully pulled *some* data from Yahoo’s servers. Behold, in all it’s glory:
<?xml version=”1.0″ encoding=”UTF-8″?>
<query xmlns:yahoo=”http://www.yahooapis.com/v1/base.rng” yahoo:count=”1″ yahoo:created=”2013-06-03T22:20:20Z” yahoo:lang=”en-US”><results><game xmlns=”http://fantasysports.yahooapis.com/fantasy/v2/base.rng”>
</game></results></query><!– total: 161 –>
<!– engine4.yql.ne1.yahoo.com –>
While it looks like gibberish it contains the identifying number of the current (2013) NFL season (314) which I’ve been looking for since… oh I don’t know… last year sometime. BUT I FOUND IT NOW. With that I can build requests to access player data for specific fantasy leagues.
But you may ask yourself, “Self, if all the players are available in all the same leagues why do you need stats specific to a fantasy league, aren’t they all in the NFL?”
Good questions, Self. I need player data specific to each fantasy league because that’ll contain their points totals for that league’s scoring system so I can properly populate player data for the offline draft.
Good news, since getting stats straight from the horse’s mouth is the better way to do this. Now I have some code to troll though, if you’ll excuse me.
In my futile attempts to get access to closely guarded data, I may have to improvise. Yahoo isn’t keen on display EASILY AVAILABLE PLAYER STATS CONVERTED TO POINTS because they’re dumb, so I may avoid using Yahoo’s API’s all together and find another source of data.
Fortunately since the points are based off the stats, if I can’t get the points I’ll get the stats and convert it to points my-damn-self. Bye weeks cause another problem but that data is easily available as well. I just have to do the hard work of putting it all together.
At least, I think so. Go home Yahoo, you’re drunk.
Yahoo! doesn’t seem to handle keeper leagues well so I’m going to try to make things easier on myself; instead of wasting hours copying player stats into a Google spreadsheet I’m going to try to get the spreadsheet to do the work for me.
Inside of each Google spreadsheet is the ability to run background scripts when the page opens (or you tell it to). In this case I want to use my API keys to pull certain player data from their server, parse it into mutable objects, then populate the spreadsheet with the pertinent data (name, position, team, bye week, and expected points).
There are some other things I want to get to work, but this is the most time intensive on my end. This should also help with my other drafts, since Yahoo! doesn’t want to behave*.
*It may actually work properly, but this is way more fun and customizable for the other leagues I’m in too.
This (linky linky) is pretty cool. It should be more functional than the current round of watches out there since it’s built to do more than tell time and has a dev kit in the works for people like me. I’ll be sure to keep track of my thoughts here, so stay tuned!
I may have some very exciting news in the coming weeks involving Softball Stats Pro, stay tuned!