...
Indicating note-taker
- Brian Lowe
- Huda Khan
- Mike Conlon
- Steven McCauley
- Benjamin Gross
- Andrew Woods
- Julia Trimmer
- Ralph O'Flinn
- Alexander (Sacha) Jerabek
- Pierre Roberge
- Michel Héon
- Don Elsborg Richard Outten
Agenda
- Announcements
- VIVO Triple Store Roadmap Proposal
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1741
- VIVO Triple Store Roadmap Proposal
- 2020 - VIVO Sprints2020 Sprint Planning
- UQAM i18n planning
- VSTF planning
- Any issues with the move from 'develop' to 'master'?
- VIVO, Vitro, VIVO-Harvester, vivo-acceptance-tests
- Auto-closed Vitro PRs
- Auto-closed VIVO PRs
- VIVO Photo issues:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1738 - email to tech list - how to delete photos via API ( file and triples )
- Vitro pull-requests
- authorization update for self editors - no JIRA
- RDF Delta patch messaging -
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1718
- looks goodJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1658
Tickets
Status of In-Review tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
Actions
- Organize a session on Brown's work on editing
Announcements
- VIVO Triple Store Roadmap Proposal
- VIVO-1741 - Change default content triplestore to TDB RECEIVED
Awaiting community input before taking action on the ticket. No comments from non-committers today. Impacts: changing an example configuration file, so the default will change but no technical changes. Later, decouple more to allow easier integration with any triple database.
2020 Sprint Planning
- UQAM i18n planning
- VSTF planning
Andrew: If we get 4 names or more for any of the topics, that’s critical mass for running a sprint. Once that happens Andrew will take action for scheduling. Pierre: It is likely the German community would participate. Christian raised possibility of the international editor in the past.
Some details have been added to sprint planning page recently. Andrew is soliciting additional information on the wiki page. Pierre: Can we add Michel to wiki editors list?
What’s the end result of the sprint? What skills are required? What aspects of UQAM’s previous editor demo will be included? Pierre: Sprint timing will be good because they are in the process of wrapping up what they have done already, including documentation and code release. Andrew: Do you have ideas for what the sprint would do? Michel: Push code to community. Want to include in next official VIVO release. Would need review and testing, especially since it is affecting admin parts of the codebase. Andrew: Is existing code based on 1.11? Michel: Yes. Rolled into Maven, as well. The code is an overlay currently, but would be better for it to actually be within the VIVO code.
Andrew: Any reservations about rolling that code into core? Ralph and Benjamin say no. Brian and Don say no. Andrew: Excellent. It will largely be an integration effort in that case, with some amount of iteration after review.
Pierre: We will provide all translation files. If some people want to review the translation as well, that would be interesting. Andrew: TIB has struggled a bit with integrating their language files into the VIVO-languages repository. Would be great if we could make progress on improving this process. Maybe there just aren’t enough details. Benjamin: Issue in the past was a lot of changes were made on the TIB fork and pull requests were not submitted incrementally. Michel: I don’t think it’s too much to have all languages inside main distro. Sprint should be in two steps: 1. Integrate code into core, 2. Develop a packing method for integrating a specific language into internationalization process. Andrew: Current process involving pom files is not entirely straightforward. Maintenance is an issue too. E.g. Changes are made in German language files but not other language files. Shouldn’t they all be within one GitHub repo ?
Michel: What is the next step? Andrew: We need a critical mass of people. Currently… there is one. Andrew to make additional call for participation. Don’t see anybody from VIVO Scholar Task Force (VSTF) here, but they are in a similar situation; they have a lot of code they are interested in integrating. Andrew to leap into action for scheduling, prioritizing UQAM’s availability, once we have critical mass.
Any issues with the move from 'develop' to 'master'?
- VIVO, Vitro, VIVO-Harvester, vivo-acceptance-tests
- Auto-closed Vitro PRs
- Auto-closed VIVO PRs
Any issues with this? What happened with the pull requests? GitHub automatically closed them since the develop branch no longer exists. Benjamin: Any way to retain audit trail, just point the old PRs to the new master branch? Andrew: Pulling down the existing code from the PR and resubmitting is a possibility if we don’t mind separating from old comments. Don: Noticed you also made some changes to projects in vivo-community. Andrew: Did it for consistency.
Discussion about how changes in vivo-community should be communicated to community vs committers. Benjamin: There are some cases where the develop branches were being used, e.g. https://github.com/vivo-community/vivo-project-template. Plus probably documentation elsewhere.
VIVO Photo issues:
- VIVO-1738 - Image uploads aren't completed for case where people are not in kb2 graph OPEN
- email to tech list - how to delete photos via API ( file and triples )
Don: Awhile ago Nate discovered that if you add photos through the GUI for individuals not in kb2 there are problems. We use Harvester and named graphs for everything except photos, so this is a problem. Ralph: Uses the VIVO photo generator utility (Javed’s tool). Then image triples get loaded into their own graph. Don: We’d have to change our process but maybe. Sometimes we truncate the entire person graph for ease. Any way to delete? Benjamin: There is a method in the code already, it just can’t be called as an API at this time.