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 
  3. Brian Lowe (star)
  4. Benjamin Kampe 
  5. William Welling
  6. Michel Héon 
  7. Mark Vanin              

Agenda

  1. Questions/Issues/Pull requests/Announcements
    1. Research publications at VIVO home page 
      1. https://groups.google.com/g/vivo-tech/c/5AY9h15h4vc/m/OjqekVxlBgAJ?utm_medium=email&utm_source=footer&pli=1
  2. Dynamic API
    1. Need more design 
      1. not ready for further implementation for the forthcoming sprint
    2. A separated task force led by Georgy Litvinov 
      1. Dynamic API Task Force
  3. The next sprint
    1. When?
      1. 19.09. - 07.10. 
    2. What?
      1. 2022/2023 VIVO Releases Planning
        1. I18n
          • Language-aware autocompletion
            • done
          • Internationalized browse sorting
            • done
          • Moving properties labels to rdfs
            • generator
          • Adopting of online label editor to work with rdf files
          • Find solution for syntax differences between languages that does not require template customization per language
            • find problematic labels
            • decouple to parts in free marker templates
            • translate
          • Reviewing translations for French, Germany, Spanish, etc.
          • Ontology
            proposal
            # baseURI: http://vivoweb.org/ontology/core/properties
@prefix : <http://vivoweb.org/ontology/core/properties#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<http://vivoweb.org/ontology/core/properties>
  owl:versionInfo "Created by Michel Héon Université du Québec à Montréal ; heon.michel@uqam.ca" ;
.

:LabelTranslation
  a owl:Class ;
  rdfs:subClassOf owl:Thing .

:#dsgf34556
  a :LabelTranslation;
  labelKey "academic_studies_or_other";
  labelValue "Academic Studies or Other Training"@en-CA ;
  labelValue "Academic Studies or Other Training"@en-US ;
  labelValue "Akademske studije ili drugi treninzi"@sr-Latn-RS ;
  labelValue "Estudos Acadêmicos ou outra formação"@pt-BR ;
  labelValue "Hochschulstudium oder andere Ausbildung"@de-DE ;
  labelValue "Otros estudios académicos o de formación"@es ;
  labelValue "Études universitaires ou autre formation"@fr-CA ;
  labelValue "Академическое обучение или другая подготовка"@ru-RU ;
  <http://www.w3.org/2004/02/skos/core#inScheme> <.../VIVO> ;
  belongsTo <.../Wilma> .

:PropertyKey
  a owl:Class ;
  rdfs:subClassOf owl:Thing ;
  rdfs:subClassOf <http://www.w3.org/2004/02/skos/core#Concept> .

:academic_studies_or_other
  a :PropertyKey ;
  a owl:NamedIndividual ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Academic Studies or Other Training"@en-CA ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Academic Studies or Other Training"@en-US ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Akademske studije ili drugi treninzi"@sr-Latn-RS ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Estudos Acadêmicos ou outra formação"@pt-BR ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Hochschulstudium oder andere Ausbildung"@de-DE ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Otros estudios académicos o de formación"@es ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Études universitaires ou autre formation"@fr-CA ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Академическое обучение или другая подготовка"@ru-RU .

:across_subdisciplines
  a :PropertyKey ;
  a owl:NamedIndividual ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "across 554 scientific subdisciplines"@en-CA ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "across 554 scientific subdisciplines"@en-US ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "através de 554 sub-disciplinas científicas"@pt-BR ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "quer durch alle 554 wissenschaftlichen Subdisziplinen"@de-DE ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "tras 554 subdisciplinas científicas"@es ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "u okviru 554 naučne poddiscipline"@sr-Latn-RS ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "à travers 554 sous-disciplines scientifiques"@fr-CA ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "по 554 научным субдисциплинам"@ru-RU .

