History:Advanced Entity

New Entities Proposal

Status: This page is a collective proposal for new entities that have not yet been implemented, their behaviour and how to present them.

Idea

At the moment we have the following CoreEntities:

• Artist
  • related concepts: Group, Band, Orchestra, Person, LegalName, PerformanceName, RoleName, FictionalPerson/Character

• 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 Series
  • 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

• Series

• For compilation series
  • examples: Café del Mar, Ministry of Sound, Kontor, Hed Kandi, ...
  • AR to URL possible (series website (use "official website"?), Wikipedia, discography site)
  • lists all albums belonging to this series. Linkage through AR or through album attribute?
  • "View Mods" for related edits

• Album Groups

• These would be called differently depending the proposal, so I just list the proposals here:
  • ReleaseGroups -- This was written before AdvancedRelationships and therefore is conceived as a new CoreEntity, but should not be one, would we implement this now.
  • AlbumHandlingPhilosophy -- This proposal could be implemented without an additional entity, but an explicit album group would not really hurt. Additionally one could think of different types of AlbumGroups like:
  • ReleaseGroup/EditionGroup for different variants of one idea of an album
  • BoxSet for different albums belonging to one set

• Track Groups

• Another "meta entity". If you think of albums as an abstract idea then album groups would represent this and Album entities would store the actual release data. The same can be applied for tracks: 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

• Studio

• For recording studios
  • AR to Album/Track ("has [instrument] recordings from ... to ... in")

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?

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). //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. //bnw

---

| Original author: Shepard