Hi guys

Some of you probably have read I'm working on an extension to import CDDB disc info into eZ publish. I'd like to know how you would structure this disc info into the eZ publish content tree. Would you use seperate disc - track objects or put it all in one class?

You can view a little example of the disc info I get from freedb at http://blog.coomanskristof.be/wp-content/uploads/2006/06/cddb.jpg.

Thanks in advance!

Hi,

I guess it depends on what you want to do with it. This being said, one of the nice things about MP3s is that we focus more on each track individualy (I'm listing to "so what"), and not on the track as an item of the disk (pre MP3, it was track #1 of "kind of blue").

I think that's likely that each track is going to live it's own life, independant of the album. Having different nodes for each track would is things like creating your own compliations and so on.

X+

P.S. Replacing Miles by Tool works as well for my example ;)

Hi guys, me again :-)

To make my online disc collection more attractive, I'd also like to display the cover images. I started playing with the Amazon SOAP webservice (using nusoap, currently only a CLI script). I'm already able to search for items and retrieve metadata and images.

Now my question is: do you see any way to make a generally useable eZ publish extension out of this? It could be of use for other products as well (DVD's, ...).

Xavier, you have written something to query Amazon and Google in the past ( http://ez.no/community/forum/developer/include_google_search )? Does this only integrate in the search module?

Hi,

I'd say that you can use the priority of the children as the track number.

X+