...

1. The update on issues reported by Michel Héon and  Sarbajit Dutta
   1. https://vivo-project.atlassian.net/browse/VIVO-2007
   2. https://vivo-project.slack.com/archives/C8RL9L98A/p1631207481027000
2. The new issues/questions
   1. https://vivo-project.slack.com/archives/C8RL9L98A/p1633128258060400 
   2. https://vivo-project.slack.com/archives/C8RL9L98A/p1632992863059800
   3. https://groups.google.com/g/vivo-tech/c/DSoi-mWgrnQ/m/Q3fV6EG6BQAJ?utm_medium=email&utm_source=footer
3. New contribution - Michel Héon 
   1. https://github.com/vivo-project/VIVO/pull/250
4. Discussion about priorities for further development of VIVO - https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
   1. The topic will be i18n
      1. internationalize Solr index / autocomplete (core per language / separate sets of fields per language)?
      2. Leftover i18n tasks - nonblockers from 1.12 (vocabulary services / form improvements)
         1. https://vivo-project.atlassian.net/browse/VIVO-2002
         2. https://vivo-project.atlassian.net/browse/VIVO-1955
         3. https://vivo-project.atlassian.net/browse/VIVO-1954
         4. https://vivo-project.atlassian.net/browse/VIVO-1941
         5. https://vivo-project.atlassian.net/browse/VIVO-1935
         6. https://vivo-project.atlassian.net/browse/VIVO-1920
         7. https://vivo-project.atlassian.net/browse/VIVO-1895
         8. https://vivo-project.atlassian.net/browse/VIVO-1879
         9. https://vivo-project.atlassian.net/browse/VIVO-1878
      3. Move i18n properties from resource bundles to ontology / (editable) RDF
      4. Find solution for syntax differences between languages that does not require template customization per language
      5. Online VIVO translations 

Notes

1. The issue reported by Michel Héon (https://vivo-project.atlassian.net/browse/VIVO-2007) has been closed because the issue can't be reproduced
2. Brian Lowe communicated with Sarbajit Dutta via slack about the issue reported by Sarbajit
3. Dragan Ivanovic will contact Naveen Sadhu (https://vivo-project.slack.com/archives/C8RL9L98A/p1633128258060400) and ask for more details about the issue (the property is not generated on the profile page, or not searchable, etc.)
4. Adding Data Distribution API to the VIVO Core was discussed in the past, but the decision of the VIVO core team was to keep that in the separate module outside of core (https://vivo-project.slack.com/archives/C8RL9L98A/p1632992863059800)
5. VIVO has not been tested with Tomcat 10, it might be it is not working as expected, although we would like VIVO works with any version of Tomcat (https://groups.google.com/g/vivo-tech/c/DSoi-mWgrnQ/m/Q3fV6EG6BQAJ?utm_medium=email&utm_source=footer)
6. Michel Héon briefly presented the new contribution. It will be merged and released with VIVO 1.13.
7. Discussion about priorities for further development of VIVO - https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
   1. internationalize Solr index / autocomplete (core per language / separate sets of fields per language)?
      1. might be complicate for the implementation, not realistic to be VIVO 1.13, but might be VIVO 1.14.

   2. Jira
      server VIVO JIRA serverId a9c2e737-83c0-3a0a-86ab-3ac9180f5705 key VIVO-2002

      1. Georgy Litvinov implementation of GUI (developer mode) for localization might be solution for giving the context during translation of UI
   3.  We will continue discussion next week

Draft notes on Google Drive

...