NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (bauerhs), last modified by Unknown User (stanclcr2) on Aug 06, 2014

 Attendees

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

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI   x
Ong, Kim L
IS 
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
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   

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. (now Sept)2014.07.09  done
205ScottSee if URI's are case sensitive as handled by the URI resolvers2014.07.16  done
206ScottDetermine if CTS2 supports a distinction between transitive derived relationships and structural graphs2014.07.23  

done

207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  open
208CraigNLM Technical team discussion - report back at next meeting. 2014.07.30  open
209Craig/LarryPlan Techical F2F/AMIA meetings.2014.07.30  

open

210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  open
211Gilberto/ScottDocument Jira 597 and create additional Jira (597 - transitive closure and new one for graphs)2014.07.30 642 created.done
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

open

213Kumar/JJConfirm QA and Dev tier decision.2014.08.06  open
       

Progress

Immediate Priorities and Problems (Mayo Team)

Scott:  DEV deployment, OWL

  • Focused on deployment on DEV  - build verifications on files (all moved to DEV)
  • Need MySQL Password (Scott to get from Tracy)
  • Mayo hardware configured to use SSD.  Working on putting indexes on this drive. 
  • Some OWL loader/issues have been commented on by Scott and would like the team to review and comment.

Cory:  Working JIRA #'s 371, 599

  • Running/verifed on local system.  Going to deploy and test before marking complete. 
  • Will start 599.

Craig: Project Plan Updates, Contract updates.

  • Updated plan to have Scott work on the DEV deployment and OWL.
  • Contract - identified travel plans and will submit with cost proposal.  This included Lucene/SOLR conference.
 

 

 

caDSR and Value Set and other URIs (Weekly Status)

Tracy - no updates. 

  
Dev DRT requestContinuing DEV deployment.  Scott will report as things progress.   
Agile discussionStill waiting on NCI policy.  Mayo team to take Agile class in September.   
Preferences File - Synonyms (Tracy/Scott)Preferences file did work correctly for Tracy.  
LexGrid XML publishing (5.1)

It was planned last week to identify the retirement of this in the 5.1 retirement announcement to see if there are any existing users. 

No further work needs to be done until decision is made about retirement.

  
QA Process

Scott discussed the monolithic junit tests and now to reduce failures (caused mostly by timing issues).    Would like to be able to simplify and refactor some of the tests. 

Given the minimal amount of time needed to do the refactoring (1 day) - and the gains that can be made for QA, we will have Scott attempt to simplify and refactor the tests.  

Per, Tin, there will be a QA tier and Dev tier (original plan was to have a compressed DEV/QA).   (Scott will need to update the PTEs) – This will need to be clarified. 

  

 

 

 

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