release Annotation: Difference between revisions
((Imported from MoinMoin)) |
(No difference)
|
Revision as of 22:43, 5 June 2006
A Release Annotation is user contributed text attached to a specific Release.
This allows information about that particular release, its additional information and the tracks on it to be explained in further detail.
The content of a Release Annotation can be edited by any MusicBrainz user. Like the rest of the database, if something is incorrect or incomplete you can fix it. All changes are recorded and if someone deletes or defaces the Annotation, you can easily restore a previous copy.
Suggested Content
The Release Annotation can hold information about a release that does not fit into the fields of the database, or which is not allowed to be in the ReleaseTitle or Tracktitles according to the OfficialStyleGuidelines. For example:
- There are tracks that are 'bonus tracks'.
- Whether a release was a vinyl or cassette release (and furthermore, where the sides went, A, B, etc.)
- Additional information about a release, links and alternative names for the release or tracks, etc.
- Note: The remainder of this page was written before the release of AdvancedRelationships: nowadays, many of these things can be represented more usefully using advanced relationships. This page needs to be cleaned up. In the meantime, please see AdvancedRelationshipTypes.
One release is a translation of another.
- Uh? This should be done with an AdvancedRelationship. Is there an AdvancedRelationshipType that can be used for this? --DonRedman
- Not that I've noticed. -- MartinRudat 11:50, 30 April 2006 (UTC)
A CD release was remastered from analog, but has extra tracks.
- This too should be done with AdvancedRelationships.
- Uh? This should be done with an AdvancedRelationship. Is there an AdvancedRelationshipType that can be used for this? --DonRedman
The reason for not allowing such information in the past was that if such extraneous info had been included with the track and release names, it would have severely cluttered the database.
Now, with the addition of annotations, the ReleaseAnnotation can be used to enter such information.
For a ProposedStyleGuideline on how to enter extended release info in a standardized way in ReleaseAnnotations please see ReleaseAnnotationStyle.
linkbacks:
Discussion/Ideas
suggested text-string for translated release versions
- please do not change the capitalisation of this release, it is exactly the way it should be as this is a japanese release, for the transliterated [translated] version go here [link]
and on the translated release:
- this is a transliterated [translated] version of [link to original]
adding the explanation not to merge the two should also be worked in, grammar-vise ~mo
Authors: Mo, CarstenKlapp