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

Kuntipuram, Kumar

 

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
293JasonCheck into Mayo being designated a trusted site2015.06.03  done

Progress

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

Agenda

Sprint Status

Current Sprint - Sprint 16 (October 29, 2015 – November 11, 2015)

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

We reviewed the backlog and discussed how to enter exit criteria for a story/bug.  This will help everyone understand when issues can be considered done.

We also mentioned that we will be grooming the backlog weekly, moving stories to the top based on priority.

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

 

LEXEVS-1296 - lbGUI cleanup script fails when no metadata is present. 

We should consider working on this issue in the next sprint as well as add exit criteria to the issue.

 


Issue Grooming

Prioritize JIRA issues (fix version 6.4)

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

 

Review decision regarding the single jar vs. a zip file

Re: Consideration of Build Impacts

We all agreed upon the proposed solution in the above link.

TODO: Mayo to create a JIRA item to capture the solution issue.

VPN and network evaluation

Craig was able to re-start this discussion between NCI and Mayo IT.  Both sides of IT are exchanging information to continue the discussion.

It was also mentioned that eventually, Mayo will need access to the NCI continuous server.

Face-Face Planning

There is a wiki link for agenda topics: LexEVS 6.3 and 6.4 Technical Face-To-Face Meetings

TODO: Mayo will add the following Face to Face topics to our list:

  • Continuous server discussion
    • How Mayo implemented their CI server and what NCI's plan is for their own server.
  • Add browser/LexEVS performance to the list of topics.
  • Loaders - how to create one from scratch.  Create a simple example of a loader.
  • End user approach to LexEVS
    • Tutorial on how to query the LexEVS API
    • Review of existing LexEVS documentation.
  • REST - CTS2 REST vs additional (extensions) REST calls like bulk download.
    • Discuss a REST Framework that includes CTS2 and other calls (extensions).

We requested NCI to fill in any addition notes/priorities on the list of proposed topics.  This will help Mayo prepare for the meeting.

LEXEVS- 970

  • OWL2  - prioritize this work

Scott suggested that we create a new story to capture the next set of OWL2 changes.

We discussed the possibility of creating an "epic" for all of the OWL2 issues/features.

TODO: Mayo to create JIRA items for the known OWL2 issues today and then close LEXEVS-970. 

Continuous IntegrationGilberto stated that he was interested in the continuous integration process on Mayo's servers.  He would be interested in a CI server on NCI's side.
November LexEVS Meetings11/11 and 11/25 meetings will be cancelled for this month.

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