How to Add Instruments: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary
No edit summary
(48 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[https://musicbrainz.org/instruments Instruments] are entities in MusicBrainz (like artists or releases). However, they can only be added by [https://musicbrainz.org/privileged relationship editors]. If you want to request an instrument, see the [[#How to request an instrument|How to request an instrument]] section below.


Before proposing an instrument for addition to MusicBrainz, make sure it fulfills the conditions to be considered as such. To ensure that the coverage of instruments in MusicBrainz remains reasonable and avoid a huge surge in the amount of instruments, the following guidelines are in place (but keep in mind exceptions can be made, so if you think your instrument still qualifies, do request it and explain why):
so this is first draft. finished product will major differs. halp reosarevok!


== Not to be added as instruments ==
=== Generic items ===
One use generic household items like cans, bowls, pans etc.
: '''Rationale:''' almost any generic thing can be used to make sound, whether as a percussion instrument (bashing one thing with another), a string instrument (a hollow body affixed with strings) or a wind instrument (any kind of tube or container with various holes, blown into)
: '''Exceptions:''' if the musical use of a generic household item becomes popular enough that it starts to be produced (usually with slight modifications) specifically as a musical instrument, or it becomes something enough people see as an actual instrument, it can qualify for inclusion (such as musical saw and musical spoons)


=== Novelty instruments ===
Novelty/experimental instruments developed and used only by one person (or a small, related group of people), such as the [https://liveweb.archive.org/web/20180924133925/https://metro.co.uk/2012/03/27/may-the-chords-be-with-you-man-makes-guitar-out-of-millennium-falcon-366592/ Millennium Falcon guitar] and most (if not all) instruments invented by [[artist:dbcec54d-49c8-4d61-8512-8025bb37bf8e|Blue Man Group]]
: '''Rationale:''' there's little benefit in adding a separate entry for every instrument conceived by any artist but not made available for more general use, since it risks filling the database with instruments that won't ever be selected again and will just confuse users.
: '''Exceptions:''' should the novelty or custom creation start being produced and sold to others (even if in very limited numbers) as a legitimate instrument, it might qualify for addition. Wider adoption can definitely move an instrument from "novelty not to be added" to "perfectly acceptable addition" (such as gravikords and handpans)


=== Modified instruments ===
To prevent complete inflation of Instruments in the database the following rules are (proposed) to be in space:
Modified instruments like "backwards guitar", "two flutes glued together" or "piano smasher"
: '''Rationale:''' any single instrument can be modified in too many ways for MusicBrainz to keep track of all of them, and instrument credits can generally be used.
: '''Exceptions:''' if a specific modification becomes common enough, it might qualify for inclusion.


=== N-string instruments ===
nope:
: '''Rationale:''' as above, these are often just modified instruments, and can be specified with instrument credits.
# one use generic household items like cans, bowls, pans etc
: '''Exceptions:''' if the instrument is actually altered in other ways specifically to adapt to the new number of strings, it might qualify for inclusion, but only if it's either widely produced and sold or the specific modification technique becomes widely adopted.
#* rationale: any generic thing can be used to make sound, that be percussion (bashing one thing with another), strings (a hollow body affixed with strings) or wind (any kind of tube or container with various holes, blown into)
=== Brand names ===
#* negation: if a generic household items used for music is then turned around and *produced* (usually with slight modifications) *for* the use of music, the this should be added (ex: musical anvil, musical saw, spoons)
Something that is simply a brand name of a generic instrument already in MusicBrainz (if the instrument is not in MusicBrainz, the generic version should be requested instead).
# novelty or otherwise "used only by one person type thing" https://www.moviefone.com/2012/03/30/star-wars-guitar-man-makes-millennium-falcon/)Millennium falcon guitar, lots of things on [that damn blue man group release] and stuff linked to https://en.wikipedia.org/wiki/Experimental_musical_instrument
: '''Rationale:''' It would cause a large growth in the number of instruments for little use. Generally, these should be requested as "brand name" type aliases for the appropriate instruments instead.
#* rationale: again conflating what we can add, it should be limited to things that will actually be *used to play music* and by more than one person in the history of the earth.
: '''Exceptions:''' a brand name instrument might be added if [https://en.wikipedia.org/wiki/Generic_trademark the brand has become generic], or if the specific brand name instrument is quite different from any generic ones. This will be rare, and mostly applicable to modern instruments where other similar instruments can't be developed because of patents or other limitations. Even then, it is always preferable to have a generic name (such as "handpan" rather than "hang").
#* negation: should novelty or custom creation be such for the explicitly distributed or sold (even if eventually in very limited numbers)to others to play music in a real setting, it should be added. a thing could very well change status from "novelty" to "genuine instrument" with enough uses and adoption. (examples of this: pvc pipe, gravikord, handpan)
=== Non-instruments ===
# instruments with virtually No information discerning them, especially if there are other and smilier instruments and these also have very similar or same names
Something that isn't an instrument and isn't used as an instrument but is credited next to other instrument credits, such as speakers, sampler(s), computers, microphones.
#* rationale: it's impossible for me to know if these are really different instruments and, even if they are, I will have nothing to be able to disambiguate them with and they will be used wrongly in recordings anyway and confuse people.
: '''Rationale:''' these aren't instruments! They can be used to produce sound, but they are not *played* to make sound.
#* negation: definitely come with enough data to add such instruments and I will!
: '''Exceptions:''' none currently. If a "gear" attribute is ever added, these will probably be allowed there.
# modified instruments like "backwards guitar", "two flutes just superglued together", piano smasher
#* rationale: see rationale 1
#* negation, see negation 1
## x string so and such string instruments
##* rationale: see above, these are just "modified", theoretically you could take a completely ordinary violin and put 15 ukulele strings on it and call it "an violuku", but then you could just put violin strings on it again and it's back to being an ordinary violin.
##* negation: actually altering the instrument to utilise the other amount of strings better, altered bridges, changes to appearance etc, AND the actual production of such in the intended "x string so and such" instrument, (alternately; a wider adoption of the specific modification method as a standard way of "creating" the instrument.)
# something that isn't an instrument and isn't used as an instrument but has a "credit" next to other instrument like credits, ex: speakers, samplers(), computers(INST-589), microphones, a.s.o.
#* rationale: these aren't instruments! they might be used to produce sound, but they are not *played* to make sound.
#* negation: should we ever get a "gear" section (together with the combining of "instrument" and "vocal" trees?) these will probably put there (also see MBS-)
# something that is simply a Brandname with a generic concept already appearing (if not in the db a generic item will be created instead of Brandname version.)
#* rationale: mega inflation! also we have the "brand-name" instrument alias type now.
#* negation: should Brandname instrument undergo [https://en.wikipedia.org/wiki/Generic_trademark Brand name inflation], or, should the specific Brandname instrument be especially unique compared to other comparable versions. this last clause will be rare and (usually) only for 20th century instruments, where the addition of copyright prevents similar instruments from being invented in addition to the brandname one. Even then, it is absolutely preferable to have a generic name (see hang vs. handpan) see (Moog) for counter example (brandname is instrument.)


=== Too little information ===
Instruments about which we have virtually no information, especially if they are very similar to other instruments, and even more if they also have very similar or the same names
: '''Rationale:''' it's often impossible for us to know if these are really different instruments and, even when they are, we will have nothing that allows users to distinguish them well enough, so they will be used incorrectly by confused users.
: '''Exceptions:''' if enough data is eventually found to clearly differentiate the instrument, it can of course be added.


== To be added as instruments ==
yepsipepsi!
=== Rare/historical instruments ===
# rare, historical or unusual instruments not in use today, bonus points if they were once in much use, were invented by inventors of other instruments or eventually led to the evolution of more current and used instruments.
Rare, historical or unusual instruments not in use today (even more so if they were once quite popular, were invented by the same inventor as other more common instruments or eventually evolved into more common current instruments).
#* negations: see the above, esp "very similar and same names"
: '''Exceptions:''' won't be added if not enough information is available to determine what the instrument is like and how it is different from others.
# native people's instruments, bonus points if they are still in use, are hybrids or are very ancient, esp if it could be they are very distant forerunners to current popular instruments
=== Traditional instruments ===
#* negations: if there is little or no information to differentiate from a same or similar native people's instrument, esp if geographically close
Native people's instruments (even more so if they are still in use or if they are thought to be very distant ancestors of current popular instruments).
# instruments with a wikdata page, esp if there are several wikipages and wikimedia commons categories and images.
: '''Exceptions:''' won't be added if there is little or no information about them, especially if that makes them hard to differentiate from similar instruments from a different, but geographically close group of native peoples.
#* negations: too generic instruments that exist as a blanket term in wikipedia, pages that are about ensembles*, conflated terms.
=== Instruments in Wikidata ===
#* ADDENDUM: we now have "ensemble" type so naturally we can add tickets for an ensemble and link the wikidata item for that
Instruments with a Wikidata page, especially if there are also Wikipedia pages in several languages and/or Wikimedia Commons categories with images.
: '''Exceptions:''' too generic instruments that exist as a blanket term in Wikipedia or pages for names that apply to more than one unrelated instrument.
=== Ensemble types ===
Established ensemble groupings consisting of a specific, mostly consistent set of instruments.
: '''Exceptions:''' ensemble groupings that exist, but are quite rare in practice are unlikely to be added to avoid a huge growth in ensemble numbers.




== Q & a ==
== Q & A ==
; This is all too hard and complicated! I just want to know if I can add a ticket for this thing or not!
: If you're still not sure if it's a valid instrument or not, then just come [https://metabrainz.org/contact ask in our forums or IRC] :)


; What do I do if a release credits an instrument, but it doesn't qualify to be added as an instrument in MusicBrainz?
Q: This is all too hard and complicated! I just want to know if I can add a ticket for this thing or not!
: Find the closest nearest equivalent and use your instrument as an instrument credit (in the "credited as" field). For example, for "pots and pans", choose "percussion" with the credit "pots and pans".
a: If you're still not sure if it's a valid instrument or not, then just come online and ask :)
: Alternatively: use "other" with an instrument credit (this is often the best option for complete "non instruments" and strange novelties that don't really match any of the existing options).


== How to request an instrument ==
Q: what to do with a instrument credit that is on a release but the instrument doesn't qualify for a new instrument?
Go to [https://tickets.metabrainz.org/ the issue tracker], choose "Create" and select "INST".
a: find the closest nearest equivalent and use an instrument credit (pots and pans; [percussion] as "pots and pans")
alternatively: use "other" with an instrument credit (this is best for "non instruments" () and absurd type wrecking novelties (eg, the idea of a trumpet with strings over the horn opening part)


In the Issue types section (from most to least likely):
Remember: These are all guidelines and are not set in stone.
* For a '''new instrument''', select "New Feature"
Of course, if you can make a good argument for why something *Should* be an instrument after all, feel free to create a ticket!
* For something that '''needs improving''', like adding an alias or updating a description, select "Improvement"
* For something that's outright '''wrong''' with existing instruments, select "Bug"
* For more '''extensive research''' that'll span several instruments, select "Task", and then:
** Create sub-tickets with the "Sub-new feature" type for each individual instrument to be added
** Create sub-tickets with the "Sub-improvement" type for each individual instrument that needs updating


In the General section:
* Explain what you're asking for in the Summary section.
* Pick the type of instrument you're asking for (or say you want a modification) in the Components section.
* Include as much useful information about the instrument as possible in the Description section: link to a description in Wikipedia, pictures, other sites, etc ([https://tickets.metabrainz.org/browse/INST-484 a good example]). Remember that the more information you provide, the easier it is for the people in charge of adding instruments to get it added.


=== Dos ===
* '''Only add one instrument per ticket''', and ''one ticket per instrument''.
** '''If several things on an existing instrument should be improved''', you can (and should) '''open only one new ticket''' for that, but still make sure to add separate tickets for each separate individual instrument that needs fixing.
* '''Describe the instrument''' in as much detail as possible: what it looks like, where it comes from, historical usage info, its inventor(s) if known, etc.
* '''Link the ticket to other relevant tickets and/or relevant instruments''' already in MusicBrainz.
* '''When creating "modify existing instrument" tickets''', make sure to '''add a link the instrument in MusicBrainz'''! That saves quite a bit of time. You can also add links to any related instruments (such as hybrids, parents, family, derivations, etc.) which haven't been linked to it with relationships yet. If you know of any other related instruments not in MusicBrainz yet, feel free to create tickets for them as well and then link to them from the "modify" ticket!
* '''When creating an ensemble or family request, set it as a "Task" ticket and create subtasks''' for every instrument in the ensemble / family. If any of these instruments are already in the database, they're still likely to need updating, so you should still create subtask tickets for them and set them to have the component "modify existing instrument".


=== Don'ts ===
das how to:(inline template maybe so it can just be fetched from its page and also edited once there, instead of copy pasta and possibilities of it becoming out of sync.)
* '''Don't add requests for instruments that already exist''', nor requests that duplicate an existing ticket (please check!)
* '''Don't add vague and unclear requests'''. If you don't know enough to be more specific, then there's little chance we do, so it will increase the chances that the request is rejected.
** '''"This instrument is played on this track / album" is not useful enough'''. We can't hear it, and even if we could, we're unlikely to get enough info from that to enter the instrument. See if the booklet tells you more about the instrument, or if you can find some sources online that seem to match the description of what you're hearing.
* '''Don't upload images to the ticket''', since we cannot use them directly. If you own the rights to the images, you can upload them to Wikimedia Commons, where we will be able to access them in the future (and so will everyone else, so you're helping more people at once!). If you don't, you shouldn't upload them to our ticket tracker anyway. Keep in mind you can definitely ''link'' to an image hosted elsewhere to help describe an instrument though!
* '''Don't write the ticket in any other language than English''', unless you really can't manage to write it in English. In that case, you can use another language, but keep in mind we will need to try to find a volunteer who speaks it, so it might be much harder for us to deal with it. It is ok to link to non-English sources if that's all you can find, though, although it's much better if you can also at least summarise them in English in the ticket or comments.
* '''Don't add yourself as the "assignee"''' for the ticket
* '''Don't overwrite old ticket descriptions'''. You can always add more information in the comments, or after the existing description.


== Other things you can do to help ==
* '''Take pictures of instruments''' on the ([https://beta.musicbrainz.org/tag/needs%20image/instrument needs image]) list or the ([https://beta.musicbrainz.org/tag/needs%20better%20image/instrument needs better image]) list and upload these to Wikimedia Commons! (make sure to follow [https://commons.wikimedia.org/wiki/Category:Commons_guidelines Commons guidelines]). This should allow us to display images of the instruments in the future.
* If you '''see instruments with "family" in their name''' being used in releases or recordings, try to '''find and select a more specific instrument'''. It's very rare that the "-family" instrument is the best possible choice, even if the specific instrument played is not completely clear. Keep in mind this does not apply to all instruments of the type "Family", but just to those explicitly named as such.
* '''Add links, info or comments''' to '''instrument tickets''' about an instrument you know something about.




{{HowtoBox}}

[[Category:How_To]]
addition

do's:
Only add one instrument per ticket, one ticket per instrument.
(instrument fix-ups like adding alias or linking to other ones, etc, can naturally have just one ticket. but for each instrument that needs fixing, add one ticket please.)

describe as much as possible (link to good practice)

link to other relevant tickets

esp now that we have ensemble / family:
when creating an ensemble request. set this as task and create subtasks for every instrument in the ensemble this is important!
if any of these instruments are already in the database, it will still very likely need updating, so create the subtask ticket and set that to have an "modify existing instrument" component

take pictures of instruments on the (link to the tag for needs image) list or the (needs better image) list and upload these to wikimedia commons!

when creating "modify instrument" tickets link the mb-instrument in question! also link any related instruments (such as hybrids, parents, family, derivations, etc)
if those don't exist in the database create tickets for them and link those to the "modify" ticket!


don'ts:
add requests that already exist
be vague, unclear or say "I don't know, but"
if you don't know then how are you sure it isn't already in the database under a different name/ isn't an instrument/etc?
upload images in the ticket, these cannot be used, they much be on wikimedia commons for to be usable for us (however you can happily link to an image on the web for description and disambiguation-ease, in-fact that's a great idea!)

write the ticket in any other language than english
look, not trying to be mean here but I can't *read* any other languages than english or norwegian, and, unless you are fluent in the latter, we're gonne be better off in english.
If english is very difficult for you, you can try spanish, but it will take some longer time as I will need to have reosarevok translate for me.

Spam Tickets, add more than one ticket adding the same instrument, add yourself as "assignee" (unless you're going to add that instrument to the database.) also please don't completely overwrite old ticket-descriptions, if you have so much information add it instead and keep the old text under a "was previously" section.
if all you have is a "I just need it for this instrument credit/played on this track:"
I'm not magical, I don't know any more about it than you do (less infact!) if there is no info on Wikipedia or online, don't just add a link to the offending MusicBrainz release/recording, try to figure more about it; what does the album's infobooklet say? what does it sound like? unless you can tell me that I can not add the instrument, and the chances of eventually it being closed as "wontfix" or "can't do" increases exponentially


editing:

adding instrument rels to recordings and releases:
please try very hard not to use any "family" type instruments, for example :
guitar example
el gamba example (viol)
violin example

however, if you see any artists, releases or recordings with links to "(anything)-family" you will do a great help if you can move those to a better place!
(should I insert "only in very rare circumstances should there be links to these."?)

Revision as of 13:45, 1 April 2019

Instruments are entities in MusicBrainz (like artists or releases). However, they can only be added by relationship editors. If you want to request an instrument, see the How to request an instrument section below.

Before proposing an instrument for addition to MusicBrainz, make sure it fulfills the conditions to be considered as such. To ensure that the coverage of instruments in MusicBrainz remains reasonable and avoid a huge surge in the amount of instruments, the following guidelines are in place (but keep in mind exceptions can be made, so if you think your instrument still qualifies, do request it and explain why):

Not to be added as instruments

Generic items

One use generic household items like cans, bowls, pans etc.

Rationale: almost any generic thing can be used to make sound, whether as a percussion instrument (bashing one thing with another), a string instrument (a hollow body affixed with strings) or a wind instrument (any kind of tube or container with various holes, blown into)
Exceptions: if the musical use of a generic household item becomes popular enough that it starts to be produced (usually with slight modifications) specifically as a musical instrument, or it becomes something enough people see as an actual instrument, it can qualify for inclusion (such as musical saw and musical spoons)

Novelty instruments

Novelty/experimental instruments developed and used only by one person (or a small, related group of people), such as the Millennium Falcon guitar and most (if not all) instruments invented by Blue Man Group

Rationale: there's little benefit in adding a separate entry for every instrument conceived by any artist but not made available for more general use, since it risks filling the database with instruments that won't ever be selected again and will just confuse users.
Exceptions: should the novelty or custom creation start being produced and sold to others (even if in very limited numbers) as a legitimate instrument, it might qualify for addition. Wider adoption can definitely move an instrument from "novelty not to be added" to "perfectly acceptable addition" (such as gravikords and handpans)

Modified instruments

Modified instruments like "backwards guitar", "two flutes glued together" or "piano smasher"

Rationale: any single instrument can be modified in too many ways for MusicBrainz to keep track of all of them, and instrument credits can generally be used.
Exceptions: if a specific modification becomes common enough, it might qualify for inclusion.

N-string instruments

Rationale: as above, these are often just modified instruments, and can be specified with instrument credits.
Exceptions: if the instrument is actually altered in other ways specifically to adapt to the new number of strings, it might qualify for inclusion, but only if it's either widely produced and sold or the specific modification technique becomes widely adopted.

Brand names

Something that is simply a brand name of a generic instrument already in MusicBrainz (if the instrument is not in MusicBrainz, the generic version should be requested instead).

Rationale: It would cause a large growth in the number of instruments for little use. Generally, these should be requested as "brand name" type aliases for the appropriate instruments instead.
Exceptions: a brand name instrument might be added if the brand has become generic, or if the specific brand name instrument is quite different from any generic ones. This will be rare, and mostly applicable to modern instruments where other similar instruments can't be developed because of patents or other limitations. Even then, it is always preferable to have a generic name (such as "handpan" rather than "hang").

Non-instruments

Something that isn't an instrument and isn't used as an instrument but is credited next to other instrument credits, such as speakers, sampler(s), computers, microphones.

Rationale: these aren't instruments! They can be used to produce sound, but they are not *played* to make sound.
Exceptions: none currently. If a "gear" attribute is ever added, these will probably be allowed there.

Too little information

Instruments about which we have virtually no information, especially if they are very similar to other instruments, and even more if they also have very similar or the same names

Rationale: it's often impossible for us to know if these are really different instruments and, even when they are, we will have nothing that allows users to distinguish them well enough, so they will be used incorrectly by confused users.
Exceptions: if enough data is eventually found to clearly differentiate the instrument, it can of course be added.

To be added as instruments

Rare/historical instruments

Rare, historical or unusual instruments not in use today (even more so if they were once quite popular, were invented by the same inventor as other more common instruments or eventually evolved into more common current instruments).

Exceptions: won't be added if not enough information is available to determine what the instrument is like and how it is different from others.

Traditional instruments

Native people's instruments (even more so if they are still in use or if they are thought to be very distant ancestors of current popular instruments).

Exceptions: won't be added if there is little or no information about them, especially if that makes them hard to differentiate from similar instruments from a different, but geographically close group of native peoples.

Instruments in Wikidata

Instruments with a Wikidata page, especially if there are also Wikipedia pages in several languages and/or Wikimedia Commons categories with images.

Exceptions: too generic instruments that exist as a blanket term in Wikipedia or pages for names that apply to more than one unrelated instrument.

Ensemble types

Established ensemble groupings consisting of a specific, mostly consistent set of instruments.

Exceptions: ensemble groupings that exist, but are quite rare in practice are unlikely to be added to avoid a huge growth in ensemble numbers.


Q & A

This is all too hard and complicated! I just want to know if I can add a ticket for this thing or not!
If you're still not sure if it's a valid instrument or not, then just come ask in our forums or IRC :)
What do I do if a release credits an instrument, but it doesn't qualify to be added as an instrument in MusicBrainz?
Find the closest nearest equivalent and use your instrument as an instrument credit (in the "credited as" field). For example, for "pots and pans", choose "percussion" with the credit "pots and pans".
Alternatively: use "other" with an instrument credit (this is often the best option for complete "non instruments" and strange novelties that don't really match any of the existing options).

How to request an instrument

Go to the issue tracker, choose "Create" and select "INST".

In the Issue types section (from most to least likely):

  • For a new instrument, select "New Feature"
  • For something that needs improving, like adding an alias or updating a description, select "Improvement"
  • For something that's outright wrong with existing instruments, select "Bug"
  • For more extensive research that'll span several instruments, select "Task", and then:
    • Create sub-tickets with the "Sub-new feature" type for each individual instrument to be added
    • Create sub-tickets with the "Sub-improvement" type for each individual instrument that needs updating

In the General section:

  • Explain what you're asking for in the Summary section.
  • Pick the type of instrument you're asking for (or say you want a modification) in the Components section.
  • Include as much useful information about the instrument as possible in the Description section: link to a description in Wikipedia, pictures, other sites, etc (a good example). Remember that the more information you provide, the easier it is for the people in charge of adding instruments to get it added.

Dos

  • Only add one instrument per ticket, and one ticket per instrument.
    • If several things on an existing instrument should be improved, you can (and should) open only one new ticket for that, but still make sure to add separate tickets for each separate individual instrument that needs fixing.
  • Describe the instrument in as much detail as possible: what it looks like, where it comes from, historical usage info, its inventor(s) if known, etc.
  • Link the ticket to other relevant tickets and/or relevant instruments already in MusicBrainz.
  • When creating "modify existing instrument" tickets, make sure to add a link the instrument in MusicBrainz! That saves quite a bit of time. You can also add links to any related instruments (such as hybrids, parents, family, derivations, etc.) which haven't been linked to it with relationships yet. If you know of any other related instruments not in MusicBrainz yet, feel free to create tickets for them as well and then link to them from the "modify" ticket!
  • When creating an ensemble or family request, set it as a "Task" ticket and create subtasks for every instrument in the ensemble / family. If any of these instruments are already in the database, they're still likely to need updating, so you should still create subtask tickets for them and set them to have the component "modify existing instrument".

Don'ts

  • Don't add requests for instruments that already exist, nor requests that duplicate an existing ticket (please check!)
  • Don't add vague and unclear requests. If you don't know enough to be more specific, then there's little chance we do, so it will increase the chances that the request is rejected.
    • "This instrument is played on this track / album" is not useful enough. We can't hear it, and even if we could, we're unlikely to get enough info from that to enter the instrument. See if the booklet tells you more about the instrument, or if you can find some sources online that seem to match the description of what you're hearing.
  • Don't upload images to the ticket, since we cannot use them directly. If you own the rights to the images, you can upload them to Wikimedia Commons, where we will be able to access them in the future (and so will everyone else, so you're helping more people at once!). If you don't, you shouldn't upload them to our ticket tracker anyway. Keep in mind you can definitely link to an image hosted elsewhere to help describe an instrument though!
  • Don't write the ticket in any other language than English, unless you really can't manage to write it in English. In that case, you can use another language, but keep in mind we will need to try to find a volunteer who speaks it, so it might be much harder for us to deal with it. It is ok to link to non-English sources if that's all you can find, though, although it's much better if you can also at least summarise them in English in the ticket or comments.
  • Don't add yourself as the "assignee" for the ticket
  • Don't overwrite old ticket descriptions. You can always add more information in the comments, or after the existing description.

Other things you can do to help

  • Take pictures of instruments on the (needs image) list or the (needs better image) list and upload these to Wikimedia Commons! (make sure to follow Commons guidelines). This should allow us to display images of the instruments in the future.
  • If you see instruments with "family" in their name being used in releases or recordings, try to find and select a more specific instrument. It's very rare that the "-family" instrument is the best possible choice, even if the specific instrument played is not completely clear. Keep in mind this does not apply to all instruments of the type "Family", but just to those explicitly named as such.
  • Add links, info or comments to instrument tickets about an instrument you know something about.


How-To Pages
Introductory Guides
Basic How-Tos
Specific How-Tos