[mythtv-users] Mooting architecture for a DataDirect replacement

Jay R. Ashworth jra at baylink.com
Fri Jun 22 17:58:31 UTC 2007


On Fri, Jun 22, 2007 at 12:42:53PM -0500, jedi at mishnet.org wrote:
> > On Thursday 21 June 2007 20:19, Christopher X. Candreva wrote:
> >> On Thu, 21 Jun 2007, Jay R. Ashworth wrote:
> [deletia]
> > - An awful lot of what's broadcast is repeats, movies, etc. I wonder if
> >   some way of separating the schedule data from the program data would
> >   be desirable, or at least providing a community-run database of
> 
>     Well, something like Program Name, Season Name, Episode Number and
> Release date should be sufficient enough information to uniquely
> identify a show. That could be embedded into the main guide data.

I'm not entirely sure what's the best primary key.  I think Show Title,
Season# , Episode#, myself.  But what do you do with the clip shows
from Grey's Anatomy that were episode 22a?

Optimally, you want to use Production Company Name, Production Number,
but then you have to deference it *somewhere*.  "Metadata transport -
closing the loop".  That's what this thread should be called.

>     Episode Titles and Descriptions could be something that could be
> gotten either from a different source or as part of a separate
> dataset.

And the descriptions potentially from several sources...  As well as
cast lists.

>     A cddb for TV And movies would be handy for those of us that have
> video jukeboxes.

Yup.

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274


More information about the mythtv-users mailing list