Difference between revisions of "Advanced Relationship Type"
m (10 revision(s))
m (24 revision(s))
Revision as of 08:22, 15 March 2009
Types of AdvancedRelationships
Each relationship entered by a user belongs to one AdvancedRelationshipType. These types define:
- Which entities will be related (artists, releases, labels, tracks, etc)
- What AdvancedRelationshipAttribute
s go along with the relationship
- The LinkPhrase
s of the relationships, which describe how to write the relationship information in English sentences.
For example, the advanced relationship type "PerformerRelationshipType" can be used to link an artist (for example, Eric Clapton) to a track on which they performed (for example, Runaway Train). The definition of PerformerRelationshipType allows an optional attribute to specify the instrument he played (InstrumentRelationshipAttribute), so you can say if he played guitar. The definition also says how to construct an English sentence out of this data, so that the website can display the words "Runaway Train was performed by Eric Clapton".
s are themselves simply entries in another database table. This means that new ones can be defined, old ones deleted, and existing ones modified through a relatively simple user-interface which does not require hacking the database internals. Since this data is much more important than any other individual entries, editing of AdvancedRelationshipType
s is limited to selected users, called RelationshipEditor
s. There are more relationship editors than developers, and the process of adding a new relationship type is much simpler than adding a new database table, so this is a very fast way to expand and improve the MusicBrainzDatabase.
Note that some of these types might still be proposals, this will be stated on their respective page. There is also some good but slightly historical information about AdvancedRelationshipTypeDevelopment.
Looking to add a new relationship type for AR?
Existing Types of Relationships
Relationship types are grouped into thematic AdvancedRelationshipClass
es. These are explained here. All types that belong to one class are explained on the class page. There is also a complete list of relationship types further below.
- This denotes all artists who played on a specific performance of a work. This means that they actually produced some new audio material, e.g. who sung or played some instrument. Remixing existing audio material or engineering the audio signal is not covered by this class.
- This describes relationships between related works, e.g. works that are the same, remastered from another, a cover from another, etc.
- This denotes al artistic activity where existing recordings are used to create (remix) something new. You can specify who remixed what material on what work. This does not refer to mix engineers in studios etc.
- This denotes all artists who created some aspect of the general work, i.e. not a specific performance of it but the lyrics, the score or the arrangement.
- This denotes all people and institutions that were involved in the production on the work, but did not play music: the manager, cover designer, audio mix engineer, etc. but not actual performers or remixers.
- This describes who was a member of which group, who collaborated with whom etc.
- This describes family relationships and liasons between artists that are in the database anyway.
- These are links to records in affiliate databases
- These are links to discographic resources
- These are links to sites where you can download and/or buy the music. Note that these must be legal, or MusicBrainz will run into trouble!
- These are links to other databases about the artists, the music etc.
The following table shows all possible relationship combinations:
All official relationship types
The following is an automatically generated list of all AdvancedRelationshipType