History:Artist Type Project Proposal

From MusicBrainz Wiki
Revision as of 16:57, 10 July 2006 by Shepard (talk | contribs) (update (Imported from MoinMoin))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Artist Type: Project

Description

A project consists of:

A single musician who is the sole engine, creative process behind the project.

  • may tour, with session musicians
  • pulls off of the same musicians, but still retains creative license. (if the musicians left, they could not perform the songs.)

A single release of multiple musicians that usually will not be retained after the project is released.

  • consists of musicians that do not usually work together, have groups or projects of their own and for the moment are combining to put together a number of songs as a single release, sometimes more. (though usually that would signify a collaboration - not to be utilized for a single song given feat.)

Or is a mixture of both: it has one or more creative forces behind it, who stay consistent over several releases, but changing performers.

Possible Values

Used with Types

Relating of artists to those of the type "Project" can be done with the following AdvancedRelationshipTypes:

  • Has/Had Project - This is the "owner" of the project
  • Is/Was involved in Project - These are the artists that were as well involved. If no project owner is known, or obvious, all artists involved should have this AR.

The exact link type definition:

project owner (0)

    * forward: has/had project(s)
    * reverse: is/was a project of
    * description: Indicates owners of a project.

project participant (0)

    * forward: {additional:additionally} takes/took part in project
    * reverse: has/had {additional} participant(s)
    * description: Indicates participants of a project.
    * attributes: additional=0-1