Date

Call-in Information

Time: 10:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

  • https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09

    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

Slack

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic 
  2. Georgy Litvinov (star)
  3. Brian Lowe 
  4. Benjamin Kampe 
  5. William Welling 
  6. Michel Héon 
  7. Mark Vanin  
  8. Huda Khan
  9. Veljko Maksimovic  
  10. Benjamin Gross          

Agenda

  1. Questions/Issues/Pull requests/Announcements
    1. Upgrade from 1.12. to 1.13 - https://groups.google.com/g/vivo-tech/c/gmyQIMWbm_Y
    2. ORCID - https://groups.google.com/g/vivo-tech/c/wDblxLmeTjs
    3. Reset wiki password
    4. https://github.com/vivo-project/VIVO/issues/3767
  2. The i18n redesign sprint
    1. LanguageTag private-use subtag
      1. fr_FR_x_uqam
      2. https://github.com/vivo-project/Vitro/pull/330
    2. Loading of translations from triple store
      1. https://github.com/vivo-project/Vitro/pull/329
    3. Organization of ttl files
      1. Re-organization of files 

Notes

Dragan: Regarding some questions on slack and emails I tried to summarize it:

  • Here is the issue of removing thumbnails from persons’ profiles. Issues are there for both versions. 

Brian: we need more details about the issue.

Dragan: I can reply to get more information.

Brian: It is a little bit strange issue.

  • ORCID-API Disable

Brian: It doesn’t do the obvious thing, if you don’t configure ORCID API we shouldn’t see ORCID part, it is broken in that case. We should create an issue for that.

Dragan: Should we open an issue?

Brian: Absolutely.

  • Reset wiki password

Dragan: Send to me username and prefered name you would like to use so we could resolve issues.

Dragan: Michel could you describe the issue.

Michel: There are two issues. I try to use VIVO as an external triple store. I see data that I put in VIVO, but the Capability map doesn’t work. On a local triple store it works, but on a remote triplestore  it doesn’t work.

Second problem: Triple store on 4th line of the code :hasConfigurationTripleStore if I try to attach to Sparql Triples store it doesn’t work. I can show it on a running instance if you want it.

Dragan: You can.

Michel: So this is the instance of VIVO, where sample data is loaded. If I go to Capability map I don’t have autocompletion and it doesn’t work.

Georgy: Are there any logs in VIVO or in Browser?

Michel: I will try to do it again. I can put the logs in the issue.

Dragan: Is that log from now?

Michel: Yes. I expect to have this problem with Fuseki. You can access the instance
http://vivo-sample-neptune.ca-central-1.elasticbeanstalk.com/
Normally there should be autocompletion, but now it is empty

Brian: RegEx error in log file is most likely not the cause of the issue, but should be resolved.

Sprint:
Dragan: Georgy created one PR. Dragan I also created PR. We should also discuss directory structure.

Dragan: There are fixes needed in more than one place. We are struggling with language parsing in more than one place.

If we define something in the runtime.property file when it is loaded in some locale object. toString method on locale creates wrong tag.

X - is an private use extension
U - unicode extension
If you using X letter then you don’t plan to use it on other systems
Idea here is that it is part of the ontology. 

Michel: If we choose to manage that type of tagging then I suggest keeping that type of tagging for other cases.
Dragan: It looks complicated to me to use more than one private use subtag.

Michel: It is not a place to put themes in runtime.properties. It doesn’t make sense to put themes in runtime.properties.

Dragan: I also tried to use a language filter in the graph. That filter is responsible for that. It seems to be working, I have to check that once again. I am not sure it will.

In sparql it might create some issues. If we have partially completed a translation for theme, but fully translated key in VIVO, then partially theme translation is going to be used.

Dragan: We should see how to organize property files and ttl files. We should keep them in the same place. We can convert them first, but make them work for the first time.

Some idea of the home directory is for updating, to have customizations there. I18n is in tomcat, when you upgrade to a new version of VIVO it will be lost. Have you discussed that in the previous i18n meeting? It looks to me that it should be moved to the home directory.

Brian: At this point having binary distribution war is only to test, but not for production. All of the labels and customizations are done with third tier architecture. That overall problem hasn’t been resolved. Everybody use overriding in the production environment.

I don’t know how many people use it, some people use the actual fork of the branches and we don’t really know how people use that. Third tier project needs to be updated anyway. It is not really easy to use that.

Dragan: My idea is to keep that as similar as possible to the hierarchy we have at the moment.
For each language we should add its files. Where should we put new translations?

Brian: Display model is perfectly fine for this. There is going to be display ontology and in the past it was going to be editable or it could be a separate model. 

It fits with the rest of the stuff in the display model, but maybe we would like to have a different model to store that. But we don’t have a directory structure for that. Is it worth it to create a new directory for this. Either one would be fine.

Dragan: Do you remember how you decided about the suffixes. Should there _de_DE at the end of the file name?

Michel: In a graph it doesn’t make a difference. I like this classification, if you want to add a new language you have to copy some language and use it. 

Dragan: If we decide to have languages in separate directories we can remove suffixes. When you build a complete VIVO app there are all files together and they come with VIVO and Vitro prefixes. We should take into account that people can use Vitro as a separate application.

I agree, we can merge that together for VIVO, but for Vitro and other applications on top of VIVO we shouldn’t do that.

Michel: does VIVO use screens from Vitro or all the screens from VIVO only. If we need to have full VIVO translations we need to translate Vitro too. If you are running VIVO do you need both?

Dragan: Yes. We need to decouple VIVO and Vitro translations. It’s for us to discuss that tomorrow.

Dragan: Let's meet to continue the discussion tomorrow.

Draft notes in Google Docs

Task List

Previous Tasks 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.