...
Agenda
- April Sprint (starts April 23)
- Post-1.10 technical priorities
- Decoupling elements of the architecture
- Clean API
- Integration testing
- ...
- Tickets being worked or considered?
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1448 - Qazi Asim Ijaz Ahmad, are you working this ticket?
- Review and testing needed
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1405 - Awaiting one more reviewer... Ralph O'Flinn?
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1408 - Awaiting one more reviewer... Huda Khan?
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1458 - Reviewed by Sarbajit Dutta, need another reviewer
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1373 - Reviewed by Sarbajit Dutta, need another reviewer (addressed by VIVO-1458)
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1435 - Needs reviewers
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1447 - Ontology team has been assigned to review... do they know that?
...
Wish to have lead for each task. Tasks 3, 4,5: in the list of teams, put names of lead or co-leads.
Task 1: Re-evaluating 1.10 branch. Create a new release candidate from where we’ll test VIVO ontology lab pull request (link is on the page). This branch has organized ontology files and this pull request needs to be tested. Need to test with real data.
Javed had tried to test VIVO instance (with pull request) with data. JAR file is supposed to convert data from Jena2 to Jena3 but this transformation did not work for Javed. This needs to be resolved before going into the sprint.
Exception thrown by one of the JAVA libraries. See https://jira.duraspace.org/browse/VIVO-1465
Lead request: Benjamin (for the whole task)
Mike to prepare documentation for release
Task 2: Elasticsearch. Jim and Benjamin’s background knowledge seems necessary for getting any progress on this task. Decision to move this task to the next sprint since Jim and Benjamin’s help needed with Task 1 and 1.10 release is a priority.
Multi-language support task: Kitio Fofack lead
Monday May 1stApril 23rd: a A sprint kickoff meeting where we go through exactly what tasks everyone will work on. At the end, having a retrospective, what worked well and what could improve with respect to process.
...
Andrew: Bring different initiatives together so that they are coordinated. So that efforts are unified.
Don: consensus on ready-only? and use of Elastic Search.
Andrew: Align our efforts of ontology group, development group and product evolution group.
Andrew: Refactoring, de-coupling to move forward ?
Huda: Yes. Try to articulate the problem first before we jump to the solutions. We need to clearly think about the problems. Why did each institution go their own way to address the problems? It is a layer before we even talk about the design. Search Index discussion is interesting but we need to go back to the core problem “how we can get the data out from VIVO easily” is important.
Andrew: Analyzing what are the workaround institutions have made and why, should be informing for our future work.
Jim: Talking about JSON output, I would love to see an example how that JSON look like. Easily can create JSON or JSON-LD. Don: Uploaded an example on Slack.
...