User:BrianSchweitzer/sandbox1

From MusicBrainz Wiki
Jump to navigationJump to search

This proposal, if passed, is only effective for the NGS release; it entails sufficient server updating that implementing it under the current mason code wouldn't make sense.

Currently, URL ARs have a URL field and a Description textarea. The Description textarea is useless; it displays nearly nowhere and serves no purpose. Any time it is populated at the moment, whatever text is in there normally shouldn't be.

This proposal changes that field, and URL ARs in general, to allow for more URL AR flexibility, and to remove a the Description field whenever it is useless.

1) Make the Description field a text input field, not a textarea.

2) Make the Description field an optional attribute for any URL AR's definition. The default for any URL AR, unless it is defined to use the field, would be that the field is not shown in the AR entry form and any text that somehow still got into the field would be invalid (and thrown away by the server upon edit submission). For any URL AR which *does* show the description field, a value for "Description text" must be provided in the definition, and when editors create any such AR, that field is manditory.

3) Make the text "Description" itself definable by the AR.

The above would allow the field to only be shown when there's a reason to show it, and for the field's label to make sense for whatever ARs would use it.

4) In the definition for a URL-foo AR type, the following additional options (or the equivalent of these) would be presented to the Relationship Editor:

a) Show description field. default: false
b) Label for description field. default: (blank)
c) Each AR displayed on a new line. default: false

5) Any URL AR type which is defined to use the description field would now, when ARs of that type are displayed, display the description text as the link text, rather than the URL. So 

<a href="http://foo.com">Description text</a>

and not the current 

<a href="http://foo.com">http://foo.com</a>

.

6) Existing URL ARs would be updated as follows:

All defaults (no description field):

  • Track-URL: can be downloaded for free at
  • Track-URL: can be purchased for download at
  • Track-URL: is available for download under the Creative Commons {license} license at
  • Release-URL: can be downloaded for free at
  • Release-URL: can be purchased for download at
  • Release-URL: can be purchased for mail-order at
  • Release-URL: has a Discogs page at
  • Release-URL: has Amazon ASIN
  • Release-URL: has a MusicMoz page at
  • Release-URL: has a Wikipedia page at
  • Release-URL: has cover art at
  • Release-URL: has lyrics available at
  • Artist-URL: has a BBC Music page at
  • Artist-URL: has a biography page at
  • Artist-URL: has a blog at
  • Artist-URL: has a discography page at
  • Artist-URL: has a Discogs page at
  • Artist-URL: has a fan page at
  • Artist-URL: has a MusicMoz page at
  • Artist-URL: has a MySpace page at
  • Artist-URL: has an IBDb page at
  • Artist-URL: has an IMDb page at
  • Artist-URL: has an IOBDb page at
  • Artist-URL: has an official homepage at
  • Artist-URL: has an official YouTube channel at
  • Artist-URL: has an online community page at
  • Artist-URL: has a picture at
  • Artist-URL: has a PureVolume page at
  • Artist-URL: has a Wikipedia page at
  • Artist-URL: music can be downloaded for free at
  • Artist-URL: music can be purchased for download at
  • Artist-URL: music can be purchased for mail-order at
  • Label-URL: has a catalog of records at
  • Label-URL: has a Discogs page at
  • Label-URL: has a fan page at
  • Label-URL: has a logo at
  • Label-URL: has a MySpace page at
  • Label-URL: has an official homepage at
  • Label-URL: has an official YouTube channel at
  • Label-URL: has a Wikipedia page at
  • Label-URL: has its history presented at

Show field, text: "Name of musical", displayed on new line: false:

  • Release-URL: has an IBDb page at
  • Track-URL: has an IBDb page at
  • Track-URL: has an IOBDb page at
  • Release-URL: has an IOBDb page at

Show field, text: "Name of movie, TV show, game, etc", displayed on new line: false:

  • Release-URL: has an IMDb page at

Show field, text: "Company or person's name", displayed on new line: false:

  • Track-URL: contains miscellaneous support from
  • Track-URL: has {additional} photography by
  • Track-URL: has art direction by
  • Track-URL: has artist & repertoire support by
  • Track-URL: has creative direction by
  • Track-URL: has design/illustration by
  • Track-URL: has graphic design by
  • Track-URL: has legal representation by
  • Track-URL: has lyrics available at
  • Track-URL: has merchandising by
  • Track-URL: has travel arrangement by
  • Track-URL: was booked by
  • Track-URL: was published by

Show field, text: "Name of studio", displayed on new line: false:

  • Track-URL: was recorded by studio at

Show field, text: "Name of review site or publication", displayed on new line: false:

  • Release-URL: has a review page at

7) Change the Recorded by Studio At Relationship type's link phrase from "was recorded by studio at" to "was recorded at", to make the wording work.


8) For the proposed Has News Coverage AR, change it such that the AR would only be implemented with NGS. It's options would be:

Show field, text: "Date and headline", displayed on new line: true

Also modify the proposal so that the date and headline attribute would be defined in this way:

Date and Headline

This is a manditory attribute.

This attribute indicates the headline for the linked article, as well as the date that article was released. This must be formatted in the following manner:

  • YYYY-MM-DD: Headline

9) For the proposed Has News Coverage AR, the RFC would be further modified such that it requests (though this would not be a blocker to initial implementation, if it has to wait) that the ARs of that type not only be displayed 1 per line, but that they be pre-sorted by the server such that the description fields are in alphanumeric order. This would allow a display such as: 

News coverage for Foo: 2000-10-03: A new band emerges!
                       2005-02-11: Foo's latest release is a hit
                       2007-09-05: Foo's 'All the Best Songs' goes platinum
                       2010-02-24: It's official, Foo is breaking up!

10) For any URL which happens to be involved in more than one URL AR, the first entered value for the description field would be the one used. This would only then be editable by directly editing the URL entity itself. (Eventually, it'd be nice if any relevant URL AR could auto-lookup an entered URL to see if it exists, to then populate the description field, then marking it as uneditable.)

11) To ensure that any URL ARs which would then be using the description field would have a description, prior to NGS we'd likely need a report of such URL ARs, so we could go and add a description to them (else there'd be no link text for them once this is implemented).

Retrieved from "https://wiki.musicbrainz.org/index.php?title=User:BrianSchweitzer/sandbox1&oldid=35562"