Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Sprint Status

Current Sprint -  Sprint 50 (February 16, 2017 – March 1, 2017)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint50

• Report writer team may need to test with Java8

DEV Server Configurations

• Planning and usage discussion

Discussion Points:

• Dev VM (Mayo) is set up and we confirmed we can log in
• Dev Blade - Jacob is waiting for the Mayo Dev team to let him know if tomcat 8 will work.
  

Decision Points:

• Cory to confirm with Jacob what version of tomcat 8.x NCI is going to run.

• DEV Blade
  • 6.4.1.3

• • .FINAL
• Mayo DEV VM
  • • 6.
  4.1.3.FINAL
  • • 5.0 SNAPSHOT

Discussion Points:

• LexEVS 6.4.1.3.FINAL

• is loaded on Mayo DEV VM
• LexEVS 6.5.0 SNAPSHOT will be loaded on DEV Blade with CentOS 7.
  • Jacob has a ticket for this work.
• We will want a separate DB (MySQL 5.6) for the Blade and the VM Dev instances.

Decision Points:

• Mayo team will request separate DBs for the Blade and the VM Dev instances.
  • Send note to Jacob.
    

Value Set Loading Enhancements

• Load Update

Discussion Points:

• Scott and team have identified the current issues with the value set failures.
• Tracy has not had an opportunity to test the mass load script yet.
  
• Mayo team will meet with Jason and Kim to discuss value sets architecture tomorrow
• There are individual value set loads that are failing.  Scott will look into them first before looking at the issues in the multiple value set definition load script.
  
• Tracy mentioned that the run she started on DEV appears to still be running.
  

Decision Points:

LexEVS Version/Naming Discussion

Discussion Points:

• The Mayo team will look at the new CTS2 JIRA issues created by Tracy.
• We will determine if our current implementation can accommodate the request.
• If it can't, can we implement it in CTS2.
• If that can't be done, we can look at implementing it in a different service.
  
• Larry suggested that there should be a simpler REST interface than CTS2.
• LexEVS Software Release Versioning
• Larry suggested if the release has a major impact on the end user (consumers), then we would increment the major version number.
  
• If the user created their own instance of LexEVS, then the versioning would affect them more than just being a consumer of the API. 
  • Larry mentioned that they (customers) are coming up with some criteria and examples of what they would like. 
  • They will have some examples/criteria in the next couple of weeks.
  • This may be something like convenience methods or CTS2 extensions.
  • 
    

Decision Points:

• The dev team will think about this and discuss again next week.hold off looking at the existing JIRA issues and see if CTS2 can accommodate this in the next sprint.
• The dev team will work on the tree extensions instead in this sprint.
  

LexEVS Logical Role Relationship

• Discussion with Kim

Discussion Points:

• There is an example in the OBI OWL2 source.
• The AnyURI is declared as data type in the annotation property

Discussion Points:

• End users are not familiar with the CTS2 model and REST API.
  
• This doesn't fit well with end LexEVS users as they are not familiar with the CTS2 model.
• It was suggested that it may make sense to have a REST API that represents the LexEVS Model.
• Example scenarios:
• • For a given regime concept, give me the associated drugs. (the user knows the relationship)
  • This was available under caCore.
• Users of CTS2:
  
  • Bob Kline (CTL), CTRP, Brian Bazilla
• Tracy created multiple JIRA issues capturing the issues:
  • LEXEVSCTS2-138-144
    
    • Most of these issues were possible under caCore data services.
• Larry suggested looking at the UMLS REST interface
  • https://documentation.uts.nlm.nih.gov/rest/home.html

Decision Points:

• Mayo Dev team will discuss and come up with some possible solutions and report back to the team.

• into LexEVS model (an association on an association).  The LexEVS API wouldn't handle this well either.
  

Decision Points:

• Scott mentioned that our load will ignore this case
• Scott will sent a snippet source example to Gilberto.
  

LexEVS Logical Role Relationship

• Discussion with Kim

Remote API timeout issue

• Discussion with Kim

Discussion Points:

•  Intermittent socket timeouts from the Remote API.
• Scott is able to reproduce this issue locally.

Decision Points:

• Scott will investigate why our system tests are not hitting the same issue.

Discussion Points:

• Nothing noted.

Decision Points:

Mayo Team

• Cory -
• Scott -
• Craig - March 6-13

NCI

• Tracy
  • March 9-17
• Rob
  

  • March 20-24