Property talk:P3763
Documentation
identifier for a musical instrument, on the instrument keyword thesaurus from Musical Instruments Museums Online
List of violations of this constraint: Database reports/Constraint violations/P3763#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P3763#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3763#Type Q34379, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3763#Item P1762, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3763#Entity types
List of violations of this constraint: Database reports/Constraint violations/P3763#Scope, SPARQL
Data Availability
edit@Vladimir Alexiev, Pigsonthewing, Spinster, Wittylama: - The entire site seems to be dead now. Any clues as to whether it's still around or if it moved?
- http://www.mimo-db.eu/
- gets redirected to:
- https://vernix.philharmoniedeparis.fr/VERNIX/Infodoc/page-daccueil-infodoc.aspx
There are now currently 753 items with this identifier [1]. -- Fuzheado (talk) 11:04, 12 December 2019 (UTC)
- The new site is https://mimo-international.com/MIMO/how-to-join.aspx so it has grown in importance ("international"). Vladimir Alexiev (talk) 01:45, 13 December 2019 (UTC)
- It does power the search at https://mimo-international.com/MIMO/.
- However the thesaurus display system http://194.254.239.28/skosmos/InstrumentsKeywords/en/index seems to be down. The github repo is https://github.com/philharmoniedeparis/mimo/ . I have posted an issue https://github.com/philharmoniedeparis/mimo/issues/29.
- the data is available, I think at https://github.com/philharmoniedeparis/mimo/blob/master/our_data/keywords_skos.xml or https://github.com/philharmoniedeparis/mimo/blob/master/our_data/03_skos/keywords_skos.xml or https://github.com/philharmoniedeparis/mimo/blob/master/Dossiers%20Marie%20Destandau/our-data/03_skos/keywords_skos.xml
- SPARQL endpoint: http://data.mimo-db.eu/sparql (don't forget to add prefixes eg from http://prefix.cc/skos.sparql) --Vladimir Alexiev (talk) 16:18, 8 January 2020 (UTC)
- 95.4k triples
- 10k Concepts
- 3 ConceptScheme:
- count by scheme:
http://www.mimo-db.eu/InstrumentsKeywords# 2572 http://www.mimo-db.eu/HornbostelAndSachs# 641 http://data.philharmoniedeparis.fr/Thesaurus# 6822
MIMO identifying number does not work.
editI have been trying to use the MIMO identifying numbers, and realized that even the examples on this page don't work. I know that MIMO's database is up and running, with two different methods of doing a search (one more of a database and one more encyclopedic). .
- search #1 If one clicks on the identifying numbers on this page, it opens a mostly blank page on MIMO. Clicking on the MIMO logo brings up a page in which a database search is an option. Not particularly user friendly.
- search #2 If one opens MIMO's home page, a different search box appears, which gives an easier to read result.
If one types in MDMB before the number, it will bring up results on either search (example MDMB 1512 will bring up the Yelatáj chos woley (Q6169915)). I don't know if anyone has explored this. Is there a way to make it work on Wikidata, so that clicking on the MIMO database number will bring up the entry at MIMO? Jacqke (talk) 20:36, 13 December 2020 (UTC)
- I'm not sure if this is helpful but it looks like there's been a website redesign. It's still not particularly accessible or user friendly, and we are still forced to navigate the hierarchical conceptual data model in order to get anywhere. Depending on what we expect this property to return when used, I think the following URL pattern will help:
https://mimo-international.com/MIMO/search.aspx?QUERY=InstrumentTypeLevel4_exact:LEXICON_%ID
Where%ID
is the MIMO number in this property, but exactly eight digits and left-padded with zeroes; e.g. here are the results for contrabass trombone using a modified ID of00006401
. It breaks my heart as a web developer that in 2022 we are still churning out terrible search interfaces like this (why can't it handle the ID without leading zeroes? Why do we have to tell it what "level" we're on when we're looking up by Lexicon ID anyway, which already encodes it?) Anyway, I'm not brave enough to modify this property myself and potentially mess it up for everyone. — Jonathanischoice (talk) 03:34, 4 May 2022 (UTC)