Page History

Current Sprint - Sprint 19 ( December 10, 2015 – December 23, 2015 )

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

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Recent CTS2 Service Related Issues (within last week)

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

LexEVS 6.3 and 6.4 2015.12 Technical Face-To-Face Meetings

• Will keep the EVS time on Wednesday if need to include others (since already on their calendars). Need to look topics that we might want to cover during that time.
• It was suggested that for Wednesday: 1:00-1:30 for topics and then start the Loader tutorial
• Loader tutorial attendance - Tracy, Rob, possibly CA
• Kim requested to have topic on Indexes - "Indexing and Search" on Wednesday AM. This should cover search results for 6.4; Discuss how Qualifiers are indexed.
• Deployment and tech stack updates - would like to have Jacob and Yeon attend.
• Deployment topics to additionally include - deployment on cloud and triple store deployment.
• Add 4:00-5:00 for General overflow/additional topics
• API usage usecase
  • Gilberto suggested to discuss:
    • graphs - API call once per node to generate a "pretty" graph (CTS2)
    • API results returned
• End User Usage - API - to include caDSR (Sima or other?) should be included. Tracy to follow up with caDSR group to ensure this time slot will work for them. CTRP may be interested as well.
• Tutorial content to be shared on the wiki.

• TODO: Craig to update the wiki face to face page.
• TODO: Tracy to follow up with caDSR.

Prioritization List

We clarified the priorities for each piece of work to be done.  There is now a column to indicate what work will be done during the 6.4 timeframe.

Next steps - We will create JIRA issues for each work item in the list.

CTRP will get back to the EVS group when they have firm requirements.  It was suggested that Craig/Larry will follow up with Jose in about a month to see if we can assist them and understand their requirements.

Tracy brought up the "Path to Root issue" - This is part of the existing transitive closure issue captured in the F2F notes. If this was developed in CTS2 it would be to retrieve descendants and ancestors.  We should also consider how this will work if there are multiple different paths to root.  For example, the thesaurus has many nodes that have 10+ paths to root.  Sherri will send an example of this to the development team.

Tracy mentioned that "Lung Carcinoma" has several different paths to root.

Examples from Sherri of concepts with many paths to root.

• Colon Serrated Adenocarcinoma
• Colorectal Neuroendocrine Tumor G2
• Intracranial Cavernous Hemangioma
• Localized Non-Resectable Adult Hepatocellular Carcinoma

Other general comments were that the 3 day duration was a good time frame and it was also good to meet with other teams (CTRP and Systems).

LexEVS release 6.3.0.1

• Kumar - Patch release discussion
• NCIP git pull request for 6.3? 6.3.0.1?

• 6.3.0.1 is a patch release to provide fixes to the loaders and lbGUI (Admin level)
• No QA is needed.
• NCIP channel needs to updated with the 6.3.0.1
• Cory to work with Gilberto to create branch in NCIP and issue the pull request. 

OBI issue

Scott is trying to determine why the tree extension isn't working for certain cases.  If he cannot determine the error, he may need to work with the term browser team to see if the issue is there.

Jacob was able to open a port for debugging on the DEV system so Scott can do some debugging.

Scott helped a user on the forum to get LexEVS installed.  The user was looking at how to get the shortest path between two nodes.

Larry suggested that we request any additional information from the user (what they are using LexEVS for, etc) if they are willing to send this.

• It was determined there weren't any namespace issues associated to the LexEVS API.
• Rob found that in the term browser, the April 2015 OBI load did not have hierarchy. Scott discovered that the tree extension fails while running on the browser against OBI. He noted that the September 2015 OBI load did work correctly.
• If we continue to pursue this issue, we would need to determine if the tree extension breaks with the April 2015 OBI load.
• Gilberto noted that he is not comfortable with vocabulary version issues - as the versions shouldn't be different with regard to hierarchy.
• Scott suggested that we perform the load (April 2015 version) and debug to determine where the tree extension is encountering the issue.
• LEXEVS-1338 - Exit Criteria was confirmed by Gilberto - Scott to update the JIRA item exit criteria.

• VPN configured and tested.
• Scott and Cory to start using the connection and report back next week how well the connection is working.
• NCI to complete security process.