History:Next Generation Schema/History
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.
