Call-in Details:
Participants
Huda Khan (probably part of the time)- Jim Blake (20 hrs/wk)
- Andrew WoodsMuhammad Javed
Kitio Fofack- Mike Conlon
- Don Elsborg
Benjamin Gross- Ralph O'Flinn
Planning
Goals
- 1.10.0 Release candidate tar/zip
Elastic Search (Proposed to move to Sprint -2)
Purpose/Rationale
Integrated elastic index in VIVO to support facetview UI used by Unavco, CU Boulder, DCO
Brings index work from Product Evolution group closer to the VIVO core
Deliver more structured and rich json and eventually json-ld documents from VIVO's indexes for web consumers
Image RemovedVIVO-1423 - Consider ElasticSearch as a means to improve search and faceted search OPEN
- Email message detailing changes since 1.9.3
- Ex) Jena2 to Jena3
- JavaScript Lib Updates
- Update release and upgrade documentation
- Update test plan, and test plan template
- Create release process documentation
Open Issues
- Address In-Review tickets: https://jira.duraspace.org/issues/?filter=14416
- Code
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1486 |
---|
|
- need confirmation from another committer (author: Benjamin) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1483 |
---|
|
- need confirmation from another committer (author: Benjamin) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1451 |
---|
|
- need reviews (author: Kitio) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1435 |
---|
|
- need one more review (author: Benjamin) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1448 |
---|
|
- needs reviews (author: Asim)
- Docs
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1485 |
---|
|
- (assignee: Mike) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1473 |
---|
|
- (assignee: Mike) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-772 |
---|
|
- (assignee: Mike)- Create ticket to highlight Data Distribution API integration docs
Expand |
---|
title | Tickets targeting 1.10... |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 1000 |
---|
jqlQuery | project = VIVO AND fixVersion = v1.10 |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
|
|
Notes
- Targeting 1.10.0 Release candidate this week
- Awaiting resolution of two blocking tickets:
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1497 |
---|
|
- Likely resolution is to reintroduce assertions that were removed in
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1447 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1483 |
---|
|
- Ralph O'Flinn to help in testing
- Other tickets that are targeted for 1.10.0 but have not yet been closed will have a day or two more before being pushed to 1.10.1
- Unresolved tickets that may or may not be resolved in time for 1.10.0
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | VIVO-1451 |
---|
|
- Based on scope of code review comments, unlikely to be resolved in 1.10.0 timeframe
- To be discussed on Dev Call
- Andrew Woods to update 1.10 release testing wiki documentation
- Andrew Woods to create draft release candidate email template
Decompose the task into smaller sections and focus on what can be achieved in two weeks time.
- Team: Benjamin Gross (Clarivate), Jim Blake (Cornell), Don Elsborg ( CU Boulder )
- DELIVERABLES:
- 1) Discuss/analyze the Elastic search work done by individual sites.
2) Based on 1, implement current vitro search functionality in Elastic
3) Create instructions on how to make YOUR VIVO installation work with Elastic (on the assumption that Solr will still be the default).
4) analyze how to build a nested json-doc that represents an object ( person, publication, grant, etc ) in the index ( both SOLR or Elastic )
5) lay groundwork for analysis of incorporating semantics ( json-ld, other ) in the indexed document. Mapping the objects from VIVO-ISF to an indexed semantic document would need to involve the ontology group