...
- When
- 20.02.23 - 10.03.2023
- The topic
- semantic web - https://github.com/orgs/vivo-project/projects/5/views/1
- Jena upgrade
- clean up or get rid of SDB code
- fix live backup of TDB
- External triple store performance improvement
- Implement a new owl-reasoner (maybe https://github.com/stardog-union/pellet)
- Jena upgrade
- code reorganization
- integration of vivo-solr into main codebase
- is that vitro-solr or vivo-solr?
- Reformat codeSource replace tabs by spaces.
- integration of vivo-solr into main codebase
- Deployment/installer
- VIVO-Installer review depending on the target user: developer, infra architect, corporate/institutionnal evaluator, etc.
- semantic web - https://github.com/orgs/vivo-project/projects/5/views/1
- When
Notes
- Dragan: although the support link is resolved, it is pointing to a contact form with an unknown recipient email address. Brian: we should provide more structured information at the support page (mailing list, slack, some additional text, etc.). William: Do we have an account for accessing wordpress at https://vivo.lyrasis.org/. Dragan: No, but will try to find a way to get one. Action: Dragan will contact Lyrasis admins to get an account.
- Georgy: TAPIR final workshop has been organized as an online event, partially in English, partially in German. It included some presentations about VIVO (semi-automated reporting by using Dynamic API).
- Dragan: Sample data repository should be re-organized. The goal is to have the same structure in all subdirectories which can be ingested in VIVO by copying in VIVO_HOME/rdf directory. Brian: if ttl is huge, might be an issue because it will be firstly loaded in memory, it would be nice to split to smaller files (up to million triples). Dragan: Sample data reorganization might be one of the topic of the next sprint (including adding ingestion of sample data in deployment/building process for testing purposes)
- William reviewed the i18n-redesign branch and provided feedback about some issues. Dragan created a PR for fixing issues with layout, William reviewed that and found one layout issue is still there - https://github.com/vivo-project/VIVO/pull/3810#issuecomment-1420871483. Dragan will fix that. Georgy will fix an issue with faux data properties when range is xml literal. There is also an issue with French data and publication graphs. Brian explained how it might be resolved. Dragan will create a PR for that.
- Dragan: the next sprint will start on February 20th. William: Can we add improvements in building/deployment process? Dragan will add that as a topic of the next sprint. William and Michel discussed the implication of those changes, and agreed it will improve VIVO customers' experience. Dragan created a project board - https://github.com/orgs/vivo-project/projects/5. We will work further on specification of tasks.
- Dragan: although the support link is resolved, it is pointing to a contact form with an unknown recipient email address. Brian: we should provide more structured information at the support page (mailing list, slack, some additional text, etc.). William: Do we have an account for accessing wordpress at https://vivo.lyrasis.org/. Dragan: No, but will try to find a way to get one. Action: Dragan will contact Lyrasis admins to get an account.
- Georgy: TAPIR final workshop has been organized as an online event, partially in English, partially in German. It included some presentations about VIVO (semi-automated reporting by using Dynamic API).
- Dragan: Sample data repository should be re-organized. The goal is to have the same structure in all subdirectories which can be ingested in VIVO by copying in VIVO_HOME/rdf directory. Brian: if ttl is huge, might be an issue because it will be firstly loaded in memory, it would be nice to split to smaller files (up to million triples). Dragan: Sample data reorganization might be one of the topic of the next sprint (including adding ingestion of sample data in deployment/building process for testing purposes)
- William reviewed the i18n-redesign branch and provided feedback about some issues. Dragan created a PR for fixing issues with layout, William reviewed that and found one layout issue is still there - https://github.com/vivo-project/VIVO/pull/3810#issuecomment-1420871483. Dragan will fix that. Georgy will fix an issue with faux data properties when range is xml literal. There is also an issue with French data and publication graphs. Brian explained how it might be resolved. Dragan will create a PR for that.
- Dragan: the next sprint will start on February 20th. William: Can we add improvements in building/deployment process? Dragan will add that as a topic of the next sprint. William and Michel discussed the implication of those changes, and agreed it will improve VIVO customers' experience. Dragan created a project board - https://github.com/orgs/vivo-project/projects/5. We will work further on specification of tasks.
Task List
- Dragan Ivanovic will contact Lyrasis admins to get an account for https://vivo.lyrasis.org/
- Dragan Ivanovic will fix issues with layout and French sample data and publication graph - https://github.com/vivo-project/VIVO/pull/3810
- Georgy Litvinov will fix the issue with faux data properties with xml literal range - https://github.com/vivo-project/Vitro/pull/363
- William Welling will review previously described issues
- Dragan Ivanovic will work on specification of tasks for the next sprint - https://github.com/orgs/vivo-project/projects/5
Previous Tasks
- Dragan Ivanovic to send a test email through contact form - https://vivo.lyrasis.org/contact/
- William Welling to complete review/testing of https://github.com/vivo-project/VIVO/pull/3805 and to summarize results in the PRs comments
- Dragan Ivanovic to review William's comments and check what should be fixed/resolved before merging of the the branch
- Georgy Litvinov to fix issues with Russian email templates
- Georgy Litvinov to fix issues with faux data properties
- All to think about organization/improvements of sample data, Dragan Ivanovic to add an item in the next week agenda for discussion
- Dragan Ivanovic in communication with Georgy Litvinov to write/update documentation for faux (data) properties
- Dragan Ivanovic to review and merge
...