From MusicBrainz Wiki
< User:CatCat
Revision as of 13:24, 19 January 2022 by CatCat (talk | contribs)
Jump to navigationJump to search

instead of vaporwave

FISHWAVE! no. Instrument addition stuff!

first the ticket must be selected. usually I square related things of in "mini-version" type ticket, where related tickets are subtickets of that.

  • for new instruments we have new feature/sub-newfeature
  • for tickets that require updating or changing, description or adding aliases we have improvement/sub-newimprovement
  • for actual errors we have bug
  • task is seldom used but occasionally for large unspecific things like "research the difference between these concepts or "translate this wikipage"

when closing the ticket thus status is used

  • for fixed finished tickets, just "fixed" and a comment with a link to the finished instrument if adding a new one/description of what has been done (eg "added all aliases and fixed description")
  • for tickets that are duplicates, just "duplicate" and close them while pointing to the one we have in a comment and linking it "as a duplicate" of that one. recently I've also been upping the priority of tickets which receive duplicates.
  • for tickets which are deemed to not be added (usually these are novelties (link to see how to add $ novelties)) just "won't fix" with a comment explaining why and a link to the appropriate guideline.
  • if the ticket does not have enough information and a search on the internet has yielded no usable information, i close it with "incomplete" these can always be reopened if someone has more information and adds it!
  • for situations where something is totally not actionable by me, not an instrument ticket etc, it would be closed as "invalid" (this doesn't happen very often and usually the ticket should be *moved* to the appropriate project)

ticket should have at fixing closing have a comment with a link to the instrument and the instrument add on musicbrainz should have a link to the associated ticket.

on the actionable tickets thus:

usually the ticket will have a wikipedia link, we follow hat and read the article, possibly also i will read swedish/danish/norwegian wikipedia as well I will then do a duckduckgo search as well as following any other links in the ticket.

I have a set of resources I almost always look up in:

for string instruments especially(of which as of current (2022) still is the largest group of instruments on INST tickets)

next there is of course wikipedia. but also:

therer is also countles blogs, sites etcetera that have specialist info, such as for indian instruments

finally there is irom for images (but someone japanese could possibly get info from pages)

(more on image abstraction later)

Then I have some offline sources I loom in:

  • The excellent The New Grove Encyclopedia of Musical Instruments I-III 1984 edition
  • The History of Musical Instruments by Curt Sachs (only borrowed from library)
  • Percussion Instruments and their History by James Blades (for percussion instruments, only borrowed from library, it is an excellent book I wish I owned)
  • Taonga pūoro: Singing Treasures (The musical instruments of the Māori) by Brian Flintoff (for the Māori instruments I extensively borrowed from the library this book several times (its music CD has already been added to mb ;)) another book I wish I owned)

else I borrow from the library any topic books if they have them, I also go through ([off] and searching for any article or book of the topic for what I'm adding

(example: while trying to piece together how ancient Indian string instruments connect together I searched extensively for these "Veena" instruments in all these sources.)