Page History

...

1. New PRs
1. PR-360 Regression fix
   Georgy: We might merge it after merging i18n-redesign in Vitro repository
2. Dragan: I am going to review this PR at the beginning of the next week
2. Calendars
1. Dragan: I will investigate inaccuracy in calendars invitations.
2. William: I got that invitation from vivo-survey@gmail.com
3. Dragan: Who could be that person?
3. New issues
1. Dragan: Christian opened an issue about broken support link in vivo web interface. This link is in ftl file and now it doesn’t work.
   I will try to find out if that can be fixed. I am not sure if this approach is good at all.
4. Documentation for i18n
1. Dragan: I started working on the documentation. 
2. I had one specific question: there was i18nChecker, is it possible to suggest alternatives for that?
3. Dragan: Adding new languages now is simplified. You just have to replace language tags and translate the labels.
5. Dragan: A month ago we started discussion about new vivo release demonstration. Will see how successful it would be. VIVO instances registry might be updated soon. Once we are ready for release I am going to announce pre release meeting.
   We might organize meetings with users each month.For this release we still need to re
6. Georgy: Can I prepare a couple of PRs for fixes in custom entry forms?
   Dragan: We don’t have a strict schedule, so that shouldn’t be a problem.
7. Dragan: I hope we will be able to publish a new release soon.
8. Questions for the next sprint:
   1. When?
   2. 1. 13.02.23 - 24.02.23  ?
   3. Main topic?
   4. 1. Preparation for Jena upgrade (our Jena version is outdated), also it might be nice to clean up SDB code
      2. Ingestion and exporting of the data
      3. External triple store performance improvements (Michel)
   1. When?
   2. Main topic?
   5. Improve vivo-solr repository: 
   1. Make it appear in pinned repositories
   2. Have synced release or move it is configuration into main repositories.

   ...