Re-reading this post...
2006/4/2, Adam Golding [EMAIL PROTECTED]:
note that we also need a way to handle multiple publications of a single
work (they might have different metronome markings, for instance.. or even
be in different keys)
Do you have any actual example of this? This would have
On 4/7/06, mud crow [EMAIL PROTECTED] wrote:
Not all parodys are covers
snip
I think that either the word cover should not be used in context with parody
or that two parody ARs should be added. Also parody needs to be track-artist
and track-track in relationships.
[track] is a parody cover
2006/4/5, Nathan Noble [EMAIL PROTECTED]:
This would imply creating perhaps hundreds of sparsely
populated db columns, or a more sophisticated schema
with dynamic attributes. Performance has to be
considered.
Not stored in specific columns. The AR system gives an example of an
alternative
On 4/7/06, Frederic Da Vitoria [EMAIL PROTECTED] wrote:
Re-reading this post...2006/4/2, Adam Golding [EMAIL PROTECTED]: note that we also need a way to handle multiple publications of a single
work (they might have different metronome markings, for instance.. or even be in different keys)Do you
Don Redman wrote:
Under this view a cover is taken in a very broad sense as a work
based on another. Parody is then an adjective, describing that it is
based on it in a porodying way.
I would suggest to make the _intention_ to humorously reinterpret a song
(of another artist). I know some
I think Don's summary of the DVD issues is pretty close to what we
should go with.
official_sounding_voice
1. We will store DVDs in MusicBrainz and we'll start doing this by
using the existing album structure.
2. We will not use DVD in the title.
3. We can start adding DVDs into
