Difference between revisions of "User:Symphonick/CSG Work Titles"

From MusicBrainz Wiki
(the beginning)
 
(language, aliases...)
Line 10: Line 10:
 
|jira=
 
|jira=
 
}}
 
}}
 +
  
 
==Sources==
 
==Sources==
The name should be recorded in MB as it exists in print from a reliable source, such as a recent urtext edition. Adding to or altering a title given by the composer or publisher should be avoided (see aliases).
+
The name should be recorded in MB as it exists in print from a reliable source, such as a recent urtext edition. Adding to or altering a title given by the composer or publisher should be avoided (see language below regarding translations and more).
  
 
If you don't have access to the best edition, just use the best source you can find. The title can be corrected later.
 
If you don't have access to the best edition, just use the best source you can find. The title can be corrected later.
  
{{note}} ''So-called generic or "untitled" works are outside the scope of this proposal.''
+
==Work type==
 +
The type of work (e.g. Aria, Sonata, Trio) is stored in the work type field
 +
For works with a given title or where the title consists of a quote from the beginning of the lyrics or libretto,
 +
 
 +
===Work type as title===
 +
Works that only have a work type as identifier, here called "generic" or "untitled" works, should be listed in the composer's preferred language.
 +
 
 +
(e.g. Sonata/Sonate, Quartet g moll)''
 +
 
 +
{{note}} Tempo as title, common for movements of larger works (e.g. Allegro, Slow) are usually not translated (possibly transliterated) and therefore not c
  
 
==Language==
 
==Language==
If possible, use the language of the first performance (if the work was written with a specific performance in mind).
+
If possible, use the language of the first performance, if the work was written with a specific performance in mind. Not applicable for works published after the composer's death.<br />
 +
 
 +
See the respective CSG-language pages for how to format language-specific details.
 +
 
 +
{{note}} Works with translated lyrics (as opposed to only translated titles) should have
  
 
===Aliases===
 
===Aliases===
{{note}} It is expected that eventually, both the user's preferred language AND the default workname can be shown in the UI.
+
There can be only one "official" alias per language; try to find the standard translation for your specific language.
 +
Be aware that direct translations is not always an option. E.g. a literal translation of "Quartet for Strings" will not work for every language, perhaps the
 +
form "String quartet" is more appropriate.<br />
 +
You can enter more aliases as search help (common misspellings etc.), but they should not have a language set.<br />
 +
 
 +
{{note}} It is expected that eventually, both a title (alias) in the user's preferred language AND the default workname can be shown in the UI.
 +
 
  
 
===Nicknames===
 
===Nicknames===
Line 35: Line 55:
 
{{note}} There's possibility we get a specific field for catalogue numbers, or that advanced properties can be used for this purpose.
 
{{note}} There's possibility we get a specific field for catalogue numbers, or that advanced properties can be used for this purpose.
  
==Part numbers==
 
  
 +
==Multi-part works==
 +
*Main work titles should not be
 +
*Part numbers should eventually have a separate (text) field, and there should be a "position" attribute too
  
 
==Examples==
 
==Examples==

Revision as of 10:40, 9 March 2013


Status: This page describes an active style guideline proposal and is not official.



Proposal number: RFC-CSG Works part II: Titles
Champion: symphonick
Current status: pre-RFC




Sources

The name should be recorded in MB as it exists in print from a reliable source, such as a recent urtext edition. Adding to or altering a title given by the composer or publisher should be avoided (see language below regarding translations and more).

If you don't have access to the best edition, just use the best source you can find. The title can be corrected later.

Work type

The type of work (e.g. Aria, Sonata, Trio) is stored in the work type field For works with a given title or where the title consists of a quote from the beginning of the lyrics or libretto,

Work type as title

Works that only have a work type as identifier, here called "generic" or "untitled" works, should be listed in the composer's preferred language.

(e.g. Sonata/Sonate, Quartet g moll)

Note Note: Tempo as title, common for movements of larger works (e.g. Allegro, Slow) are usually not translated (possibly transliterated) and therefore not c

Language

If possible, use the language of the first performance, if the work was written with a specific performance in mind. Not applicable for works published after the composer's death.

See the respective CSG-language pages for how to format language-specific details.

Note Note: Works with translated lyrics (as opposed to only translated titles) should have

Aliases

There can be only one "official" alias per language; try to find the standard translation for your specific language. Be aware that direct translations is not always an option. E.g. a literal translation of "Quartet for Strings" will not work for every language, perhaps the form "String quartet" is more appropriate.
You can enter more aliases as search help (common misspellings etc.), but they should not have a language set.

Note Note: It is expected that eventually, both a title (alias) in the user's preferred language AND the default workname can be shown in the UI.


Nicknames

Remember that nicknames are local.

Note Note: There's possibility we get a specific field for nicknames.


Catalogue numbers

Since catalogue numbers are an important part of identifying a work, as a workaround one catalogue number can be added to the title. If more than one catalogue is used for a work, try to find the most commonly used catalogue.

Note Note: There's possibility we get a specific field for catalogue numbers, or that advanced properties can be used for this purpose.


Multi-part works

  • Main work titles should not be
  • Part numbers should eventually have a separate (text) field, and there should be a "position" attribute too

Examples