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
Mayo 
Endle,  CoryMayo 
Wynne, Robert    NIH/NCIx
Pan, JJ
NIH/NCI [E]x
Tran, Tin    NIH/NCI [C] x
Ahmed, Shamim
NIH/NC [C]  
Haber, Margaret (NIH/NCI) 
Roth, Laura (NIH/NLM)  
Ramani, Vivek (NIH/NCI) [C]  
Carlsen, Brian (NIH/NCI) [C] 
Wong, Joanne  x

Kuntipuram, Kumar

 x

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
156Scott

Scott to work with Gilberto to determine what is needed for OWL 2 requirements

2014.04.30  

on hold

164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
170ScottUpdate the ARC dates to include range of dates for each tier.2014.05.14  on hold
185GilbertoCreate Jira for OWL 2 Annotation issue in the API.2014.05.28  open
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  open
204LarryPlan for August NLM Demo/Meeting.2014.07.09  open

Progress

Immediate Priorities and Problems (Mayo Team)

Scott:  Loader testing against, Working on JIRA #598

  • Jira 598 - fix complete.

Cory:  Working JIRA #'s 531, 371

Craig: Project Plan Updates.

 

 

 

 

caDSR and Value Set and other URIs (Weekly Status)Production now reflects updated URI's  Need to know if URI resolver is case sensitive (Scott).  URL's are not by definition case sensitive.  In general you cannot say you can use either.  Proposal:  Should go to all lower case.   
Dev DRT request
  • Ssh is now being implemented on Shady Grove dev. 

  • Dev and QA to be combined via new Agile approach.

  • QA and developer sit together to develop the test. 

  • Once done on Dev, QA is done. 

  • Perhaps sprint testing will be done on Dev. 

  • This will save data migration. 

  • Potential for conflict  with data and application testing taking place on the same server. 

  • Need to have a plan as to how we will test to potentially take to Systems.

  • Requirements for testing should be different thanks to better resources. 

  • Two data base instances might be a good way to manage things. 

  • How will we manage documentation of this?  N

  • eed to have a streamlined test plan/process. 

  • JIRA agile may be a good place for this. 

  • Other applications are currently trying to create such documentation and may create a standard template for this.  We can define exit and entrance values for Dev to QA even though they are on the same tier.  Need to create a checklist.

  
Plans for the future of caCORE webservices.Perhaps leave this in for this iteration.  
Discussion of JIRA #597CTS2 Association Graph:  Proposed as a CTS2 Specification implementation.  Will leave this to be further discussed next week.  

 

 

 

JIRA Issues

Description
LEXEVS-570 - Getting issue details... STATUS
LEXEVS-573 - Getting issue details... STATUS
LEXEVS-579 - Getting issue details... STATUS
LEXEVS-586 - Getting issue details... STATUS
LEXEVS-594 - Getting issue details... STATUS
LEXEVS-597 - Getting issue details... STATUS
LEXEVS-598 - Getting issue details... STATUS
LEXEVS-599 - Getting issue details... STATUS
LEXEVS-605 - Getting issue details... STATUS
LEXEVS-606 - Getting issue details... STATUS
LEXEVS-607 - Getting issue details... STATUS
LEXEVS-608 - Getting issue details... STATUS
LEXEVS-609 - Getting issue details... STATUS
LEXEVS-612 - Getting issue details... STATUS
LEXEVS-613 - Getting issue details... STATUS
LEXEVS-615 - Getting issue details... STATUS
LEXEVS-616 - Getting issue details... STATUS
LEXEVS-617 - Getting issue details... STATUS
LEXEVS-618 - Getting issue details... STATUS
LEXEVS-619 - Getting issue details... STATUS
LEXEVS-620 - Getting issue details... STATUS
LEXEVS-621 - Getting issue details... STATUS
LEXEVS-622 - Getting issue details... STATUS
LEXEVS-623 - Getting issue details... STATUS
LEXEVSCTS2-2 - Getting issue details... STATUS
LEXEVSCTS2-3 - Getting issue details... STATUS

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