History:Label Future

Label future

Purpose

This page should be used to collect the various limitations and known bugs of the current label system in MusicBrainz, as well as ideas about how to enhance it and make it evolves toward a better model.

Outstanding bugs

• None

Easy enhancements

List of suggested enhancements, supposedly easy to fix:

• Style tasks:
  • discuss and rationalize the use of SpecialPurposeLabels (like [autorelease])
  • discuss the use of collabs labels (see LabelDiscussion)

• Doc task: documentation is lacking a lot on label EditTypes, and also EditLabelPage
• Doc task: stuff examples in all existing documentation
• Doc task: ACL and transclude all Label documentation
• 2677: Passed label names get truncated
• 2675: View label edits don't show AdvancedRelationship edits related to the label
  • see 884:

• 2674: Add the possibility to search edits by label
• 2669: label pages lack inline voting frame.
• 2661: Add Artist-Label relationship: "artist founded label" "label was founded by"
• 2658: Server > Labels > "LabelX was renamed to LabelY" AR does not need begin & end dates
• 2657: Server > Labels > New AR "ReleaseX was licensed from LabelY"
• 2653: Should get a warning/confirmation message when adding releases to holding label
• 2635: Labels > Barcodes need to accept HYPHENS and SPACES
• 2602: Add a warning when duplicate barcodes are entered

Other enhancements

List of enhancements with some (bigger or unknown) technical impact:

• 2574: Release date should not be mandatory in release event.

Needs research

• There have been some discussion lately about concurrent/additional label identification systems in the wild, apparently dependent of the country. At that time, we lack informations about how these relate to the Label Code system, and there is no solution foreseen. Please provide input on that thread if you have more informations. Please AnswerMe if you do. -- dmppanda 19:28, 29 January 2007 (UTC)

NGS/Pie in the sky

None

Controversial

None

Wontfix

None