Difference between revisions of "Category:Relationship Attribute"

From MusicBrainz Wiki
(Additional information)
Line 19: Line 19:
 
{{:Founder Relationship Attribute}}
 
{{:Founder Relationship Attribute}}
 
{{:Guest Relationship Attribute}}
 
{{:Guest Relationship Attribute}}
 +
{{:Half Kinship Relationship Attribute}}
 
{{:Instrument Relationship Attribute}}
 
{{:Instrument Relationship Attribute}}
 
{{:License Relationship Attribute}}
 
{{:License Relationship Attribute}}
Line 24: Line 25:
 
{{:Orchestra Relationship Attribute}}
 
{{:Orchestra Relationship Attribute}}
 
{{:Parody Relationship Attribute}}
 
{{:Parody Relationship Attribute}}
 +
{{:Step Kinship Relationship Attribute}}
 
{{:Translated Relationship Attribute}}
 
{{:Translated Relationship Attribute}}
 
{{:Transliterated Relationship Attribute}}
 
{{:Transliterated Relationship Attribute}}

Revision as of 09:20, 31 March 2010

Advanced relationships may have attributes. The attributes which are allowed depend on the advanced relationship type.

Attributes

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. 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. 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. 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. 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. 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. 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. 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. Half Kinship Relationship Attribute 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. License Relationship Attribute 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. Orchestra Relationship Attribute 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. Step Kinship Relationship Attribute 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. 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. 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.

Additional information

This category currently contains no pages or media.