...
Indicating note-taker
Regrets
Agenda
- Questions/Issues/Pull requests/Announcements
- The issue with calendars
- No response yet
- The support link
- No response yet
- PIDSKG workshop
- the last year event - https://cost-dkg.eu/pidskg
- this year it should be in Italy on February 13th-15th
- The draft abstract - https://docs.google.com/document/d/1iGl-06AGRiWMADmY6QzX9Qv3XsrQwuc3Yta8BfU9_s8/edit?usp=sharing
- Privacy issues in graphs
- hide from display
- dynamic api and privileges for fetching
- editor (at institutional level)
- Annual report
- Sites: percentage increase: 30% more active sites (55 in 2019, 76 now)
- The issue with calendars
- PRs
- The VIVO 1.14.0 release
- review and merging of PRs
- previously listed + https://github.com/vivo-project/VIVO/pull/3805
- Release notes
- Documentation
- Internationalization
- updated, please review
- Other documentation update is needed
- Internationalization
- Release testing
- update wiki page - Release Testing - 1.14.0
- copy and adopt google forms
- review and merging of PRs
- The next sprint
- When
- 20.02.23 - 10.03.2023
- The topic
- Jena upgrade
- clean up or get rid of SDB code
- fix live backup of TDB
- External triple store performance improvement
- integration of vivo-solr into main codebase
- is that vitro-solr or vivo-solr?
- VIVO-Installer review depending on the target user: developer, infra architect, corporate/institutionnal evaluator, etc.
- Implement a new owl-reasoner (maybe https://github.com/stardog-union/pellet)
- Reformat codeSource replace tabs by spaces.
- Jena upgrade
- When
Notes
Questions/announcements
- Calendar issue: vivosurvey@gmail.com automatically sent calendar invites at beginning of year that are no longer accurate. No response on this yet.
- Vivoweb.org support link should be fixed later today.
- Dragan will present at PIDSKG about privacy
- Brian: VIVO currently has display/edit/linked data publishing role-level annotation properties that can be set on each property in the domain ontology. This is not dependent on the current UI technology and can (should) be respected on any API access to the data.
- SPARQL queries have access to all the data regardless of role level. William wonders if there are triple stores that might offer privacy controls built in. Brian mentions that we could at least parse SPARQL queries and reject those that include prohibited predicates.
- GDPR questions. William: Can a user request that they not be listed as a coauthor on someone else’s profile?
- Brian: ORCID presumably has to deal with the same issue and has a knowledge base article about GDPR. https://support.orcid.org/hc/en-us/articles/360006895834 Might be instructive.
- Michele updated VIVO registry; 76 current active VIVO databases in the registry.
Next release
- Dragan: Current sample data is not so useful for testing i18n. The Map of Science can’t be tested because the journal names are not real journal names.
- For i18n, Michel can put up sample datasets for people to use.
- William: Cucumber(?) testing framework might be useful; designed for testing microservice architectures.
- Dragan updated wiki and testing procedures; need to migrate to Google Forms. Expect to make release candidate soon. Need to improve channels of communications with end users to solicit ideas/feedback.
Next sprint
- Suggestion is to start on 20 February.
- Have freedom to use some of our sprints for internal needs / technical debt.
- Ideas
- Jena upgrade (Jena 4, Java 11)
- TDB backup utility
- Improve SPARQL triple store connection performance
- Move Vitro/VIVO languages into core
Installer
- Michel: Why not have multiple installers separate from the main repository? Different users will prefer different installers. UQAM has a separate installer repository, but synchronization can be a problem.
...