Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Weekly Tech PM Meeting

(moved here this week)

Discussion Points:

• DEV Blade - Update to 6.5.0 RC 1
  • lexevs-remote is up and running and tested by the browser.
    
  • lexevs-service (CTS2) deployment is having issues.  Cory is working with Jacob to resolve this issue.
• QA blade server - work is pending the success of the DEV blade server.
  
• Docker - Mayo and Systems team met on Monday.  Systems team will assist in putting Docker containers of specific versions on the NCI Nexus server for Mayo to use with the lexevs-system-test Docker scripts.
  
  • This will include MySQL 5.6.x, Java 1.8, CentOS7, and Tomcat 8.0.x
  • The NCI Nexus server is only available on the NCI VPN.
    

Decision Points:

Sprint Status

Current Sprint -  Sprint 55 (April 27, 2017 – May 10, 2017)

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

When lexevs-service is successfully deployed and tested on dev, we will generate the final 6.5.0 versions of lexevs.

• Testing update
• Moving up the tiers
• URI Resolver CTS2 (Java 1.8)

Discussion Points:

• Jacob to install URI Resolver and CTS2 in separate containers.
• Kim's browser testing looks good.
• Tracy/Rob to load the latest source and then test today.
  • Kim/Jason will test with the latest source when Tracy has completed the load.

Decision Points:

•  If everything goes well, we should be able to create a FINAL version next week.

Value Set Architecture Discussion

• Use case for OWL expressivity

• Discussed above.

Decision Points:

Discussion Points: 

• Value Set Architecture
• We had a meeting last week and another one is scheduled for this afternoon.
• Scott asked - What is the use case that would require us to use the triple store or OWL2 API?  Do we need an OWL representation?
  • Larry suggested it could be used for concept models, role groups, and traversal.  For value sets - it was for more rich information (hierarchical)
• Are there aspects of the OWL class that can't be stored in OWL?
  • Restrictions, Anonymous nodes are not well defined in LexEVS API.
• LexEVS API performance may be an issue and a reason to move to OWL.
• Larry offered a use case: Structured organization of the role relationships in the browser. They could only separate out roles that were directly attached.
  • This is associated to reasoning and OWL.
  • This is a general coding scheme issue (not necessarily associated to value sets).
• Gilberto - We only need OWL it if we show the OWL semantics. 
  
  • Relationships without the anonymous nodes is faster.
  • In the value sets, we don't need the expressivity. 
    
  • There may be a performance penalty to navigate from a concept in a value set to another entity.
    

Decision Points: 

Docker - Next Steps Discussion

• Update from recent meeting

Discussion Points:

• The server is configured with Jenkins and Docker.
  • There are a few adjustments that are still needed.
• Next Steps - Meet with the the systems group and work on reusable containers that have approved NCI tech stack software.
  

Decision Points:

• Discussed above.

Discussion Points:

• This has already been discussed above to some extent.
• We will need to work through more of this during our VS architecture discussion.
  

Decision Points:

Discussion Points: Decision Points:

• Scott will coordinate with the NCI team when we plan to change the DNS settings for lexgrid.org.

Decision Points:

Access to NCI Wiki Pages

Discussion Points:

• Craig was wondering if LexES Project Documents folder and sub folders should be visible to all.
  • Larry suggested these folders should be public unless there is private information.
   

Decision Points:

• Larry requested that we check the contract to verify what is mentioned.  Does it specify that certain pages should be public?
  • Kumar will investigate what the contract contains.
• It was decided to leave it open to the public for now.
  

Deployable LexEVS Containers

• • NCI Containers for deployment

Discussion Points:

• This was discussed above.

Decision Points:

•  OWL2 loader issue -
  
  • term-group changed to term-type
  • 5-6 qualifiers have to be renamed manually.
  • Gilberto suggested this be put into the preferences file.

Decision Points:

• Rob will generate a JIRA issue for this.
• Scott will work on this on Monday.
  

LexEVS External Users

Discussion Points:

• Combination Entity and SubjectOf Endpoint (CTRP -Brian Pizzillo)

Decision Points:

• The Mayo team will respond to Brian

LexEVS External Users

•  Interest in LexEVS Docker containers for deploymentF
• caDSR content admin
  • Run queries against LexEVS and using Python (not using LexEVS Admin)

Discussion Points:

•  Scott has sent the user in caDSR some sample code and tips on how to directly access the LexEVS DB.
• The user is working on the UMLS.  The user wants the mappings.
  • The user wants to retrieve the semantic types for certain terms and also get the mappings.

Decision Points:

• Scott to send the code examples to Tracy and she will add the code to the LexEVS coding examples on the wiki.

Mayo Team

• Cory - May 8
• Scott
  
  • April 28 - May 85
• Craig - May 8

NCI

• Tracy
• Rob
• Kim