NIH | National Cancer Institute | NCI Wiki  

 Attendees

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

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

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

Kuntipuram, Kumar

NIH/NCI [C]

x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
Craig/LarryFollow up with Jose (CTRP) in January 2016 to see if we can assist them and understand their requirements.2015.12.162016.01.31 Open

Progress

  
Scott
  • Sprint 19
  • On going Support
Cory
  • Sprint 19
  • On going Support
Craig
  • Sprint 19
  • Agile Admin

Agenda

Sprint Status

Current Sprint - Sprint 19 ( December 10, 2015 – December 23, 2015 )

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

Sprint Planning

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

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

 

Recent CTS2 Service Related Issues (within last week)

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

 


Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Key Summary T Created Reporter P Status Labels
Loading...
Refresh

 

Face-to-Face Recap

2015.12 Technical Face-To-Face Prioritization List

We clarified the priorities for each piece of work to be done.  There is now a column to indicate what work will be done during the 6.4 timeframe.

Next steps - We will create JIRA issues for each work item in the list.

CTRP will get back to the EVS group when they have firm requirements.  It was suggested that Craig/Larry will follow up with Jose in about a month to see if we can assist them and understand their requirements.

Tracy brought up the "Path to Root issue" - This is part of the existing transitive closure issue captured in the F2F notes. If this was developed in CTS2 it would be to retrieve descendants and ancestors.  We should also consider how this will work if there are multiple different paths to root.  For example, the thesaurus has many nodes that have 10+ paths to root.  Sherri will send an example of this to the development team.

Tracy mentioned that "Lung Carcinoma" has several different paths to root.

Examples from Sherri of concepts with many paths to root.

  • Colon Serrated Adenocarcinoma
  • Colorectal Neuroendocrine Tumor G2
  • Intracranial Cavernous Hemangioma
  • Localized Non-Resectable Adult Hepatocellular Carcinoma

Other general comments were that the 3 day duration was a good time frame and it was also good to meet with other teams (CTRP and Systems).

OBI issue

LEXEVS-1386 - Getting issue details... STATUS

Scott is trying to determine why the tree extension isn't working for certain cases.  If he cannot determine the error, he may need to work with the term browser team to see if the issue is there.

Jacob was able to open a port for debugging on the DEV system so Scott can do some debugging.

Holiday PlanningThe next two Wednesdays will be cancelled due to the holidays.
LexEVS External Users

Scott helped a user on the forum to get LexEVS installed.  The user was looking at how to get the shortest path between two nodes.

Larry suggested that we request any additional information from the user (what they are using LexEVS for, etc) if they are willing to send this.

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Key Summary T Created Reporter P Status Affected Version/s Fix Version/s
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
   
   

 

Action Item Backlog

 #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

 

 

 

  • No labels