NIH | National Cancer Institute | NCI Wiki  


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

De Coronado, Sherri    


Safran, Tracy

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

Kuntipuram, Kumar



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
185GilbertoCreate Jira for OWL 2 Annotation issue in the API.2014.05.28  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
237ScottFinal code deliverables posted to SFTP site and wiki pages updated.2014.10.02  done
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  open
245Kim/NCIConfirm that the manifest and Tree Jar that Scott put on sftp will work. 2014.12.10  done
246CoryInvestigate if possible to use Apache as a proxy for NodeJS (if an issue with security appscan)2014.12.10  

on hold

253ScottLexEVS 6.2 sftp site to be updated with 6.2 related Jars2015.01.07  


254Tracy/RobEVS download page to be updated for 6.2.2015.01.07  


255ScottLexEVS 6.2 download page to be updated to point to the sftp site.2015.01.07  done
256GilbertoComplete OWL 2 review by Wednesday, January 142015.01.07  done
257ScottMeet with Gilberto to discuss OWL 2 duplicate relationships.2015.01.07  done
259Scott/Cory/KevinVerify that all distributed interfaces that are exposed are surfaced.2015.01.14  open
260CraigUpdate 6.3 plan to remove deployment tasks.2015.01.21  open
261CoryInstall Node.js on informatics and host the 6.2 CTS2 API documentation on Informatics.2015.01.21  open


Immediate Priorities and Problems (Mayo Team)


  • Backwards compatibility issue LEXEVS-689
    • Tree related. Kim and Scott identified a code path that hasn't been previously discovered.
  • OWL Updates
    • Discussion below.
    • Gilberto and Scott had a duplicate discussion - more details below.
  • Lucene planning
    • Continued planning, trying to develop a roadmap and way of managing the project.


  • JIRA Agile Configuration.
    • 6.4 planning - adding agile related activities.
  • Waiting for AppScan Results for nodeJS
    • Waiting for results.
    • Tracy thought the results came through.
  • Lucene planning


  • Lucene Planning
  • GitHub release and development planning
  • JIRA-636

Craig: Project Plan for 6.3 and 6.4

  • Lucene planning.
  • 6.3 release.
  • Agile Configuration

6.3 release planning,  (Craig)

Confirm tagging and deploying to Dev

  • 2 development tasks remain to be completed and are expected to be complete by Jan 28.  
  • As discussed last week, 6.3 will not be an official release.  
  • 6.3 will be deployed on NCI Dev for continued 2.7 browser development.
  • All fixes in 6.3 will be officially deployed to Production in the 6.4 release.  
  • no timeline established for 2.7 browser. Once plan in place, then we can decide on deploying 6.3.
  • Craig to update plan and remove deployment tasks.

Deployment of Node.JS (so we can point to 6.2 services)

  • Can we have it available for 6.2 announcement? Getting it pushed up to Production will require quite a bit of time.
  • In the short-term, Cory will deploy on informatics and point to the 6.2 Production service.
Tree Evaluation – Feedback


Shady Grove Deployment

Questions about DNS naming conventions.

  • If there are changes, Mayo will need to know so we can update the release artifacts.
  • lexevsapi6 url was added (generic)
    • This is to remain valid across 6.2, 6.3, 6.4, etc
OWL2 Changes

Discussed the list of fixes (captured in spreadsheet) and those will be added to JIRA.

Gilberto and Larry discussed and there are additional things to be considered in the near term.

Would like to cover all the main features in the 6.3 timeframe. In the spreadsheet, the 5 (high priority) will be done first and continue down until 1. Scott and Gilberto will need to have further discussions. This effort will push out schedules (6.4).

Distributed Interfaces

Kim identified "Sorting the mapping table" as a problem. Mayo team to review.

NCI team would point the term browser to the remote API to see if anything is broke.

Deployment Automation

It was discussed that we should not depend on anthill pro. Scott suggests that automation be for individual services (not one for all). There are some projects at NCI that uses Jenkins.

In house deployment - lengthy process, often doesn't go quite right. If we could automate, then more frequent updates to make things available. Warren has been pushing this moving forward.

Mayo team to discuss - when would it make sense to tackle this and start planning.


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