On Sat, May 24, 2014 at 9:02 AM, Hoggins! <[email protected]> wrote:
> I like Jay Ashworth's solution, having some sort of a "related songs" > field. It is more flexible, and lightweight, and I wonder if it's > already possible to use one of the existing fields to achieve this, like > the "user defined" one, or something like that. > This approach unfortunately does not scale well at all. Imagine having to configure the set of 'related songs' for "Hey Jude". Of course, the entire Beatles catalog would be 'related'. What about John Lennon's "Imagine"? The entire "Wings" catalog would need to be entered as well. And don't forget all of the remakes of the various Beatles songs by other artists made over the years! All of this for *one* song. You'd then need to repeat this for *every one* of the other 'related' songs in this category. This is precisely the situation that scheduler codes were made for: configure a bunch of policy *once*, then associate that policy with some set of carts. Yes, to do it well, it's a lot of work. Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | Like the ski resort of girls looking for husbands and husbands looking | | for girls, the situation is not as symmetrical as it might seem. | | -- Alan McKay | |-------------------------------------------------------------------------|
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
