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
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian (NIH/NCI) [C] 
Wong, Joanne   

Kuntipuram, Kumar

Liu, Sichen x


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
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

254Tracy/RobEVS download page to be updated for 6.2.2015.01.07  


259Scott/Cory/KevinVerify that all distributed interfaces that are exposed are surfaced.2015.01.14  done
260CraigUpdate 6.3 plan to remove deployment tasks.2015.01.21  done
261CoryInstall Node.js on informatics and host the 6.2 CTS2 API documentation on Informatics.2015.01.21  open
262Mayo TeamDiscuss Automated Testing/Deployment strategy2015.01.28  open
263CraigWork with Larry to set up meeting for Automated Testing/Deployment strategy2015.01.28  open
264RobUpdate download links once code on NCIP Channel2015.01.28  


265CoryRespond to APPSCAN issues for CTS2 API documentation on Protege server.2015.01.28  open
266CoryUpdate the CTS2 API page to include location of hosted documentation (only show IP address) and call out the CTS2 API URL.2015.01.28  open


Meeting Debrief

It was discussed that automated testing of the distributed API on a client would be good for LexEVS.

  • could be done using a cron job to run a script to test the API.
  • ensure it gets run when there is a new load of content/updated new software.
  • Provide a list of tests that could be run (Scott), so that can be included in the larger plan. Will schedule a meeting to discuss.

Currently, Mayo uses Jenkins, Travis and Maven based builds.


Immediate Priorities and Problems (Mayo Team)


  • Backwards compatibility issue LEXEVS-689
    • Tree updates
    • OWL loader issues LEXEVS-721 - will work on this this week.
  • OWL2 Updates - Scott is going to have Kevin help with these fixes.
  • Lucene planning
    • Prototype discussion
  • NCIP github support
    • Gilberto and Scott have been working on trying to get 6.2 deliverables to the NCIP channel.
    • Scott to look at lexevs service to make sure it is complete. (Scott and Gilberto to discuss at 3:00EST)
    • All download links to be pointed to the NCIP channel. Rob/Tracy and Scott will do this.


  • API Documentation install prep
    • Installed on informatics.
    • Updated the CTS2 wiki pages.
    • Need to make changes to file permissions and then request another appscan.
  • Agile configuration


  • Lucene Planning - coaching the team as we prepare the Lucene work.
  • Prototype discussion with Scott.

Craig: Project Plan for 6.3 and 6.4

  • Lucene planning with team.
  • 6.3 release - updates to project plan and documentation.
  • Agile Configuration - working with Cory and Kevin to prepare JIRA for an Agile project.

6.3 release planning,  (Craig)

Will not pursue new containers up the tiers. Once we know when we want to deploy, we will then start that process.

For now we will deploy the 6.3 deliverables to DEV to allow the browser team to continue development.

Tree Evaluation – Feedback

Identified an OWL issue (JIRA 721).

When a namespace is provided for tree resolution, you currently do not get the full resolution. Need to decide if this is correct behavior or do we need to provide a fix. Will be fixed as suggested by Gilberto.

Doc API demo

It was suggested that the API doc page could include:

  • Hosting information (Mayo)


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