...
- Questions/Issues/Pull requests/Announcements
- Expert Finder Webinar
- i18n issue with ordering and filtering by the first letter - https://vivo-project.slack.com/archives/C8RL9L98A/p1658820115012559
- Documentation improvement
- Performance tuning - https://github.com/vivo-project/VIVO/issues/3732
- Change URI feature - https://github.com/vivo-project/VIVO/issues/3731
- Java HEAP out of memory - https://github.com/vivo-project/VIVO/issues/3730
- Float data properties regex - https://github.com/vivo-project/Vitro/pull/318
- Dynamic API, reengineering of io - https://github.com/vivo-project/Vitro/pull/319
- The next sprint
- When?
- 19.09. - 07.10.
- What?
- Improvement of expressiveness of notation
- Iterative steps
- Operation data
- Improvement of UI
- Support for more rich structure of entities
- Notation for UI layouting
- Completion of authorization and authentication
- Extension of SHACL rules
- Editor for definition of a dynamic action
- VIVO based on dynamic actions
- Improvement of expressiveness of notation
- Who?
- When?
- Summer vacation period
- 05, 12, 26 of July, 2022
- 09, 23, 30 of August, 2022
Notes
- Questions/Issues/Pull requests/Announcements
- Expert Finder Webinar was a good time for VIVO, since it’s one of the open-source project here and one that is vibrant with its development.
- Nice to have dynamically populated different field, because now we have user-defined hard-coded internalization rules. Sigma had similar problem, they overcome it with they’re own i18n files. Problem appears, due to collisions in languages. In a short-term: custom fields (that, probably, might/have already problem).
Michel (had this problem): you can get rid of it by, probably, make translation inside VIVO (Spanish ontology). Problem could also be in a SPARQL query. What VIVO version they use, might be resolved in 1.12 (high chances only for French language).
Brian: mentioned this issue https://github.com/vivo-project/VIVO/issues/3606
Georgy: for multiple languages you need multiple modifiers or have fields based on the languages. Solution might be - extend modifiers. - Documentation improvement - small issues need further look at.
- Try to improve your heap (make it bigger). Other solutions might appear after Dragan will try to reach this person.
- Little typo with dot at the end of the float number now fixed.
- Lots of information about technical side: how to return json in rest-api, everybody is welcomed to participate in a future testing.
- You can register for next sprint already.
...