How to Add Instruments: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
mNo edit summary
No edit summary
Line 58: Line 58:




= do's: =
=== do's: ===
Only add one instrument per ticket, one ticket per instrument.
*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.)
(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
describe as much as possible (link to good practice)

link to other relevant tickets


esp now that we have ensemble / family:
esp now that we have ensemble / family:
Line 70: Line 68:
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
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!
*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)
*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!
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
= don'ts: =
*be vague, unclear or say "I don't know, but"
add requests that already exist
(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?)
be vague, unclear or say "I don't know, but"
*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!)
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?
*write the ticket in any other language than english
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!)
(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.)
write the ticket in any other language than english
*Spam Tickets
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.
*add more than one ticket adding the same instrument
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.
*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.

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:"
if all you have is a "I just need it for this instrument credit/played on this track:"

Revision as of 11:18, 1 September 2018

so this is a draft. finished page will majorly differ. halp reosarevok!


To prevent complete inflation of Instruments in the database the following rules are (proposed) to be in space:

nope

  1. one use generic household items like cans, bowls, pans etc
    • 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)
    • 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)
  2. 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: 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.
    • 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)
  3. instruments with virtually No information discerning them, especially if there are other and smilier instruments and these also have very similar or same names
    • 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.
    • negation: definitely come with enough data to add such instruments and I will!
  4. modified instruments like "backwards guitar", "two flutes just superglued together", piano smasher
    • rationale: see rationale 1
    • negation, see negation 1
    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.)
  5. 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-)
  6. 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 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.)


yepsipepsi!

  1. 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.
    • negations: see the above, esp "very similar and same names"
  2. 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
    • negations: if there is little or no information to differentiate from a same or similar native people's instrument, esp if geographically close
  3. instruments with a wikdata page, esp if there are several wikipages and wikimedia commons categories and images.
    • negations: too generic instruments that exist as a blanket term in wikipedia, pages that are about ensembles*, conflated terms.
    • ADDENDUM: we now have "ensemble" type so naturally we can add tickets for an ensemble and link the wikidata item for that


Q & a

Q: This is all too hard and complicated! I just want to know if I can add a ticket for this thing or not! a: If you're still not sure if it's a valid instrument or not, then just come online and ask :)

Q: what to do with a instrument credit that is on a release but the instrument doesn't qualify for a new instrument? 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)

Remember: These are all guidelines and are not set in stone. Of course, if you can make a good argument for why something *Should* be an instrument after all, feel free to create a ticket!


How to

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.)


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."?)