Relationship Type "Is a Mash-Up Of"
Link Phrases
release is a mash-up of release
release has mashed-up version(s) release
track is a mash-up of track
track has mashed-up version(s) track
Description
It is not always clear when a track is a MashUp, so you should use your best judgement as to determine when to use this, and be ready to argue the case in your moderations.
This relationship can be used to represent a release that is a MashUp of one or more other releases, or a track that is a MashUp of several other tracks. It is also currently possible to represent a release that is a MashUp of one or more tracks, but it is planned that we will remove this feature. It isn't possible to represent a track that is a MashUp of a release.
This AdvancedRelationshipType is part of the RemixRelationshipClass.
Relationship Attributes
None are appropriate.
Style
The person who made the MashUp should be the PrimaryArtist of the release or track. Alternatively, the RemixerRelationshipType can be used. Style guidelines for MashUps are kept at VersusStyle.
Examples
![[WWW]](http://wiki.musicbrainz.org/-/musicbrainz/img/moin-www.png)
Smells Like Booty (Nirvana vs. Destiny's Child) by 2 Many DJ's is a MashUp of Nirvana's Smells Like Teen Spirit and Bootylicious by Destiny's Child. - The Grey Album by Danger Mouse is a MashUp of The Black Album by Jay-Z and The Beatles (The White Album) by The Beatles.
Discussion
This relationship doesn't allow [release-track] or [track-release] EntityPairs. Those could conceivably be useful in a very few situations: however, those situations are so rare that adding these possibilities would just make things confusing. You can still represent a track which is a MashUp of all the tracks on a release, or a release which is a MashUp of many other tracks, using multiple [track-track] relationships.
It has been suggested that we should move away from the PrimaryArtist field altogether, and give all credits as advanced relationships. There are currently (2005-08-12) advanced relationships equivalents for every current use of PrimaryArtist, except MashUp. So if we ever did deprecate PrimaryArtist, we'd either need to create a new relationship type for "masher-upper", or use the RemixerRelationshipType.
I disagree. The proposed RemixRelationshipClass does not have sub-types to the RemixerRelationshipType on purpose. Since is is so difficult to tell RemixMeansDifferentThings apart, and a MashUp could even be considered a special kind of remix, I think it is perfectly OK to call the person doing a MashUp a remixer. I thought this was even consensus. --DonRedman
You're right - so right, that I modified the style section above to reflect that. Is that correct, or am I jumping the gun? --MatthewExon