instead of vaporwave
FISHWAVE! no. Instrument addition stuff!
The Instrument project on jira is situated https://tickets.metabrainz.org/projects/INST/summary/statistics it shows an overview of stats and the like (I also have some dashboard named "blup" and stats images for my own uses)
https://tickets.metabrainz.org/issues/ is the view for all the issues.
I have some filters i use to delimit tickets and find things. (such as https://tickets.metabrainz.org/browse/INST-776?filter=11020 for "ensemble this!" fix version)
Fix versions are used for an overarching large compound.
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:
- http://oxfordmusiconline.com/ (I have full access via https://wikipedialibrary.wmflabs.org/ )
therer is also countles blogs, sites etcetera that have specialist info, such as https://chandrakantha.com/articles/indian_music/instruments.html 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 https://www-jstor-org.wikipedialibrary.idm.oclc.org/action/doBasicSearch?Query=SEARCH ([off] and https://libgen.is/) 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.)
How to determine if a ticket is not actionable?
it can be not actionable because:
- it has insufficient information and search in prior explained ways have left nothing -> close as incomplete
- duplicate or erroneous type - > as already explained.
- finally if it is fully acceptable instrument or ticket, but na not be doen becase something blocks it, such as implementaion detail (eg https://tickets.metabrainz.org/browse/MBS-9642 or )
Which leave the difficult "when is an instrument not useful for musicbrainz"
in general the logic for deciding this has been outlined in https://wiki.musicbrainz.org/How_to_Add_Instruments#Not_to_be_added_as_instruments (which was the secondary reason we worked it out - have a document that describes the rationale for inclusion/non-inclusion)
So after reading it what is the summary?
Basically it comes down to judgement! all examples have counter arguments, it's never actually that clear, because artists, sigh.
so what I do is I ask for other people's point of view, chiefly reosarevok (Nicolas Tamargo), sometimes Freso (Frederik Olesen) or yvanzo (I don't actually know your name :O) for things that they might know specific about, Bodhráns/Koras etc. I will also reach out to the community with specific opinions and calls for help from anyone who could know/languag ot translate etc. (example sothotalker or shepard for translating german, d4rkie for translating japanese, zas, yvanzo, loujine etc for french, etcetra.) some years ago we had gci'ers coming in from countries that spoke languages we did not have many of in our community, they where a great help and I hope we can attract more people with more languages to help with translations.
however be advised: the community can be fickle, ask them for suggestions on alias translations and they'll just get occupied with with the usage of transliteration in sortnames :|
You can *not* direct peoples attention or incentives anywhere, you can only suggestively nudge, if they do not want to help, but instead want to argue about something else, it is little use to try to redirect them.
Remember that anything can always be edited.
In general all instruments that are "signature moves" to borrow a Pokémon-term of a specific artist are susspect of novelty
How To (actually) Add An Instrument
After all is researched and data is found one makes the instrument. a Disambiguation and a Description. the name should alwasy be lovercase
a bit about aliases
(technically parts of this part goes against established guidelines of how things are *supposed* to be, but I do it this way anyway because it's easier and can be retrofitted should the mb schema be updated (hopefully) in the future )
Generally I will go by the Wikidata list of aliases (ie other lang wiki's) names for an instrument is. I will also add other actual aliases written on that wikidata page, additionally some wikipedia pages will sometimes have more names in their article text (usually the first or second sentence includes them in bold/italiceds) I will include these (provided they don't duplicate any actual language names) as "search hint"
Then I will add any extra names/spellings from Grove or Oxford dictionary (or any other source) as an alias too.
for aliases in a script other than latin i follow the common done thing for artist names -> that is, for the alias name use the full script but for the sortname of thus, use a latin transliteration
- this has some issue in that example, japanese names should probably use hiragana instead
I do this because it is easier to see what an alias is, it's interesting ot see language families, and not to unoften are alternate names transliterations of other scripts as well.
a better way of handling this would be to create a transliteration/script way for aliases
a bit about image (IROM) extraction
how to deal with community friction
How to deal with community friction when correct decisions lead to argument and complaints about "making it impossible to add instruments unless you're a scholar" etc?
- first thing, Don't panic!
- Don't just "give in" and give the people what they (think) they want and compromise data
- learn to walk away and ignore toxious people and arguments
- don't engage with toxic people, ignore them.
- always second guess yourself, but get a 2 persons opinion about if your initial logic was all that faulty to begin with