Call-in Details:

• https://duraspace.zoom.us/my/vivo1

Participants

1. Huda Khan (probably part of the time)
2. Andrew Woods
3. Kitio Fofack
4. Mike Conlon
5. Don Elsborg
6. Benjamin Gross
7. Ralph O'Flinn

Planning

Goals

1. 1.10.0 Release candidate tar/zip
   • https://github.com/vivo-project/VIVO/releases
2. Email message detailing changes since 1.9.3
   1. Ex) Jena2 to Jena3
   2. JavaScript Lib Updates
3. Update release and upgrade documentation
   • https://wiki.duraspace.org/display/VIVO/VIVO+1.10.0+Release+Planning
4. Update test plan, and test plan template
   • https://wiki.duraspace.org/display/VIVO/Release+Testing+-+1.

• Multi-language Support
• Elastic Search
• Depth on Capability Map

Elastic Search

Purpose/Rationale

1. Integrated elastic index in VIVO to support facetview UI used by Unavco, CU Boulder, DCO

2. Brings index work from Product Evolution group closer to the VIVO core

3. 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

1. Decompose the task into smaller sections and focus on what can be achieved in two weeks time.

2. Team: Benjamin Gross (Clarivate), Don Elsborg ( CU Boulder )
3. DELIVERABLES:

4. 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

Multi-Language Support

Purpose:

Implement full i18n proof on concept on a simple form. The form should be able to display data accoring to the selected language but also to save them in the database in respect to the language currently selected.

Depth on Capability Map

Purpose:

...

1. • 10
   • https://wiki.duraspace.org/display/FF/Release+Testing+Procedures+-+Template
   • Steps for community testing
2. Create release process documentation

Open Issues

1. Address In-Review tickets: https://jira.duraspace.org/issues/?filter=14416
   1. Code

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1486

          - need confirmation from another committer (author: Benjamin)

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1483

          - need confirmation from another committer (author: Benjamin)

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1451

          - need reviews (author: Kitio)

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1435

          - need one more review (author: Benjamin)

      5. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1448

          - needs reviews (author: Asim)

   2. Docs

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1485

          - (assignee: Mike)

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1473

          - (assignee: Mike)

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-772

          -  (assignee: Mike)
      4. Create ticket to highlight Data Distribution API integration docs

2. 
   

   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

1. Targeting 1.10.0 Release candidate this week
   1. Awaiting resolution of two blocking tickets:

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1497

         1. Likely resolution is to reintroduce assertions that were removed in 

            Jira
            server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1447

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1483

         
         
         1. Ralph O'Flinn to help in testing
   2. 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
2. Unresolved tickets that may or may not be resolved in time for 1.10.0

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1451

      
      
      1. Based on scope of code review comments, unlikely to be resolved in 1.10.0 timeframe
      2. To be discussed on Dev Call
3. Andrew Woods to update 1.10 release testing wiki documentation
4. Andrew Woods to create draft release candidate email template