:active_grants_for
  a :PropertyKey ;
  a owl:NamedIndividual ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Active Grants for the"@en-CA ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Active Grants for the"@en-US ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Aktivni grantovi za "@sr-Latn-RS ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Bolsas ativas para a"@pt-BR ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Subvenciones activos para"@es ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Subventions actives pour"@fr-CA ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "laufende Forschungsprojekte für"@de-DE ;
  <http://www.w3.org/2004/02/skos/core#prefLabel> "Действующие гранты в"@ru-RU .
    3. Who
      1. https://forms.gle/qLi1PhRrrpvUrrYRA
    4. Infrastructure
      1. Wiki page
      2. GitHub project board
      3. slack private channel - i18n-sprint-september-2022

Notes

  1. Questions/Issues/Pull requests/Announcements
    1. Research publications at VIVO home page 
      1. https://groups.google.com/g/vivo-tech/c/5AY9h15h4vc/m/OjqekVxlBgAJ?utm_medium=email&utm_source=footer&pli=1
        1. Brian: it sounds like they want something a bit more involved than what they could do with the existing searchIndividualsByVClass service.  Could develop their own – ideally with the dynamic API in the future,
        2. Georgy: could also do a SPARQLQueryDataGetter scoped to the home page template. 
        3. Brian will send a response.
  2. Dynamic API
    1. Need more design 
      1. not ready for further implementation for the forthcoming sprint
    2. A separated task force led by Georgy Litvinov 
      1. Dynamic API Task Force
  3. The next sprint

    1. When?
      1. 19.09. - 07.10. 
      2. Pre-sprint meeting on Friday 16.09 at same time as developers call.
    2. What?
      1. 2022/2023 VIVO Releases Planning
        1. I18n
          • Language-aware autocompletion
            • done
          • Internationalized browse sorting
            • done
          • Moving properties labels to rdfs
            • generator
          • Adopting of online label editor to work with rdf files
          • Find solution for syntax differences between languages that does not require template customization per language
            • find problematic labels
            • decouple to parts in free marker templates
            • translate
          • Reviewing translations for French, Germany, Spanish, etc.
          • Ontology
            • Georgy:  need to have properties from different sources that override others (theme vs. VIVO vs. Vitro).  Need to have context for each set of properties.  Query by theme and application and get most appropriate translations.
            • Dragan:  Will the labels from each application and theme be mixed together in the triple store?
            • Georgy:  Yes, potentially a union of models.  But shouldn’t rely on URIs based solely on key.
            • Brian: Would be nice not to rely on semantics embedded in the URIs.  Each resource could have arbitrary URI and at least three properties: key, value, and concept scheme (which theme or application it belongs to).
            • Michel:  skos:prefLabel is better than rdfs:label.
              1. Can encode context (e.g theme) in IRI.
              2. Dragan:  Do you have to specify the theme in the key you use in the template file?
              3. Should have links in the ontology back to the Freemarker templates in which each translation is used as an aid for translators to understand the contexts in which these phrases are used.
                1. Georgy: What about translations used in multiple templates? What if we move away from Freemarker?  Is this for processing or just for aid for humans?
                2. Michel:  We could process them if available.
                3. Georgy:  Doesn’t that complicate addition of a new translation?
                4. Michel: No, not really.
                5. Georgy:  Maybe there’s a way to serve the same need without having this coupling.  Online translation instrument could possibly help with this.
                6. Michel:  It’s a complicated task to add a new language; not something for everyone.
                7. Georgy:  That’s why I created the online editor tool, to lower the barrier to creating new translations.  You see the keys on the page and you can directly type in the new translation.  To understand the context you really need to see it on the page.  This is a case where it probably is better to invest in a tool rather than depending on links in the data.
          • Other sprint priorities:
            • Georgy: move templates out of VIVO-language and Vitro-languages
            • William:  makes sense for it to be a subtask for moving languages into VIVO/Vitro.
          • Proposed division of tasks:
            • Dragan:
              1. One group gets rid of templates.
              2. One group gets rid of Java property files.
              3. Another group works on engine.
              4. Georgy adapts online translation editor?
            • Dragan: Can people work on improving the translations during the sprint, or only afterward?

    3. Who
      1. https://forms.gle/qLi1PhRrrpvUrrYRA
    4. Infrastructure
      1. Wiki page
      2. GitHub project board
      3. slack private channel - i18n-sprint-september-2022

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.