History:Next Generation Schema/History: Difference between revisions
(correct link (Imported from MoinMoin)) |
(intertwingling (Imported from MoinMoin)) |
||
| Line 18: | Line 18: | ||
* [[Getting Rid Of Featuring Artist Style|GettingRidOfFeaturingArtistStyle]] (for support of multiple artists of one track/album or alternatives) |
* [[Getting Rid Of Featuring Artist Style|GettingRidOfFeaturingArtistStyle]] (for support of multiple artists of one track/album or alternatives) |
||
* [[Disentangle Interfaces From Schema|DisentangleInterfacesFromSchema]] asks what a schema change can and should do, and more importantly what it should not do. |
* [[Disentangle Interfaces From Schema|DisentangleInterfacesFromSchema]] asks what a schema change can and should do, and more importantly what it should not do. |
||
[[User:Shepard|Shepard]] and [[User:DonRedman|DonRedman]] have started [[Object Model|ObjectModel]], a collaborative document, that tries to describe all objects that [[MusicBrainz]] deals with in an abstract manner. This is ''not'' supposed to be a database schema, but some preliminary analysis that can then ''lead'' to a database schema (BIG difference!). |
|||
[[Category:To Be Reviewed]] [[Category:Development]] |
[[Category:To Be Reviewed]] [[Category:Development]] |
||
Revision as of 01:49, 18 November 2005
This is a process working towards a greater release covering a lot of database schema changes and the connected interface and client changes. (started in October 2005)
The changes are related to album groups, track groups, multiple artists and many more issues and produce a lot n:n tables.
At the moment we are in the planing phase so this is FutureWork.
Previous documents addressing those changes are (some only of historical interest):
- SchemaVersion2 (very early proposal from late 2001)
- BoxSet (addressing problems with grouping albums in boxes)
- ReleaseGroups (the proposal on which AlbumRework is mostly based on)
- AlbumHandlingPhilosophy (abandoned by the author in favour of AlbumRework)
The current rework is split into:
- AlbumRework (covering ReleaseTypeRestructuringProposal, ReleaseDataSet, ReleaseRegionStyle)
- TrackGrouping (not yet sanctioned ;))
- ArtistRework
- AdvancedEntity (for creating new entity types like the ones we already have (artists, albums, tracks, URLs))
- GettingRidOfFeaturingArtistStyle (for support of multiple artists of one track/album or alternatives)
- DisentangleInterfacesFromSchema asks what a schema change can and should do, and more importantly what it should not do.
Shepard and DonRedman have started ObjectModel, a collaborative document, that tries to describe all objects that MusicBrainz deals with in an abstract manner. This is not supposed to be a database schema, but some preliminary analysis that can then lead to a database schema (BIG difference!).
