NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (stanclcr2), last modified on May 06, 2015

 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
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayo 
Wynne, Robert    NIH/NCIx
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian (NIH/NCI) [C]x
Wong, Joanne   

Kuntipuram, Kumar

 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  on hold
281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold
288GilbertoFollow up on the possibility of obtaining a license for the JIRA Capacity plugin (project portfolio management plugin)2015.04.08  done

Progress

  
Scott
  • Sprint 4
Cory
  • Sprint 4
Craig
  • Sprint 4
  • Agile Admin

Agenda

Sprint Status

Current Sprint – Sprint 4 (April 22, 2015 – May 12, 2015)

LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint4


Sprint Planning

Issue Grooming

  • Prioritize JIRA issues

Key Summary T Created Reporter P Status Labels
Refresh

Patch release naming conventions (6.3 vs 6.2.1)
  • Agreed to use 6.3 as release identifier. 
  • Next time, we should better evaluate what naming should be (point release/other release).
  • Scott created an overview of what is included in 6.3.  Larry and others to share with Preston.
Tree Extension Code Merge to LexEVS repository discussion (Update) - Browser Support - 6.2/6.3, etc.

LEXEVS-889 - Getting issue details... STATUS

  • Package naming were changed for Tree Extension when factored into LexEVS.
  • It was the understanding that this change would be in parallel with the next release of browser. 
  • 2.6 browser (in production) to test the 6.3 tree extension.
  • 6.3 anticipated to be released prior to the 2.7 browser.
  • Scott to further investigate.
     
OWL2 Discussion

LEXEVS-852 - Getting issue details... STATUS

  • Scott to create new JARS  for Rob to test latest changes from Cory.
Mapping Extension Discussion
  • During loads - noticed that loads were causing problems.  Was able to fix with manifest.  Not all inclusive, but this seems to be the problem. 
  • Rob to further test.  Scott to send information to Rob.

External End-user support (SNOMED loader issues)

Discussed previously. 

No further action required by Mayo team.  Comment to users to use NCI version. 

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Key Summary T Created Reporter P Status Affected Version/s Fix Version/s
Refresh

Recent CTS2 Service Related Issues (within last week)

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

6.4 LexEVS Related Issues

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

6.4 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
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