Thursday 08 June 2006 7:37:37 pm - 6 replies
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!
Thursday 08 June 2006 10:25:54 pm
Presented view looks very nice. How you solved searching for track which exists on several discs? disc - track variant will be more flexible. Disc as parent object and tracks as children. Import should use browse mode for better navigation in content structure where you want to place it.
Modified on Thursday 08 June 2006 10:44:29 pm by Łukasz Serwatka
Friday 09 June 2006 8:52:32 am
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.
P.S. Replacing Miles by Tool works as well for my example
Modified on Friday 09 June 2006 8:52:54 am by Xavier Dutoit
Sunday 11 June 2006 11:21:00 am
Thanks for your input!
What would you do with the track offsets? Should they all be stored in the disc object, or in the track object? Or should I just drop them?
What if I have 2 or more discs with exactly the same song? Would you use the same track object again with an additional node location?
Friday 28 July 2006 6:29:38 pm
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?
Thursday 03 August 2006 10:27:00 pm
In the past as you say
I integrated it with Amazon, google search and some wether report service.The weather isn't about search, but the two other where. Contact me if you want more detail, that's kind of a long time ago
Modified on Thursday 03 August 2006 10:28:54 pm by Xavier Dutoit
You must be logged in to post messages in this topic!