NIH | National Cancer Institute | NCI Wiki  


Please be advised that NCI Wiki will be will be undergoing maintenance on Monday, June 24th between 1000 ET and 1100 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.


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

De Coronado, Sherri    


Safran, Tracy

Ong, Kim L
Lucas, Jason R
Bauer, Scott  Mayox
Stancl, Craig
Endle,  CoryMayox
Wynne, Robert    NIH/NCI 
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian (NIH/NCI) [C] 
Wong, Joanne   

Kuntipuram, Kumar

Liu, Sichen  


Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  open
246CoryInvestigate if possible to use Apache as a proxy for NodeJS (if an issue with security appscan)2014.12.10  

on hold

264RobUpdate download links once code on NCIP Channel2015.01.28  


266CraigSet up Lucene Search Review2015.02.18  


281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  open
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  open
283CraigDiscuss what it means to deploy 6.3 to PROD at our next meeting (4/8/2015).2015.03.25  open
284Craig/CoryCreate the Architecture document for the CTS2 API service.2015.04.01  open
285ScottCreate a new JIRA item to capture issue investigate for LEXEVS-8282015.04.01  open
286ScottCreate a JIRA issue for the issue Kim found with the tree extension (path to root and namespace).2015.04.01  open


  • Sprint 2 - design and documentation
  • Support - JIRA 828

  • Sprint 2 - design and documentation
  • Agile Setup in JIRA
  • Agile




TODO: Craig/Cory to get Arc. document template and fill out.

Jason to set up a meeting after an Arc. document is done.

Currently deployed at

6.3 Deployment

Browser may need 6.3 features sooner than 6.4 would be deployed.

We will discuss further next week when everyone is present.

Lucene and Agile process

Currently on Sprint 2.

Reviewed the agile sprint 2 board with the group.

The project roadmap is available here:

Scott has investigated this mapping extension issue.

Junit that is failing addresses this problem that the iterator is working properly.

TODO: Scott to create a new JIRA item to capture this issue and what the fix could  be.  This is a 6.3 issue.

Mayo Security initiative - binary code review (similar to Jenkins)

Mayo has a toolset to scan code for security concerns.  It may be possible to run LexEVS binaries through our security scan.

This is a static analyzer for the binary code.  The dynamic analyzer is available to hit the end REST services.

Mayo team will meet with the security team to start this process.

Tree extension issue (Kim)

Trying to find the path to root. 

Namespace was the same, the NPO boundary was brought in.

TODO: Scott to create  a JIRA issue and place in the backlog.


JIRA Issues

Recent LexEVS Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.3 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.3 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation

 Planned Activities

Area of InterestDetails

Risks, Issues, Dependencies


Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy


 #Opened DateDescriptionImpactAssignedStatus


Opened DateDescriptionAssigned





  • No labels