Adding a classical release should be reasonably close to how you enter any other release in MB.
Start with "Editing->Add release", and we'll look at "Release information".
I'm going to enter my copy of Berlioz's Symphonie Fantastique, you can see the cover here.
Title & Release Group
The title is in all caps on the cover, but we normally standardise capitalisation unless there is a strong reason to believe that the musicians
(as opposed to the cover designer) intended to appear that way. So I enter "Symphonie Fantastique" instead of "SYMPHONIE FANTASTIQUE".
I have checked that the release group isn't already in MB, so I enter the same title for the Release Group as for the release title. Also, there are no other titles available on the cover.
Next, we add artists from the cover, in the order of prominence. Berlioz got the biggest font here, so I start with him.
Next in line is the conductor (next biggest font). His name in MB is the local version:
Often for classical releases, you can choose one of 3-4 different languages tracklists & then you set the language field to that particular language.
This tracklist however is only available in one version so I'll use "English" here. See the guidelines for more examples of how to deal with multiple languages.
The other fields in this section is just as for any other release.
This section is very important! Please attempt to add a release event to any classical release which you add or edit. Many classical releases feature the same compositions. Occasionally the same performers will release an entirely new recording of the same compositions which they previously recorded and released. Without a release event, even if advanced relationships are present, it can be difficult or impossible to determine what recording is actually represented by such an "empty" release.
I'm entering recording location from the booklet in the annotation:
Recorded in Stockholm Concert Hall 4-9 November 1991
I can use the dates later, when adding Advanced Relationships, but not the location. We have no field for recording location in MB yet.
If I was in a hurry and didn't have time to enter Advanced Relationships between the performers & the recordings, I'd put in performer information in the annotation too, to help identify the release.
Click "Next" or on the "Tracklist" tab to get to the tracklist editor.
This will be exactly as with any other release in MB. Just remember that tracktitles in classical are often subtitles, and we will need to add the main title to the beginning of each track.
Choose the advanced editor, or we won't be able to change track artists.
Start with selecting the format "CD". Don't enter anything in the "title" field, it's for medium titles (useful for some boxsets). Input the number of tracks (6 in this case) in "Add _ track(s)" and click on the green cross. And then just enter the titles as on liner, inserting colons between lines (subtitlestyle which is only for releasetitles, I'm afraid)
- Don't touch "Guess case" when entering classical, it will mess up your titles! Yes, even the "Classical" setting!
...to be continued.
from old proposal
It is important that performer, arranger, and conductor relationships be added at the recording level (as applicable). Please also review the Advanced Relationship guidelines. Be aware that setting a relationship to say that an artist composed a release is not the same as setting relationships to say that an artist composed each track on a release.
- For any given classical release, it is quite likely that there are several other releases containing the same works in the same order; if these basic ARs are not set, the release is essentially a 'blank' listing. Such unidentified 'blank' listings have a bad tendency to become full of PUIDs, TRMs, CD TOCs, and other data from a range of unrelated releases. Setting these basic identifying ARs allows the users of the database to identify that the releaser you are adding is not, in fact, the one that they want, both avoiding inaccurate data being added, and potentially leading to more releases being added, both of which benefit the data-health of the database.