Date

12 Mar 2019

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-05:00)

To join the online meeting:

Go to: https://duraspace.zoom.us/j/823948749
Or iPhone one-tap :
- US: +14086380968,,823948749# or +16468769923,,823948749#
Or Telephone:
- Dial(for higher quality, dial a number based on your current location):
- US: +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833
- Meeting ID: 823 948 749
International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5

Indicating note-taker

~~Selenium Tests~~ VIVO Acceptance Tests - Jim Blake
When Androids Dream (codename: androdies) - Huda Khan
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
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
Status of In-Review tickets
1. Soft balls
  1. 1. Low-hanging - need one more reviewer - Brian Loweis reviewing
  2. 1. Low-hanging, documentation - Mike Conlon, can you give this one a review?
2. Regular balls
  1. 1. New
  2. 1. Kitio Fofack ? Orcid and i18n
  3. 1. Is this feature of broader interest?
  4. 1. Andrew Woods to look into
  5. 1. Mostly trivial, with conversation around Tomcat version support
  6. 1. Relatively straight-forward bug fix
  7. 1. An important step for i18n... resolves many other open issues
  8. 1. Kitio Fofack to review?

Received

1. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design
1. Should be low-hanging
1. Where does this stand? What is needed to add more person identifiers to VIVO?
1. Mike Conlon : thoughts on where this stands?

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.

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

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.