History:Advanced Entity: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(formulation (Imported from MoinMoin))
 
(33 intermediate revisions by 8 users not shown)
Line 1: Line 1:
This page was a collective proposal for new entities that had not yet been implemented, their behaviour and how to present them. Many of the ideas here had since been implemented, as of March 2010. Those which had not been, and were not yet planned (the NGS release), have been split off to [[Advanced Entity (Post-NGS)]] for future discussion/development.
=New Entities Proposal=


See [[Data Elements For Advanced Relationships|DataElementsForAdvancedRelationships]] for an older proposal.
'''Status:''' [[Image:Attention.png]] ''This page is a collective proposal for new entities that have not yet been implemented, their behaviour and how to present them.''


==Idea==
==Idea==
Line 16: Line 16:


The following entities with the described behaviour are proposed:
The following entities with the described behaviour are proposed:
* Label For record labels, subdivisions of labels and distributors
* Label
** field: [[Label Code|LabelCode]]
** field: [[Label Code|LabelCode]]
** AR to URL possible (label website (use "official website"?), Discogs entry, Wikipedia, discography site)
** AR to URL possible (label website (use "official website"?), Discogs entry, Wikipedia, discography site)
** AR to Artist ("is/was signed to from ... to ...")
** AR to Artist ("is/was signed to from ... to ...")
** AR to Series
** AR to Label ("is sub-division of", "is distributor of"?)
** AR to Label ("is sub-division of", "is distributor of"?)
** album listing with all albums which have the id of this label in a release
** album listing with all albums which have the id of this label in a release
** "View Mods" for related edits
** "View Mods" for related edits


