Difference between revisions of "Relationships"

From MusicBrainz Wiki
(Bring back up to date text from Cat page)
m
 
(19 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{| width="100%"
+
Relationships are a way to represent all the different ways in which [[MusicBrainz Entity|entities]] are connected to each other and to URLs outside MusicBrainz. To know more about how to add them, see [[How to Add Relationships]].
| style="border:0;" |
 
{| cellspacing="0" cellpadding="0" style="clear: {{{clear|left}}}; margin-bottom: .5em; float: left; padding: .5em 1.4em .8em 0; background: none; width: {{{width|{{{1|auto}}}}}};" {{#if:{{{limit|}}}|class="toclimit-{{{limit}}}"}}
 
| __TOC__
 
|}
 
{| cellspacing="0" cellpadding="10" style="clear: {{{clear|right}}}; margin-bottom: .5em; float: right; padding: .5em 0 .8em 1.4em; background: none; width: {{{width|{{{1|auto}}}}}};" {{#if:{{{limit|}}}|class="toclimit-{{{limit}}}"}}
 
| {{AdvancedRelationshipNavigation}}
 
|}
 
|}
 
  
An advanced relationship is a way to represent all the various inter-relationships between [[MusicBrainz Entity|entities]], as well as relationships from [[MusicBrainz Entity|entities]] to information and resources found outside of the [[MusicBrainz Database|MusicBrainz database]].
+
* [[recording:271051c3-1a4c-4612-8c6e-2a5400e37b56|The Rockafeller Skank]] by Fatboy Slim includes a sample from the Just Brothers song [[recording:0ad2aa31-cf5f-4ef4-93d8-4568d404323b|Sliced Tomato]].
 
 
For example:
 
* The song [[track:271051c3-1a4c-4612-8c6e-2a5400e37b56|Rockafella Skank]] by Fatboy Slim includes a sample from the Just Brothers song [[track:0ad2aa31-cf5f-4ef4-93d8-4568d404323b|Sliced Tomato]].
 
 
* [[artist:85994c53-062f-462e-95fd-3a521dd1fcd2|Paul Di'Anno]] was a member of [[artist:ca891d65-d9b0-4258-89f7-e6ba29d83767|Iron Maiden]] from 1977 until 1981.
 
* [[artist:85994c53-062f-462e-95fd-3a521dd1fcd2|Paul Di'Anno]] was a member of [[artist:ca891d65-d9b0-4258-89f7-e6ba29d83767|Iron Maiden]] from 1977 until 1981.
* The Metallica album [[release:5997cf87-5225-4830-9edf-358638a24905.html|St. Anger]] was produced by [[artist:4f0730d0-fd52-4818-8a5d-f3f69ce8f378.html|Bob Rock]] & [[artist:65f4f0c5-ef9e-490c-aee3-909e7ae6b2ab.html|Metallica]].
+
* The Metallica album [[release:5997cf87-5225-4830-9edf-358638a24905|St. Anger]] was produced by [[artist:4f0730d0-fd52-4818-8a5d-f3f69ce8f378|Bob Rock]] & [[artist:65f4f0c5-ef9e-490c-aee3-909e7ae6b2ab|Metallica]].
 
+
* [[artist:486067ad-56d6-48b5-957b-d6cfe3e1af73|Perfume]] have an official site at http://www.perfume-web.jp/.
All of this information is stored in a single table in the database, and there is a single user interface for adding new information. In this way, [[MusicBrainz]] has a fairly simple way to deal with extremely complicated data.
 
 
 
==Getting Started==
 
 
 
There is a tutorial at [[How To Make Relationships]].
 
 
 
==Advanced Relationship Types==
 
 
 
Each relationship entered by a user belongs to one [[Advanced Relationship Type]]. These types define:
 
* Which entities will be related (artists, albums, tracks, etc)
 
* What [[Advanced Relationship Attribute]]s go along with the relationship
 
* The link phrases of the relationships, which describe relationship information in an English sentence.
 
 
 
For example, the relationship type "[[Performer Relationship Type]]" can be used to link an artist (for example, [[artist:618b6900-0618-4f1e-b835-bccb17f84294|Eric Clapton]]) to a track on which they performed (for example, [[track:64d0220a-0587-43c9-b7e3-809e8c06542b.html|Runaway Train]]). The definition of [[Performer Relationship Type]] allows an optional attribute to specify the instrument he played ([[Instrument Relationship Attribute]]), 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".
 
 
 
These [[Advanced Relationship Type]]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 [[Advanced Relationship Type]]s is limited to selected users, called [[Relationship Editor]]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 [[MusicBrainz Database]].
 
 
 
[[:Category:Relationship Type|Relationship type]]s includes a list of all of the relationship types currently defined, as well as documentation for each individual relationship type.
 
  
==Style==
+
==Relationship types==
Please see [[Advanced Relationship Style]].
 
  
==Creating and editing relationships==
+
There are a huge number of different relationship types. The lists (organised per types of entities they connect) can be checked at the [[mb:relationships|relationship type table]].
The types and attributes of advanced relationships are managed by [[Relationship Editor]]s.  They implement new relationships and changes to existing relationships following the passage of a [[Proposals|proposal]] to do so.
 
  
While there are very few [[Relationship Editor]]s, anyone can propose new relationships or changes to existing relationships, using the [[Proposals|proposal process]].  While most editors are not able to directly edit the types of advanced relationships, it can be useful to know what [[Advanced Relationship Attribute Syntax|advanced relationship attribute syntax]] itself supports, as it will be used to implement any relationship proposal which passes RFV.
+
==Guidelines==
  
==History==
+
Please see the [[Style/Relationships|general guidelines for relationships]], the [[Style/Relationships/URLs|guidelines for URLs]], and also the documentation for the specific relationship type you're using, accessible from the [[mb:relationships|relationship type table]].
Advanced Relationships were first officially proposed [[How Advanced Relationships Works|here]][[User:DaveEvans|Dave Evans]] created the database structure to allow relationships, and wrote tools for allowing the user to define a type of relationship.  However, the code for linking two entities together and the UI to manipulate relationships themselves was left undone.
 
  
In November of 2004, [[User:RobertKaye|Robert Kaye]] took over working on the user interface and [[User:DonRedman|Don Redman]] became the [[Proposals|Idea Champion]] for advanced relationships.  The design documents of the time, including the [[Advanced Relationship Type Development|original set of relationship types]], make for interesting reading:  [[Simple Advanced Relationships Interface]] describes the initial development of the UI and model for editing relationships, while [[Fancy Advanced Relationships Interface]] describes some then-future ideas for development of that relationships UI and model.
+
==Credits==
 +
Credits allow indicating that, for example, songwriting was credited to an artist's legal name, and not his main (performance) name.
  
On April 10, 2005, development was completed, and advanced relationship support was officially added to the database.
+
==Attributes==
 +
Relationships can have attributes which modify the relationship. There is a [[mb:relationship-attributes|list of all attributes]], but the attributes which are available, and how they should be used, depends on the relationship type, so see the documentation for the relationship you want to use for more information.
  
[[User:RobertKaye|RobertKaye]] and [[User:DonRedman|DonRedman]] defined the original set of [[:Category:Relationship Type|relationship types]]; all additions, removals, and changes to the list of [[:Category:Relationship Type|relationship types]] since then have been made by the [[Proposals|Style Council]].
+
===Dates===
  
 +
Some relationships have two date fields, a begin date and an end date, to store the period of time during which the relationship applied. The date can be the year, the year and the month or the full date. It is optional, so it can also be left blank. As with other attributes, see the documentation for the relationship types you are using.
  
[[Category:Documentation]][[Category:WikiDocs Page]]
+
[[Category:Documentation]] [[Category:WikiDocs Page]] [[Category:Relationships]]

Latest revision as of 12:53, 2 June 2015

Relationships are a way to represent all the different ways in which entities are connected to each other and to URLs outside MusicBrainz. To know more about how to add them, see How to Add Relationships.

Relationship types

There are a huge number of different relationship types. The lists (organised per types of entities they connect) can be checked at the relationship type table.

Guidelines

Please see the general guidelines for relationships, the guidelines for URLs, and also the documentation for the specific relationship type you're using, accessible from the relationship type table.

Credits

Credits allow indicating that, for example, songwriting was credited to an artist's legal name, and not his main (performance) name.

Attributes

Relationships can have attributes which modify the relationship. There is a list of all attributes, but the attributes which are available, and how they should be used, depends on the relationship type, so see the documentation for the relationship you want to use for more information.

Dates

Some relationships have two date fields, a begin date and an end date, to store the period of time during which the relationship applied. The date can be the year, the year and the month or the full date. It is optional, so it can also be left blank. As with other attributes, see the documentation for the relationship types you are using.