Meeting ID: 843 7861 5572 Passcode: 556561 One tap mobile +16699006833,,84378615572#,,,,*556561# US (San Jose) +19292056099,,84378615572#,,,,*556561# US (New York)
Dial by your location +1 669 900 6833 US (San Jose) +1 929 205 6099 US (New York) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) +1 346 248 7799 US (Houston) 877 853 5257 US Toll-free 888 475 4499 US Toll-free Meeting ID: 843 7861 5572 Passcode: 556561 Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4
Expert Finder Webinar was a good time for VIVO, since it’s one of the open-source project here and one that is vibrant with its development.
Nice to have dynamically populated different field, because now we have user-defined hard-coded internalization rules. Sigma had similar problem, they overcome it with they’re own i18n files. Problem appears, due to collisions in languages. In a short-term: custom fields (that, probably, might/have already problem). Michel (had this problem): you can get rid of it by, probably, make translation inside VIVO (Spanish ontology). Problem could also be in a SPARQL query. What VIVO version they use, might be resolved in 1.12 (high chances only for French language). Brian: mentioned this issue https://github.com/vivo-project/VIVO/issues/3606 Georgy: for multiple languages you need multiple modifiers or have fields based on the languages. Solution might be - extend modifiers.
Documentation improvement - small issues need further look at.
Try to improve your heap (make it bigger). Other solutions might appear after Dragan will try to reach this person.
Little typo with dot at the end of the float number now fixed.
Lots of information about technical side: how to return json in rest-api, everybody is welcomed to participate in a future testing.