Timeline: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary |
(Add NGS to the timeline) |
||
| Line 7: | Line 7: | ||
===Next Generation Schema=== |
===Next Generation Schema=== |
||
The [[Next Generation Schema]] of the database was released in mid-May 2011, and tries to solve a lot of problems with the "classic" schema, bringing the data closer to reality. As this was not an easy process, it has been structured under some collaborative modeling pages: [[Object Model|object model]] for finding out what kinds of objects we are dealing with and we would need to store and [[Aspect Model|aspect model]] to split them into several aspects which all have a different view on the data. |
|||
The team are now stabilizing, adding missing features and functionality not yet migrated from the "Classic" MusicBrainz Server. |
|||
After finishing that process we can start to build a new database model which covers release grouping, [[Release Attribute|release attribute]] and [[Release Event|release event]] changes, track grouping, multiple artist support, and much more. This model should regard that we have to disentangle interfaces from schema so we also need to build a view model separately. |
|||
== MusicBrainz summits == |
== MusicBrainz summits == |
||
| Line 27: | Line 27: | ||
== Completed work == |
== Completed work == |
||
;2011-05-16 [[Server_Release_Notes/20110516|Server release]] ([http://blog.musicbrainz.org/?p=875 blog post]) |
|||
* Other: Complete rewrite of MusicBrainz Server on a new data model, with new frameworks |
|||
* Other: Full use of CSS and a new, cleaner design. |
|||
* New feature: new schema that allows us to grow into a comprehensive music encyclopedia. |
|||
* New feature: RDFa support embedded into the HTML pages |
|||
* New feature: A new version of our web service API (see release notes) |
|||
* New feature: [[Artist Credit]]s |
|||
* Improved: Huge improvements to the release model; such as supporting multiple discs/mediums (see release notes) |
|||
* New feature: The concept of a musical [[Work]] is now supported (see release notes) |
|||
* New feature: The concept of a musical [[Recording]] is now supported (see release notes) |
|||
* New feature: Releases support packaging and can be be attributed to multiple labels. |
|||
This list only scratches the surface; see the [[Server_Release_Notes/20110516|release notes]] for the bigger picture |
|||
;2009-05-24 [[Server Release Notes/20090524|Server release]] ([http://blog.musicbrainz.org/?p=391 blog post]) |
;2009-05-24 [[Server Release Notes/20090524|Server release]] ([http://blog.musicbrainz.org/?p=391 blog post]) |
||
Revision as of 13:54, 7 June 2011
Development > Timeline
If you have a suggestion or a idea you would like to see implemented, please use UserVoice to let us know.
Currently under development
Next Generation Schema
The Next Generation Schema of the database was released in mid-May 2011, and tries to solve a lot of problems with the "classic" schema, bringing the data closer to reality. As this was not an easy process, it has been structured under some collaborative modeling pages: object model for finding out what kinds of objects we are dealing with and we would need to store and aspect model to split them into several aspects which all have a different view on the data.
The team are now stabilizing, adding missing features and functionality not yet migrated from the "Classic" MusicBrainz Server.
MusicBrainz summits
- 2009-11-28 Summit 10
- Held in Nürnberg, Germany.
- 2008-05-10 Summit 9
- Held in London, UK.
- 2007-06-07 Summit 8
- Held in London, UK.
- 2005-12-03 Summit 7
- Held in Hamburg, Germany.
- 2004-11-30 Summit 6
- Held in London, UK.
- 2003-11-20 Summit 5
- Held in Oxford, UK.
Completed work
- 2011-05-16 Server release (blog post)
- Other: Complete rewrite of MusicBrainz Server on a new data model, with new frameworks
- Other: Full use of CSS and a new, cleaner design.
- New feature: new schema that allows us to grow into a comprehensive music encyclopedia.
- New feature: RDFa support embedded into the HTML pages
- New feature: A new version of our web service API (see release notes)
- New feature: Artist Credits
- Improved: Huge improvements to the release model; such as supporting multiple discs/mediums (see release notes)
- New feature: The concept of a musical Work is now supported (see release notes)
- New feature: The concept of a musical Recording is now supported (see release notes)
- New feature: Releases support packaging and can be be attributed to multiple labels.
This list only scratches the surface; see the release notes for the bigger picture
- 2009-05-24 Server release (blog post)
- New feature: Release Groups, these are used to group several different releases into a single logical entity.
- New feature: ISRC, a standardized identification system for audio and music video recordings.
- Other: WikiDocs now use new MediaWiki wiki.
- 2009-03-15 Wiki migration
- 2008-11-23 Server release (blog post)
- New feature: Rating System, this allows users to rate MusicBrainz entities (artists, labels, releases and tracks).
- New feature: CD Stubs, these are raw releases with a DiscID which are not part of MusicBrainz proper data.
- New feature: Collections added, these allow users to keep track of their own music collections in MusicBrainz.
- Removed feature: TRMs.
- 2007-10-14 Server release (blog post)
- New feature: Folksonomy tag support added.
- New feature: Subscribe to Editor, this allows a user to subscribe to other users edits the same way as one can be subscribed to an artist right now.
- 2007-04-01 Server release (blog post)
- New feature: Labels added to the schema.
- New feature: Data Quality.
- New feature: Track annotations.
- 2006-12-17 Server release
- New feature: URLs can now be edited, instead of having to be removed and readded.
- New feature: FreeDB search added.
- 2006-07-12 Server release (blog post)
- New feature: Edit notes now have timestamps.
- 2006-03-05 Server release (blog post)
- New feature: Lucene search.
- New feature: XML Web Service.
- New feature: Auto-Editors can "approve" edits.
- 2005-04-10 Server release (blog post)
- New feature: Advanced Relationships (blog post), these allow MusicBrainz users to define new and flexible relationships between almost any data element. For example, "artist a and artist b are married", "artist c performed on track d".
- New feature: Artist Comment, these help in distinguishing between identically named artists.
- Other: Voting now required a verified email address.
- 2005-01-08
- New feature: Added the ability for Auto-Editors to temporarily drop their privileges, thus allowing them to enter an edit that has to go through the voting process.
- New feature: Artists now display the number of subscribed users.
- New preference: "Allow other users to see my subscribed artists".
- New preference: "When I vote on a edit, mail me all future notes for that edit"
- 2004-12
- New feature: Persistent MusicBrainz Identifiers, these allow a merged artist's ID to still work and point to the new artist's ID.
- New feature: Internationalization, rudimentary support for specifying the language of each release.
- Other: memcached and pgmemcache support being tweaked.
- 2004-11 Server release (blog post)
- New feature: Artist annotations, Release annotations, there allow editors to add free-text annotations to artists and releases.
- New edit type: "Add Disc ID", these are auto-approved edits like "Add PUID"; but having the data added via a moderation provides an audit trail of changes.
- Other: Style Guidelines and Documentation moved to the wiki.
- 2004-05
- New server feature: Replication Mechanics for mirrors, the first mirror (http://nl.musicbrainz.org) went live.
- 2004-04
- New feature: Amazon matching, most Amazon mismatches are now fixed.
- Other: MusicBrainz is now a Tax Exempt Organization.
- 2003 and older
- Capitalization standard proposal accepted and guideline created.
- Email address confirmation went live in June, 2003.
