Page History

...

1. March (18-29?) sprint planning

   1. Ingest
   2. UI
   3. Decoupling
2. Docker experience? Interest from UF in helping with VIVO 1.10 Docker image
3. Product Evolution updates? (is there a wiki landing page?)

4. Mailing list messages

   1. Re: help related to facetview in vivo - (Jan 30th) Facet view expertise, anyone?
   2. jquery.scrollTo error - (Dec 13) Do we need to upgrade `jquery_plugins`? – Has anyone else been able to reproduce?
   3. No Subject - (Dec 12) "How can I add more associated profiles for that particular  editor."
   4. Freemarker Template Error (Dec 10)
      
   5. [vivo-tech] help regarding the custamization (Dec 6)
      
   6. [vivo-tech] Inferencing engine not adding triples needed (Dec 4)

5. Status of In-Review tickets

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

   1. Soft balls

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

         1. Don Elsborg ?

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

         1. Only touches one file

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

         1. Low-hanging - need one more reviewer - Brian Loweis reviewing

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

         1. Low-hanging, documentation - Mike Conlon, can you give this one a review?

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

         1. Low-hanging... need one more review - Huda Khanto review
   2. Regular balls
      

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

         1. New

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

         1. Kitio Fofack ? Orcid and i18n

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

         1. Is this feature of broader interest?

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

         1. Andrew Woods to look into

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

         1. Mostly trivial, with conversation around Tomcat version support

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

         1. Relatively straight-forward bug fix

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

         1. An important step for i18n... resolves many other open issues

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

         1. Kitio Fofack to review?

6. Received

   Expand

   Expand Jira server DuraSpace JIRA jqlQuery filter=14802 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1666   (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1665   Should be low-hanging Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1663   Where does this stand? What is needed to add more person identifiers to VIVO? Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1644   Mike Conlon : thoughts on where this stands?

   
   

7. Bugs (1.11)

   
   

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=14702 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

...

• 2019 sprint series

• Planning first sprint for March: focus on architectural fly-in topics

• Outstanding items from last sprint? Need to merge development branch

• decoupling search: need to resolve smoke tests

• Solr working; Elastic still needs to be implemented

• Integrating search engines and “shapes” as defined by Product Evolution group

• Shapes and JSON schema

• Not yet fleshed out; needs a second pass: integrating with ontology, etc.

• Product Data definition:

• https://docs.google.com/spreadsheets/d/14EJH8qNIoHpw7g3r7MzHiIBekhXaF385sCZZd8OvXac/edit#gid=471799009

• Start to json-schema (needs more work)

• https://github.com/vivo-community/product-evolution-sandbox/tree/master/experiments/duke/elastic_import/schemas

• Can search engine indexing and core VIVO shapes be bridged? Probably not ready yet, but Jim Blake can have a draft ready prior to sprint

• Using the DocumentModifier class

• Might be better to focus on modularization of VIVO components for now

• Necessary steps: what are the queries that need to be run? How to maintain multiple indices?

• Don Elsborg may be able to reuse CU’s python VIVO export to Elastic document scripts for Elasticsearch

• Triple-pattern fragments: lingering issues

• All data in triple store is publicly exposed

• TPF server is currently configurable: maybe needs more documentation

• Should data store be closed down by default? That would align with all best practices re: security, db administration

• March sprint goals: Solr and Elastic; modularization; Docker

• Upcoming releases: first, a maintenance release (maybe end of March); then, modularization

• Dockerization: tested locally, needs more work

• Product Evolution meeting

• JSON specification, GraphQL

• Adding shapes (resources): how to customize

• Mailing list messages: cleaning the slate

• Can Google Groups messages be forwarded to Slack?

• Need to update jQuery plugins: Ralph will examine

• Failed inferencing: mysteriously disappeared, problem solved

• Don will handle facetview

• Messages to be removed

• Closing out softball items under 5a

• 1674: update of image processing libraries

• Breaks on 1.9: may require too much work to get backported

• merged with Graham’s updates?

• Original library is no longer supported; doesn’t work with Open-JDK

• Ralph: should be done by next week

• 1672: error catching; Benjamin on it

• 1667: back to Graham

• 1659: documentation update; over to Mike

• 1525: Huda will take a look

Actions

•   

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

  - Brian Loweis reviewing
•  

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

   - Mike Conlon, can you give this one a review?
•  

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

  - Huda Khanto review

Previous Actions

•  Brian Lowe  confirm LDF server issue with TDB content stores
•  Don Elsborg - add jira tickets for abox/tbox use cases - one ticket for each use case
•  Brian Lowe  - check with ontology group on handles
•  Alex Viggio will bring news of Elasticsearch instead of Solr up with Product Evolution.  

...