History:Next Generation Schema/History: Difference between revisions
(intertwingling (Imported from MoinMoin)) |
(kinda status note and placing the current analysis at the top, linking to models (Imported from MoinMoin)) |
||
| Line 3: | Line 3: | ||
The changes are related to album groups, track groups, multiple artists and many more issues and produce a lot n:n tables. |
The changes are related to album groups, track groups, multiple artists and many more issues and produce a lot n:n tables. |
||
'''Please note''': ''Realizing we cannot just go and develop a new schema we are currently figuring out what objects we are generally dealing with in reality and what we would need to store in the database. So we are analyzing and developing an [[Object Model|ObjectModel]] first which later can lead to a new database schema. The objects in this model all represent different aspects of the world of music so we also need to deal with an [[Aspect Model|AspectModel]] describing in what different ways a user might want to look at the data. |
|||
At the moment we are in the planing phase so this is [[Future Work|FutureWork]]. |
|||
Being in the planning and collaborative brainstorming phase on that makes this process here [[Future Work|FutureWork]].'' |
|||
Previous documents addressing those changes are (some only of historical interest): |
Previous documents addressing those changes are (some only of historical interest): |
||
| Line 18: | Line 20: | ||
* [[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 23:58, 21 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.
Please note: Realizing we cannot just go and develop a new schema we are currently figuring out what objects we are generally dealing with in reality and what we would need to store in the database. So we are analyzing and developing an ObjectModel first which later can lead to a new database schema. The objects in this model all represent different aspects of the world of music so we also need to deal with an AspectModel describing in what different ways a user might want to look at the data.
Being in the planning and collaborative brainstorming phase on that makes this process here 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.
