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
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
- Dragan Ivanovic
- Georgy Litvinov
- Brian Lowe
- Mark Vanin
- Huda Khan
- Andreas Czerniak
- Benjamin Gross
- Christian Hauschke
Agenda
- Questions/Issues/Pull requests/Announcements
- Report from VIVO LG meeting
- Discussion about next VIVO conference
- New GitHub issues
- Forgot password - https://github.com/vivo-project/VIVO/issues/3770
- Academic position - https://github.com/vivo-project/VIVO/issues/3771
- ORCID confirmation - https://github.com/vivo-project/VIVO/issues/3772
- Capability map - https://github.com/vivo-project/VIVO/issues/3767
- Report from VIVO LG meeting
- The i18n redesign sprint
- Ontology
- Generator
- LanguageTag private-use subtag
- fr_FR_x_uqam
- https://github.com/vivo-project/Vitro/pull/330
- Loading of translations from triple store
- Organization of ttl files
Notes
- Leadership meeting. Dragan informed about next conditions:
- Dynamic API taskforce is going to start soon. First meeting 5th Wednesday at 5 p.m. CEST (11 am Eastern Time).
- We are in the middle of the i18n redesign sprint.
- VIVO conference this year might not be organized, the idea is to have it next spring, but there are still going to be discussed how to organize the conference.
- New Github issues:
- Forgot password - person might incidentally closed this issue, it was reopened again. VIVO has an option to change password, but it’s only available for administrators.
- Academic position - Benjamin will try to reproduce the issue, it was/is in Tenderfoot theme.
- ORCID confirmation - opened issue with email about ORCID triples. Would be good to disable the confirmation.
- Capability map - Michel opened an issue regarding his pre discussed problem with logs and how to run to it. There is some problem, if you try to run VIVO in Fuseki Triple Store or AWS Neptune Triple Store.
- The i18n redesign sprint
- Ontology - Michel gave a presentation called “French semantic ontology for form label translation”. Key points:
- No masculine, female and neutral forms in menu “NewIndividualForm”. Letters in word got from ${typeName} should be in a lowercase, now it’s in uppercase.
- Theoretical framework, that consists from three layers (taken from research work called “Advantages of thesaurus representation using the Simple Knowledge Organization System (SKOS) compared with proposed alternatives - link: research_gate_link:
- Conceptual level
- Terminological correspondence level
- Lexical level
- Create key for every situation (Hospital, Letter, Literal), but there will be a problem with having too many .ftl files, as we would need to have one .ftl file for each key.
- Skos label called “Gender” with exception keys. Idea is next: skos_conceptionSchema (prop:PropKey) =>
=> skos_Concept (prop:create_new) =>
=> skosxl_Label (prop:create_new_label_fr_CA_exception) =>
=> skos_Concept (ex:exception) =>
=> Literal (Hopital@fr_CA)
Georgy: approach presented by Michel might only work for French language, and the complexity will only grow for other languages. Approaches that you could use is brootforcely make labels for needed number of individuals (in Michel’s case around 311)
Michel: solution is only for one specific form. All of the individuals are using just two fields (create_new() and typeName) from the form - newIndividualForm. People using other languages will have to invent rules for their desired language.
Dragan: a simple solution for nowadays is: create_new_object: Department or create: Department.
Christian: approach is an overkill for todays. In German, for example, there are not lots of cases, when literal is plural or singular, is not so important. You need a specialist in a new language, which also might be a problem.
Georgy: make one universal optimal template, after discussions (using new pull request and inviting people to participate in it) with the community.
Task List
Previous Tasks
- Dragan Ivanovic to ask Arif for more info on the reported issue - https://groups.google.com/g/vivo-tech/c/gmyQIMWbm_Y
- Dragan Ivanovic to open a ticket for https://groups.google.com/g/vivo-tech/c/wDblxLmeTjs. Done, ticket available at https://github.com/vivo-project/VIVO/issues/3772
- Dragan Ivanovic will redirect reporter of this issue https://github.com/vivo-community/vivo-docker2/issues/22 to https://github.com/vivo-project/VIVO#docker
- All to analyze the issue reported in the slack (https://vivo-project.slack.com/archives/C8RL9L98A/p1663253504895989) and check whether we should open a GitHub issue and add to the i18n redesign project board - https://github.com/orgs/vivo-project/projects/4
- Brian Lowe will respond on the email https://groups.google.com/g/vivo-tech/c/5AY9h15h4vc/m/OjqekVxlBgAJ?utm_medium=email&utm_source=footer&pli=1
- All to consider participation in the sprint and register via https://forms.gle/qLi1PhRrrpvUrrYRA
- Dragan Ivanovic to work on specification of tasks for the sprint - GitHub project board
- Michel Héon to work on the translation messages ontology
- Dragan Ivanovic will bring up with leadership group that we would like to set up task force for dynamic API
- Dragan Ivanovic will create infrastructure for the next sprint (slack channel, GitHub project board, wiki page, GitHub branch, GitHub issues, etc.)
- Michel Héon to work on the ontology for UI labels (in multiple languages)
- All to think about dates for the next sprint
- Dragan Ivanovic to resolve conflicts for https://github.com/vivo-project/Vitro/pull/311 and https://github.com/vivo-project/Vitro/pull/297
- Dragan Ivanovic to write script for preparing a release candidate - started at https://github.com/chenejac/VIVO-release-publisher
- All to test the release candidate - Release Testing - 1.13.0
- Dragan Ivanovic to publish VIVO 1.13.0 release (if there is no reported issue till 1st of September)
- Dragan Ivanovic to prepare presentation for demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to send reminder for the demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to open an issue for a reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
- Dragan Ivanovic to contact Andrew Wood for resolving the issue with registration for the Slack channel
- All to consider participation in the sprint and if decide to participate to register for the sprint - link
- Dragan Ivanovic to send a require to add in the Leadership group agenda a topic for discussing Copyright owner in License
- All please help in filling this document - spreadsheet
- Dragan Ivanovic to create a draft version of a Google Spreadsheet document with labeled columns representing requirements and to share with committers
- Committers to review the structure of the document and to fill it with data for JS and CSS frameworks