NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NameRolePresent
Wright, Larry NIH/NCI   
Fragoso, Gilberto NIH/NCI     

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

NIH/NCI [C] x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo 
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Sharma, DeepakMayo 
Wynne, Robert    NIH/NCI [C] x
Tran, Tin    NIH/NCI [C]  x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C] 

...

Sprint Status

 

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

LexEVS 6.4 S13-500 Agile Development - Sprint Status

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 script tests are half way complete.
  • 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 go through the term browser and through Selenium automated scripts.

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

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

Status#SprintStatus-Sprint34

Scott completed the OWL2 loader issue this sprint.

LexEVS 6.4.0 FINAL artifacts have been built.

FINAL Tag - QA

  • Ticket submission

 

Jason submitted two tickets to deploy the FINAL artifacts on QA.

  • NCI-RITM0031271: New container on QA for the LexEVS 6.4 Remote API
  • NCI-RITM0031282: CTS2 AHP on QA

Tin will test once everything is deploy. He will also request an AppScan on QA.

JIRA - LEXEVS-2131- Qualifier field not wide enough

getIsPreffered() 6.4 Investigation

  • Cory to discuss investigation findings

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-

2020

2131

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

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

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

Addition of 2078 to this sprint

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-2078

This has been fixed in Sprint 34.

has a lower priority than the current OWL2 loader issues.

TODO: Scott will investigate this in the next sprint.

We will need to discuss if the field length needs to be extended and by how much.

Gilberto suggested making it a variable length field.

JIRA - LEXEVS-1999 TreeServer API fails on RadLex, Version 3_13_1.

  • Update from Kim (Verify the load)

This issue appears to be a data issue. It is working in LexEVS 6.4.

There is no need to fix in previous versions.

Cory will close this issue

CBIIT Infrastructure Technology Catalog Update

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 - 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 on Thursday 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.

this user.

Team AbscencesTeam Absences

Mayo Team

  • Scott - July 15th - 20th

...