Re: [Xmltv-devel] Schedules Direct JSON API grabber

[Kevin G. <kgr...@gm...>]

On Thu, Dec 11, 2014 at 10:27 AM, Robert Eden <rm...@gm...> wrote:

> Sorry for the delay, but I just got around to trying this again (been
> buried by replacement SD datadirect server)... Excellent progress, and
> usable even at this point.
>

That's okay.  My delay was even longer...


> Some suggestions.
>
> 1. add a --debug switch and only output debugging if you specify it.
>

Done. There are only a few status messages now by default.  These can also
be disabled with --quiet.  Error messages are always enabled.


> 2. during config, ask the user for a suggested timezone and convert times
> to that (with an offset of course).  Folks looking at the raw XML for
> troubleshooting aren't going to want to see UTC, heck, some apps ignore
> timezone and need the XMLTV file in a local timezone.
>

I guess that may be a nice to have.  I just assumed most apps would handle
UTC.  It does seem to be the most logical format to use in a storage format
and then only use local time for display.


> 3. Include more station details (like network, etc).  I suspect this is
> already on your TODO list.
>

There may be some missing metadata, but I think I got most of it. It is a
little confusing in some cases figuring out the appropriate mapping from
the SD fields to the XMLTV fields.


> 4. Change channel-ids to a domain style format... maybe  ###.
> json.schedulesdirect.org
>

Done.


> Probably after #1, we can even add it to the distribution.. it appears
> usable now, and with all the international coverage may really help some
> folk.
>
>
> http://forums.schedulesdirect.org/viewtopic.php?f=16&t=2616&p=8053&hilit=international#p8053
>

Interesting. I didn't realize schedules direct had lineups for outside of
Canada and the USA. During the config stage when searching for lineups I
only prompt for USA or CAN, I guess this may need to be extended.

I have also fixed a couple other minor issues in the last couple days.  I
really should put a little more effort into better error handling soon.


Kevin