Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up makam instruments #175

Closed
sertansenturk opened this issue Jan 30, 2015 · 15 comments
Closed

Clean up makam instruments #175

sertansenturk opened this issue Jan 30, 2015 · 15 comments
Milestone

Comments

@sertansenturk
Copy link
Contributor

I stumbled upon some examples where compmusic.dunya.makam.get_recording(mbid) returns empty performer information while the data is available in Musicbrainz. An example:

from compmusic import dunya as dn
import compmusic

dn.set_token...
compmusic.mb.auth...
compmusic.mb.set_hostname...

mbid = "2ec806b4-7df2-4fd4-9752-140a0bcc9730"
compmusic.mb.get_recording_by_id(mbid, includes = ["artists"])['recording']
dn.makam.get_recording(mbid)
@alastair
Copy link
Member

alastair commented Feb 2, 2015

Almost certainly because this is a vocal relationship, and for some reason I don't have the "vocal" instrument in the database. I'll add it, then we'll have to reimport everything

@alastair
Copy link
Member

alastair commented Feb 3, 2015

Some more questions about makam instruments:
In the makam lists file: https://docs.google.com/a/upf.edu/spreadsheet/ccc?key=0Aswz5KkuLnI3dDRYZHVUNzl2dllHVlBSVDVNek5YcWc#gid=3
we list all of the instrument types that we have in relationships in musicbrainz, but some of these are not specific instruments. See for example

  • guitar
  • guitars
  • double bass / contrabass / acoustic upright bass
  • other drums
  • other instruments
  • other percussion
  • strings
  • woodwind

(don't worry about ney/nei, we have to fix that separately)

So, these "instruments" are not really real instruments, so we shouldn't have an instrument entry for them. However, there are relationships that use these instruments. What should we do? Our options are to

  1. delete the instrument reference (and so the relationship will be lost)
  2. add an alias so that the reference is added somewhere
  3. change/fix the relationships in musicbrainz
  4. store these relationships without actually linking them to a "real" instrument (a nicer idea but requires lots of work in dunya)

@alastair alastair changed the title Performer info obtained from compmusic.dunya.makam.get_recording is not reliable Clean up makam instruments Feb 3, 2015
@georgid
Copy link

georgid commented Feb 3, 2015

@sertansenturk: by compmusic.mb do you mean musicbrainzngs?
If so then I tested the given MBID:
if I say with musicbrainzngs
rec = mb.get_recording_by_id(mbid, includes = ["artist-rels"])['recording']
then the I have relationship of type vocal in:
rec["artist-relation-list"]

in general I am not sure what is the difference between mb.get_recording_by_id() and dunya.makam.get_recording(). Would appreciate if you explain me.

@sertansenturk
Copy link
Contributor Author

@alastair I have corrected most of the instruments. However, I was unsure of some examples. Please check my doubts in the google docs...

@georgid Alastair fixed the vocal issue explained above. That's why you should see it correctly. We are trying to fix some related things now. Related to your question Alastair can explain it much better but I don't think it is relevant to the issue here and it should be discussed elsewhere.

@alastair
Copy link
Member

alastair commented Feb 4, 2015

OK, I'm happy with the list now.
One final question - should we rename "double bass / contrabass / acoustic upright bass" to something smaller?

In hindustani and carnatic we have an english name and a local name for raaga and taala names. Do you want the same for turkish instruments?

We should leave the three "other" instruments. I'll set them up as these "hidden" instruments that we discussed. That is, a release will show "Person played other percussion" but there will be no instrument page for "other percussion" and you can't search for people who played "other percussion"

@alastair
Copy link
Member

alastair commented Feb 4, 2015

strings will be hidden as well.

Finally, do we want to merge the three violas together? They should probably all be listed under "Viola", but we could say "x played Viola da gamba" and then link to a single page for viola.

@alastair
Copy link
Member

alastair commented Feb 4, 2015

  • instruments are translated
  • Double bass now has an alias of the long one - so it'll import properly but look good
  • "other" instruments will be hidden
  • for now we'll not merge violas, but should speak with a historic classical music expert who can tell us if we can

@alastair
Copy link
Member

alastair commented Feb 4, 2015

If people select "percussion" as an instrument, we should consider showing all sub-instruments that are also percussion when we show lists of artists. We'll wait until we implement this page to see if it looks nice.

@sertansenturk
Copy link
Contributor Author

@xserra (as a musician) stated the viola, viola d'amor and viola de gamba are very different from each other, so no need to merge them.

@sertansenturk
Copy link
Contributor Author

http://dunya.compmusic.upf.edu/dashboard/release/3850 shows some unknown instruments, some of which should be in the list (violin), some is already in the list (oud) and some should be merged in Dunya (Spanish acoustic guitar). Can there be something missing when you are accumulating the instrument list?

@alastair
Copy link
Member

This might be a problem with the verification script - I think I might not
be comparing both upper and lower case names (e.g. Violin vs violin).

Spanish acoustic guitar definitely isn't in the list. Our options are

  1. add it to the instrument list
  2. change it to guitar in musicbrainz
  3. leave it in musicbrainz, but change it to guitar during import into
    dunya

On 10 February 2015 at 23:28, Sertan Senturk notifications@github.com
wrote:

http://dunya.compmusic.upf.edu/dashboard/release/3850 shows some unknown
instruments, some of which should be in the list (violin), some is already
in the list (oud) and some should be merged in Dunya (Spanish acoustic
guitar). Can there be something missing when you are accumulating the
instrument list?


Reply to this email directly or view it on GitHub
#175 (comment).

@alastair
Copy link
Member

Actually, I didn't realise that we /are/ missing violin. I'll add it

On 11 February 2015 at 11:43, Alastair Porter alastair.porter@upf.edu
wrote:

This might be a problem with the verification script - I think I might not
be comparing both upper and lower case names (e.g. Violin vs violin).

Spanish acoustic guitar definitely isn't in the list. Our options are

  1. add it to the instrument list
  2. change it to guitar in musicbrainz
  3. leave it in musicbrainz, but change it to guitar during import into
    dunya

On 10 February 2015 at 23:28, Sertan Senturk notifications@github.com
wrote:

http://dunya.compmusic.upf.edu/dashboard/release/3850 shows some unknown
instruments, some of which should be in the list (violin), some is already
in the list (oud) and some should be merged in Dunya (Spanish acoustic
guitar). Can there be something missing when you are accumulating the
instrument list?


Reply to this email directly or view it on GitHub
#175 (comment).

@sertansenturk
Copy link
Contributor Author

The funny part is it says oud and kanun are missing. I guess when the "solo" attribute is around something is going wrong.

I listened to the track with the Spanish acoustic guitar, it is correct. I think it's better to be specific in MusicBrainz. Let's change it to guitar during import.

@alastair
Copy link
Member

oud an kanun are because they are named Oud and Kanun in dunya. I need to
make it ignore case.

On 11 February 2015 at 12:07, Sertan Senturk notifications@github.com
wrote:

The funny part is it says oud and kanun are missing. I guess when the
"solo" attribute is around something is going wrong.

I listened to the track with the Spanish acoustic guitar, it is correct. I
think it's better to be specific in MusicBrainz. Let's change it to guitar
during import.


Reply to this email directly or view it on GitHub
#175 (comment).

@alastair alastair modified the milestone: Makam Feb 11, 2015
@alastair
Copy link
Member

Instruments are done. I need to add a few more aliases - instead of adding these to the database I am directly creating the alias in the import code. Will close when the aliases are created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants