Page History

Sprint Status

Current Sprint -  Sprint 34 (July 7, 2016 – July 20, 2016)

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint34

Cory is working on LexEVS 6.4 documentation

Scott is working on an OWL2 loader issue

We are investigating lexevs-1999 - TreeServer API fails on RadLex, Version 3_13_1.

We added lexevs-2078 to this sprint.

RC.2 Deployment and Verification

• Tin to provide testing feedback
• Jacob AHP install feedback

Lexevs API 6.4.0.RC.2 is deployed on DEV. This was done manually by Rob. Jacob is still working on the AHP deploy process and expects to have it completed today.

Testing (Tin):

• Automation scripts script tests are half way donecomplete.
• There is a single character issue. Kim is adjusting his code to fix this issue.
• There is also a single bracket search issue.: {Provider}
  • Scott suggested that the Lucene search algorithm is slightly different in 6.4.
  • We have a different approach to cleansing our characters in the search. We are using a standard analyzer in Lucene for this.
  • Scott will investigate further why the query with the brackets is failing for the test use case.

Kim will create a new JIRA issue for the {Provider} issue.

Overview of QA Process (Test Plan)

• Integration tests between LexEVS and the latest browser?

• Are there tests specifically for LexEVS API?  Distributed API?  CTS2?

• JIRA issues verified for LexEVS 6.4

For LexEVS 6.5, we would like to see QA testing done earlier during the development process.

Automated tests goes go through the term browser and through Sellium Selenium automated scripts.

CTS2 and URI Resolver - Tin has a set of manual scripts to test these services. He Tin will test run these tests on QA.

JIRA issue testing - Tin will run Junits associated to the JIRA issues. He Tin will test run these tests on QA.

getIsPreffered() 6.4 Investigation

• Cory to discuss investigation findings

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2020

This is not needed for LexEVS 6.4 as Rob does has a workaround.

We are assuming this is a loader issue. We could agreed to explicitly provide a true/false value for preferred in the loader code.

TODO: Cory will update LEXEVS-1999 2020 with the proposed resolution and exit criteria.

Addition of 2078 to this sprint

We should discuss when MySQL should be upgraded to 5.7 or Maria DB 10.x. We are currently on MySQL 5.5.

We also discussed the possibility of node.js being included in the tech stack.

Docker and a Docker repository would also be a good addition.

TODO: Mayo team will send Gilberto a summary note for this discussion.

LexEVS External Users

• HL7 Loader - content from Meta

  • https://github.com/lexevs/lexevs/issues/42

• RF2 Content

  • https://github.com/lexevs/lexevs/issues/7#issuecomment-231646538

HL7 loader - This may be a source issue. Allameda is the author of this content.

Rob mentioned that the MIF loader worked for him.

Scott will follow up with the user to see if they can use the HL7 MIF loader.

It is also possible that the user is not subsetting the HL7 version correctly.

RF2 Content - Our loaders don't support RF2 (Australian content).

We will need to discuss how to proceed with Larry.

Mayo Team

• Scott - July 15th - 20th