...

1.  Don Elsborg
2. Ralph O'Flinn 
3. Huda Khan
4. Andrew Woods 
5. Benjamin Gross 
6. Brian Lowe 
7. Mike Conlon 
8. @Harry Thakkar
9. Jim Blake
10. Steven McCauley
11. Richard OuttenAlex Viggio

Agenda

1. Selenium Tests VIVO Acceptance Tests - Jim Blake

2. When Androids Dream (codename: androdies) - Huda Khan

3. March (18-29) sprint planning

   1. Finish work on externalizing Solr and Elasticsearch
   2. Decoupling - Dockerize: Solr, Elasticsearch, MySQL, rest-of-VIVO
      1. Reference: Docker 101 and 102
   3. 2019-03-18 Sprint Kickoff Meeting

4. Mailing list messages

   1. Some triples not getting deleted in VIVO?
      
   2. How can I backup the custom Pages that have been created?
   3. ORCID login on vivoweb.org return with error
   4. ORCiD Integration - Sync - Muhammad Javed suggesting Jim Blake has clues
      
   5. Issues with VIVO 1.9.3 and activating the ORCID integration - (do we have contact with Metcalfe House, Delhi?)
      
   6. input data Vivo last version

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-1667

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

      2. 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?
   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

   
   

...

Draft notes in Google-Doc

• Don will open a ticket regarding a proposed change to data properties for courses

• AW: Relation of interesting Ontology work to the development call

• MC: Seeking separation of concerns.  Adding terms to VIVO 1.7 ontology is expected.  VIVO 2.0 to remodel things.

• RO: perhaps the architecture is naturally separating these concerns.

• MC: Perhaps two years down the road.

• VIVO Acceptance Tests -- JB

• Acceptance tests -- used to accept the product.  NOT unit tests.

• Selenium -- drives the browser.  Mimics a user. Runs on all major platforms.  Firefox plug-in to create a test and run the test.

• Previously -- 28 test suites for testing presentation, editing, search, indexing, permissions, and much more.

• Run manually -- 3 hour process. Run on the release candidates.  Not run for 1.10, not maintained. 28 suites, 242 tests, 18,423 steps.

• Not portable.  Fixed file paths.  Difficult to write, difficult to maintain.

• Goals for new tests

• Fully automated

• Repeatable

• Portable

• Multi-browser. Ruby is headless, runs in Selenium.

• Easy to write and maintain tests

• Will use Ruby and RSpec.  Suites are now called tests.

• Simple infrastructure: TDB, no MySQL.  Run in JettyRunner, no Tomcat. Might run without Solr.

• Can write subroutines.  Can wait for threads. Automated conversion.  Now curating.

• Tests become shared_examples in Ruby.

• Four suites running. 24 to go (two weeks until Jim retires)

• Jim demonstrated one of the suites

• Run tests regularly.  Continuous integration.  Can make it happen.

• https://github.com/j2blake/vivo-acceptance-tests  dev branch.  Can become a vivo-community repo.

• Have a reasonable chance of becoming an on-going capability

• AW: Needs to go to CI as soon as possible.

• Test harness looks good for product evolution

• 242 externalized, clear text tests is crazy good.  These are claims about VIVO can do. If there are missing claims we add more tests.

• Next week -- Androdies -- a graphical view of the fly-in

• Would be good to review before next week.

• Sprint starts this coming Monday -- March 18.

• Dockerizing

• Agenda item 4 -- ORCiD related.

• VIVO confirms ORCiDs (might be broken)

• Open VIVO uses ORCiD sign-on and pulls from VIVO

• Jim has some code in development that would support push to ORCiD

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?

...