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 .
The tile is in all caps on the cover, we don't enter that.
I have checked that the release group isn't already in MB, so I enter the same title as the recording. 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:
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. copied this from Brian's 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.
can we say use the annotation instead of adding performer ARs to releases?
- 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.