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,  KevinMayox
Wynne, Robert    NIH/NCIx
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
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

261CoryInstall Node.js on informatics and host the 6.2 CTS2 API documentation on Informatics.2015.01.21  done
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  done


Immediate Priorities and Problems (Mayo Team)


  • Deploying 6.3 to DEV
  • Tree Updates - resolving issue with Kim
    • Posted files to sftp (lexbig jar and war) to be tested by Kim.
    • Can send client zip if necessary
    • NPO loader is loading correctly.
  • OWL discussions with Kevin.


    • Agile Planning
      • Configuring JIRA
      • Created all artifacts in JIRA
    • 6.3 and 6.4 documentation
      • Created structure and documents.
    • 6.2 announcement
      • Updates to documentation from Larry.
    • 6.2 documentation API
      • Updated to use a new public server.
      • Published URL is better.
      • Need to update permissions on the Protege server.
      • Heroku hosting site.


  • OWL2
    • Reviewing the spreadsheet from Gilberto.
    • 100+ issues in spreadsheet.
    • Need to write testcases to capture each related issue.
    • Time to be spent on testing and regression testing. 
    • There are some common issues, but not absolutely sure that is the case for all.


  • Agile
  • 6.3 docs
  • 6.4 docs
  • Closed 6.2 release
  • Cleaned up previous versions on Jira
Lucene Project Methodology
  • JIRA will be used to track all Agile artifacts.
    • Jira Versions - Phases of the project
    • Jira Epics - Describes a larger issue or feature to be implemented
    • Jia Issues - Stories which describe the issue or feature to be implemented
      • Jira Sub-Tasks - Tasks which represent the work to be completed
  • Sprints will be used to iteratively develop the stories. (1 to 2 week Sprints)
    • Will be focused on what is agreed upon in each Sprint Planning Meeting.
    • If a new issue or question comes up for the team, it will be put into the backlog (Jira item created) and will only be considered during the next Sprint planning meeting for inclusion in the next Sprint.   
    • Consulting time can be included in the Sprint, but will reduce the effort possible by the team.  
  • Scrum meeting flow:  
  • Retrospective and sprint planning day before sprint starts.   
    • Suggest Sprint starts on Wednesday
    • Sprint and Retrospective planning on Tuesday
    • Wednesday NCI meeting - Demo and Sprint overview OR Backlog Refinement
  • Project Roadmap and Agile Reports will be used to report progress.  
  • Cannot start Lucene work until 6.3 tasks are complete.


Tree Evaluation – FeedbackNothing to report (see above)
Doc API Update

Server configured and linked in the announcement.

6.3 Documentation

LexEVS Project Documents

  • Include a note on the 6.3 and 6.4 that 6.3 is an internal release only.


Installer requirements Discussion

Scott reviewed what is available for installers. The installer izpack is still most popular (based on review).

Another option is a configured VM that a user could use to get up and running quickly.

VM might not work for all. Would be good option for someone that need to quickly look at and evaluate. Not necessary lack of skills, but immediate need.

Need to wait - on demand from others. Minimally provide more build documentation.

CI DiscussionSee above.
Lucene Searches on special characters.Searching of special characters and it seemed that it was translated to ascii characters. There aren't existing tests for such characters, so not guaranteed to work today.


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