[mythtv-users] Schedules direct JSON information compared to XMLTV information and mythmetadatalookup

[jrh]

On Oct 2, 2014, at 1:02 PM, Gary Buhrmaster <gary.buhrmaster at gmail.com> wrote:

> On Thu, Oct 2, 2014 at 11:52 AM, jrh <jharbestonus at gmail.com> wrote:
> ...
>> Could this be used instead of using mythmetadatalookup?
> 
> At this point, I do not believe anyone has contributed
> a metadata grabber that supports any commercial service
> offering using licensed and paid for data (whether that is
> tms (via schedules direct), or fyi, or imdb, or something else).
> Since the grabber definition is in the database, it should
> be possible for you to write something to use (presumably)
> a local license file with the sources official API to access
> other metadata services, although I think it would be better
> still if the crowds were better at maintaining the free services
> data [one reaps what one sows, so everyone needs to be
> both a giver as well as a taker; if the data is bad, one only
> has to look in the mirror to identify who can fix it].
> _______

Understood regarding the metadata grabber supporting a commercial service. What could be interesting is that the raw data from Schedules Direct contains almost all the data that would be fetched by the metadata lookup and doesn't have to be 'screen scraped'. Seems like that could be a good simplification of code. I'm just an everyday user of mythtv(since 2010), that does coding/support on 80's legacy software for my day job. 5 or so years in the future after I retire, I could see myself taking on something like this. 

Robert,

Does  your example code import all the fields into mythtv that you describe in the referenced document? or just the fields that map to what are currently getting imported via the xmltv import?

Regards!