more json data available from WNL page #2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I took a look at the WNL homepage source for the first time since I found the json URL. At least most of the JS that fetches dynamic information is in the script element at the bottom. Besides the timetable json URL, theres one for M-scale, and another for video IDs and thumbnail URLs of the live stream and three most recent videos.
It would be nice to record the M-scale and especially the video IDs, maybe even the thumbnail jpegs, of the live streams in the database.
You can even see their functions for translating the caster and program names in the json record.
And of course their JS functions for extracting the data from the json records are there too.
This is good to know. When I get a little more free time, I'll think about recording more data.
I'm just taking notes publically for later.
We're about an hour into Evening with Airin. Here's the thumbnail.
The video id was returned as:
pX0ZEKzxnb4
.The video id and thumbnail will have to be captured separately from the schedule, because they're not available until the live broadcast starts.
I also just noticed that the thumbnail url can be derived from the video id. That's one less thing I have to store in the database.
For recording purposes, I'm going to treat mscale as a value that's independent of the schedule. The unique
jst
column that exists in both theschedule
andmscale
tables can be used to join the data together.@pta - The
schedule
table has avideo_id
column that will be updated the minute after the JSON reveals a new live video id via cron job. I currently only sync the db found on https://gg.vern.cc/wn-data/wn.db twice a day, but maybe I'll do it more often going forward. We'll see.There's also an
mscale
table that records the M-scale value hourly. Theschedule
andmscale
table can be joined using theirjst
column which both have.I may redo the
schedule_joined
view to include this new data. It might look something like this:I think I should link the db in the next OP, under the schedule links, with a short description.
Feel free. Eventually a site that queries the db will be made, but until that exists, a link to the raw db may suffice.
Here's an unstyled dump of the schedule.
https://gg.vern.cc/wn/