Difference between revisions of "User:CallerNo6/proposal/Relationship Types/Release Group-Release Group/Includes"

From MusicBrainz Wiki
(Link Phrases: grr, still have direction wrong)
(adding rfv link)
Line 5: Line 5:
 
|discussion=
 
|discussion=
 
|rfc=http://musicbrainz.1054305.n4.nabble.com/RFC-STYLE-331-add-composite-reissue-relationship-tp4667196.html
 
|rfc=http://musicbrainz.1054305.n4.nabble.com/RFC-STYLE-331-add-composite-reissue-relationship-tp4667196.html
|rfv=
+
|rfv=http://musicbrainz.1054305.n4.nabble.com/RFV-STYLE-331-add-composite-reissue-relationship-aka-includes-tp4668089.html
 
|style=
 
|style=
 
|ar=1
 
|ar=1

Revision as of 23:36, 10 September 2014


Status: This page describes an active advanced relationship proposal and is not official.



Proposal number: RFC-331:Release_Group included in Release_Group
Champion: user:Caller_number_six
Current status: active

RFC RFV

JIRA ticket http://tickets.musicbrainz.org/browse/STYLE-331

Description

This links two release group when one, typically a compilation or multi-disc collection, includes another.

A release group "includes" another when it retains:

  • The track list in essentially the same order as the original
  • The original title, possibly as a medium title, a super-title in the track list, or in reproduced cover art

Link Phrases

  • Forward link phrase: includes
  • Reverse link phrase: included in
  • Long link phrase: includes

Attributes

This relationship type doesn't allow any attributes.

Guidelines

A release group generally doesn't "include" singles unless it is explicitly a compilation of singles. To link a single to the album it appears on, use the Single from relationship.

Examples