Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Sprint Status

Current Sprint -  Sprint 54 (April 13, 2017 – April 26, 2017)

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

OWL2 Release Update

• Final OWL2 source

Discussion Points: 

•  The current OWL2 source that we have should not have any additional structural changes.
• We don't anticipate any further changes for LexEVS

Decision Points:

• Testing update
• Install LexEVS admin
• Moving up the tiers
• URI Resolver (Java 1.8)
• CTS2 Deployment ticket for Dev

Discussion Points:  

• The browser and term browser are running in their containers on DEV.  There have been no reported problems.

Decision Points:

• Rob tested loaders for 6.4.1.4, not 6.5.0
• Kim reported that the browser is running fine against 6.5.
• Cory created a PTE for URI Resolver for 6.5.0
  
• Cory created a ticket for Jacob to install URI Resolver on Dev blade server.
• Tracy suggested that the DBs on the tiers should be seeded with the PROD data.
• We agreed that testing on DEV should be complete by end of this sprint.
• Cory will rebuild with Jason will talk to Jacob.  Jacob will need to configure the blade servers on QA/STAGE/PROD for the 6.5.0 release so testing can continue.

Value Set Loading

• New/Updated Removal scripts

Discussion Points: 

• We are planning a value set architecture discussion for early next week.
• Scott has been doing some value set investigation in preparation for this meeting.
  

Decision Points:  

• We will need the requirements from NCI in order for the Mayo team to propose a new architecture.

• .FINAL tag when testing is complete for the QA tier.
• We discussed LexEVS admin install (local loader environment) and if we should create a PTE for this.
  
  • Tracy/Rob agreed.  
• LexEVS 6.5 will be on the new blade and LexEVS 6.4 will be on the old blade running in parallel on STAGE and PROD.
  
  

Decision Points:

• Cory to create ticket to deploy CTS2 on DEV blade.
• Cory to create a PTE for installing LexEVS admin.
  

Value Set Architecture Discussion

Discussion Points: 

• Working on scheduling a meeting to include everyone to attend.
• We looked quickly at the value set requirements
  • LexEVS 6.5.1 Value Set Architecture
  • One requirement is to reduce errors in the workflow when loading value sets.
    

Decision Points: 

Tree Extensions in 6.5

• Testing/Validation

Discussion Points:  

•  Kim will test when 6.5.0.RC is installed on DEV.Kim mentioned that he verified the tree extension issues that were fixed.

Decision Points: 

Docker - Next Steps Discussion

• Update from recent meeting

Discussion Points:

• Jacob will install/configure a server for Docker next week.mentioned that he has the server configured. He is working on setting up Docker.
• Phil/Wei are looking into setting up Jenkins and running the Docker script in a master/slave setup in JenkinsCory will work with Jacob to get our LexEVS system tests configured and running.
  

Decision Points:

LexEVS Wiki Documentation

Discussion Points:

• The documentation should be updated.
  
• Tracy mentioned that there are CBIIT technical writers that may be able to help to rework the wiki documentation.
• Larry mentioned that users that want to program against our APIs have a hard time navigating to a "general developer" starting page on how to use/integrate with the LexEVS API.
  

Decision Points:

• Scott was wondering if Gilberto was interested in the graph db in Stardog.
• Gilberto suggested that the graph db and the triple store are the same.  It's just a matter of they refer to it.
  

Decision Points:

Discussion Points:

•  We will migrate lexgrid.org to github.  This will be seamless to the end user.
• We will work on this over the next sprint.

Decision Points:

Discussion Points:

• There is a user in China (part of the ISO meeting next week) that is interested in using LexEVS.None

Decision Points:

Mayo Team

• Cory -
  
  • April 28
• Scott
  
  • April 28 - May 3
• Craig -

NCI

• Tracy
• Rob
• Kim