[mythtv-users] MythArchive and MythCollection

Simon Dyson sdyson at themaelstrom.co.uk
Wed Nov 15 20:58:18 UTC 2006

I think Tom has a great idea here. At the moment I'm keeping my burnt 
DVDs in a large flight case which saves a lot of space but isn't 
anywhere near as easy to browse as a load of DVDs cases on the shelf so 
it would be good to browse the collection via MythTV.

Tom, it sounds like what you've done integrates with MythWeb but not 
with MythFrontend - is that right?


tom roth wrote:
> Now that MythArchive is so successfull (Congratulations to Paul) i 
> recently experienced a spark of interest in my MythArchive Extension 
> MythCollection.
> The Goal of MythCollection is to help you keep track on the movies you 
> have archived. It also supports you on the generation of a nice 
> CD-Cover and there is a (rudimentary) webfrontend for mythburn. Now 
> before you all get excited, while this works rather well for me, this 
> is pre-alpha software. It consists of:
> - mythcollect.py a python script that gets called by mythburn.py, 
> looks at the jobfile and writes title and description of the archived 
> files into the mythcollection table. Of course this is optional and 
> can be configured with an option in mydata.xml.
> - mythcover.py, another python script that gets (optionaly) called by 
> mythcollect.py and creates a cd-cover using a screenshot of the movie.
> - MythCollection, just another moviedatabase integrated with the 
> mythtv database. MythCollection does the following:
> - - Enrich the movie information by  an IMDB lookup.
> - - Provides a browse and a search interface (using ajax)
> - - Manual Editing
> - - Shelf organisation with index markers
> - - CD-Cover generation. Here mythcover.py is called again, but this 
> time there a more options to influence the generation process.
> I use MythCollection to keep track of all my Movie including the DVDs 
> i bought. I also set up a rudimentary webinterface to call mythburn from.
> If this is of any interest to you i could send you the code and help 
> you setting it all up until a installation routine is written.
> At this stage it would be best if you knew how to write bugreports and 
> a little python and/or ruby would be helpfull.
> MythCollection is a ruby on rails application. Now why did i do this ?
> There are several reasons:
> - I looked at mythweb and found the code quite complicated to 
> integrate another module. This is by all means no complaint against 
> mythweb, which i like and use often.
> - My first Announcement of MythCollection met with little interest so 
> i choose a route more convenient for me.
> - I wanted a granular Authentication schema which allows me to put my 
> collection online for my friends to see, but restrict the editing part.
> - Configuring apache is rather complicated and i do not want to 
> support that.
> - I think with webapplications you can do seamless integrations on the 
> frontendview even with diffrent backends.
> - Rails is fun ;-)
> regards  tom
> ------------------------------------------------------------------------
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

More information about the mythtv-users mailing list