NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

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.

 Attendees

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

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

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

Kuntipuram, Kumar

  
Ahmed, Shamim(NIH/NCI) [C]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
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  

open

266CraigSet up Lucene Search Review2015.02.18  

open

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  done
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  done
286ScottCreate a JIRA issue for the issue Kim found with the tree extension (path to root and namespace).2015.04.01  done
287ScottDetermine estimates for  tree extension, mapping extension, and OWL2  fixes to be considered for 6.3.2015.04.08  open
288GilbertoFollow up on the possibility of obtaining a license for the JIRA Capacity plugin (project portfolio management plugin)2015.04.08  open

Progress

  
Scott
  • Sprint 2 - design and documentation
  • Support

Cory
  • Sprint 2 - design and documentation
Craig
  • Agile

 

Agenda

6.3 Deployment Discussion

Determine a timeline for a 6.3 production deployment.

Would like 6.3 for the fixed search component (default active flag behavior)

Need to determine if tree extension and mapping extension fixes needs to be in 6.3.  (These fixes could be pushed up separately).  These fixes would be for 2.7 browser.

  • LexEVS-829
  • LexEVS-850
  • LexEVS-851
  • LexEVS-852

Two options are:

  • Wait until these issues are fixed and do one 6.3 build.
  • Push 6.3 now and fix the above issues and then push fixes later as a separate tree extension jar.

Also need to determine if these new OWL issues can be fixed and integrated into 6.3

  • LexEVS-853
  • LexEVS-854
  • LexEVS-855

TODO: Discuss with Scott the effort to fix the above issues.

Sprint Status

Review Sprint 2 (complete)

Sprint Planning

Sprint 3 Overview

Support Process:

Issue Grooming

  • Prioritize JIRA issues

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

JIRA Plugin

Capacity Planning for the Mayo team within JIRA Agile tooling.

TODO: Gilberto will follow up to see what our options are for obtaining this plugin

LexEVS 851 Tree ExtensionPrioritize and schedule

 

JIRA Issues

Recent LexEVS Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.4 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

6.4 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
 None     
       
       

 Planned Activities

Area of InterestDetails
  
  
  

Risks, Issues, Dependencies

Risks

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

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

 

 

 

  • No labels