** [[Album Group|AlbumGroup]]s These would be called differently depending the proposal, so I just list the proposals here:
* Series
*** [[Release Groups|ReleaseGroups]] -- This was written before [[Advanced Relationships|AdvancedRelationships]] and therefore is conceived as a new [[Core Entity|CoreEntity]], but should not be one, would we implement this now.
** examples: [http://musicbrainz.org/newsearch.html?limit=0&table=album&search=caf%C3%A9+del+mar Café del Mar], [http://musicbrainz.org/newsearch.html?limit=0&table=album&search=Ministry+of+Sound Ministry of Sound], [http://musicbrainz.org/newsearch.html?limit=0&table=album&search=kontor Kontor], [http://musicbrainz.org/newsearch.html?limit=0&table=album&search=hed+kandi Hed Kandi], ...
*** [[Release Handling Philosophy|ReleaseHandlingPhilosophy]] -- This proposal ''could'' be implemented without an additional entity, but an explicit album group would not really hurt.
** AR to URL possible (series website (use "official website"?), Wikipedia, discography site)
Additionally one could think of different types of [[Album Group|AlbumGroup]]s like:
** lists all albums belonging to this series. Linkage through AR or through album attribute?
*** [[Release Group|ReleaseGroup]]/[[Edition Group|EditionGroup]] for different variants of one idea of an album
** "View Mods" for related edits
One [[Album Entity|AlbumEntity]] could be member of several groups - like Apocalyptica's "Cult: Special Edition (disc 1)" is in the same [[Edition Group|EditionGroup]] like the original "Cult" release but also in a [[Box Set|BoxSet]] together with "Cult: Special Edition (disc 2)" (but that could lead to multi-inheritance problems if you also want to use an inheritance mechanism like for [[Artist Group|ArtistGroup]]s). And you have to differentiate between a group of albums representing the same abstract album idea and groups of albums representing the same recording (important for linking recording information to the group).

** [[Track Group|TrackGroup]]s Track groups would be the equivalent to the abstract idea of a '''Song''' while the '''Track''' entity stores data for one version/release of a track (which perhaps still could be used for several albums - so one Track entity could be on an album and a compilation).
* Album Groups
*** Easier to link covers, participating artist infos and so on
<ul><li style="list-style-type:none">These would be called differently depending the proposal, so I just list the proposals here:
Like for albums you have to separate between groups of tracks representing the same abstract song (of one artist!) and groups of tracks representing the same recording of a song.
* [[Release Groups|ReleaseGroups]] -- This was written before [[Advanced Relationships|AdvancedRelationships]] and therefore is conceived as a new [[Core Entity|CoreEntity]], but should not be one, would we implement this now.
For new more detailed proposals for such groups see [[Album Rework|AlbumRework]] and [[Track Grouping|TrackGrouping]].
* [[Album Handling Philosophy|AlbumHandlingPhilosophy]] -- This proposal ''could'' be implemented without an additional entity, but an explicit album group would not really hurt.
</ul>


==Description==
==Description==


(More detailed description missing...)
(More detailed description missing...)

Note that both distributors and labels are described with the entity Label.


Label entities could then be used in extended release infos of albums. Both labels and series help to keep an overview of the related releases and the related mods.
Label entities could then be used in extended release infos of albums. Both labels and series help to keep an overview of the related releases and the related mods.


Open question: link albums belonging to a series to the Series entity instead of [[Various Artists|VariousArtists]]? Or better leave VA as the artist because a Series entity is not an Artist entity and this could cause implementation problems? So better link it *additionally* to the Series?
Open question: link albums belonging to a series to the Series entity instead of [[Various Artists|VariousArtists]]? Or better leave VA as the artist because a Series entity is not an Artist entity and this could cause implementation problems? So better link it *additionally* to the Series?

==Discussion==

Me love! Especially I love the series proposal if it would mean that we would dump the volume number style guideline (which is used for keeping releases in a series together even if their names don't really imply it). //[[User:bnw|bnw]]

I'm not too sure of the new name of this page. Is this really about Advanced Entities? As I understood it it was just a suggestion for a few new 'normal' entrities. //[[User:bnw|bnw]]
----| Original author: [[User:Shepard|Shepard]]


[[Category:To Be Reviewed]] [[Category:Discussion]] [[Category:Development]] [[Category:Proposal]]
[[Category:History]] [[Category:Development]]

Latest revision as of 07:58, 28 September 2011

This page was a collective proposal for new entities that had not yet been implemented, their behaviour and how to present them. Many of the ideas here had since been implemented, as of March 2010. Those which had not been, and were not yet planned (the NGS release), have been split off to Advanced Entity (Post-NGS) for future discussion/development.

See DataElementsForAdvancedRelationships for an older proposal.

Idea

At the moment we have the following CoreEntities:

  • Album
  • Track

We already have the following AdvancedEntity:

  • URL

The following entities with the described behaviour are proposed:

  • Label For record labels, subdivisions of labels and distributors
    • field: LabelCode
    • AR to URL possible (label website (use "official website"?), Discogs entry, Wikipedia, discography site)
    • AR to Artist ("is/was signed to from ... to ...")
    • AR to Label ("is sub-division of", "is distributor of"?)
    • album listing with all albums which have the id of this label in a release
    • "View Mods" for related edits
    • AlbumGroups These would be called differently depending the proposal, so I just list the proposals here:

Additionally one could think of different types of AlbumGroups like:

One AlbumEntity could be member of several groups - like Apocalyptica's "Cult: Special Edition (disc 1)" is in the same EditionGroup like the original "Cult" release but also in a BoxSet together with "Cult: Special Edition (disc 2)" (but that could lead to multi-inheritance problems if you also want to use an inheritance mechanism like for ArtistGroups). And you have to differentiate between a group of albums representing the same abstract album idea and groups of albums representing the same recording (important for linking recording information to the group).

    • TrackGroups Track groups would be the equivalent to the abstract idea of a Song while the Track entity stores data for one version/release of a track (which perhaps still could be used for several albums - so one Track entity could be on an album and a compilation).
      • Easier to link covers, participating artist infos and so on

Like for albums you have to separate between groups of tracks representing the same abstract song (of one artist!) and groups of tracks representing the same recording of a song. For new more detailed proposals for such groups see AlbumRework and TrackGrouping.

Description

(More detailed description missing...)

Label entities could then be used in extended release infos of albums. Both labels and series help to keep an overview of the related releases and the related mods.

Open question: link albums belonging to a series to the Series entity instead of VariousArtists? Or better leave VA as the artist because a Series entity is not an Artist entity and this could cause implementation problems? So better link it *additionally* to the Series?