NIH | National Cancer Institute | NCI Wiki  

 Attendees

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

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,  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
154Larry

Provide an email update to NCBO, NLM, and Mayo with current activities and what has been built.

   

open

155KumarVerify that funds can be extended through Oct.2014.04.30  open
156Scott

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

2014.04.30  

open

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  open
171TracyDetermine what IE Version to be supported for the VS Client2014.05.14  done
173CraigAdd OWL2 Loader JIRA items to project plan in loader development section2014.05.21  

done

174ScottCreate Jira item for use of manifest in UMLS Loader.2014.05.21  done
175CraigEmail VS Client Issue prioritization to group for review.2014.05.21  done
176CoryUpdate UI header with suggested changes.2014.05.21  

open

177ScottFollow up with Tracy Troung about the Site Scape usage.2014.05.21  done
178LarrySend sorting related email from Kevin2014.05.21  done
179CoryCreate Jira regarding IE 11 usage within NCI2014.05.21  

done

180ScottProvide DEV tech stack requirements to Jason2014.05.28  

open

181JasonCreate DRT for DEV request2014.05.28  

open

182CraigSet out latest project plan2014.05.28  

open

183ScottSend Tracy the location of the scoring code in LexEVS2014.05.28  

open

184Scott6.1 Release notes update - include Jira #21 (value set name restriction)2014.05.28  open
185GilbertoCreate Jira for OWL 2 Annotation issue in the API.2014.05.28  open
186LarryDirect Clinical Trials DB users to Scott for CTS2 Services assistance.2014.05.28  open

Progress

Immediate Priorities and Problems (Mayo Team)

Scott:

MySQL 5.5 update

  • pre-CTS2 API authoring functionality causing locks
  • 5.5 has a metadata lock on tables (update and create)
  • The API uses
    • iBatis XML (for querying, etc)
    • DDL - script implementation (drop and create tables)  - currently used within LexEVS and the pre-CTS2 API.
  • The problem is when you create a code system and drop the code system (using the CTS2 API)
  • Scott needs to talk with Kevin to hope to get some insight on the DAO. 
  • This is not part of the distributed API.
  • Options:
    • Fix the locking use and continue to include CTS2 java API in 6.2.
    • Remove CTS2 Java API from 6.2 (no fix required)
  • Scott will continue to look at issue with Kevin to confirm this limited to the CTS2 Java API.

Cory:  CTS2 Client UI, Java 1.7

  • Java 1.7
    • Compiled in 1.7 and running Junits
    • Determining what are issues and what are simply timing issues.
    • Plan to run on Mayo Dev system - full integration testing.
  • Client UI
    • Version of IE - 11

Craig: Project Plan Updates

  • Added Struts Jira Item
  • Added OWL Loader Items.
  • Jason to create DRT for DEV request.  Scott to provide details to Jason.

 

 

 

 

caDSR and Value Set and other URIs (Weekly Status)
  • Denise and Sherri to get a demo set up in June – Harold to be included.
  • Tracy sent a list of sort extensions to caDSR.
  • Tracy sent note to Kevin about how "match to query" was implemented. 
    • If we can send Tracy the section of code, she can send that onto caDSR.

 

  
ARC
  • No updates.
  
Value Set Viewer Item prioritization

Jira #21 ( LEXEVSCTS2-21 - Getting issue details... STATUS ) - currently limits the use of the value set CTS2 1.1 based service.

   Need to determine if it needs to be fixed in LexEVS or only in CTS2 service.  TODO:  Scott

This limitation should be noted on current release notes:  TODO: Scott

LEXEVS-594 - Getting issue details... STATUS has been resolved.  Needs to be verified and marked as resolved.  

  
Value Set Resolution issue CTS2 JIRA #21See above.  
Review tasks for OWL2

LEXEVS-614 - Getting issue details... STATUS

LEXEVS-595 - Getting issue details... STATUS

LEXEVS-586 - Getting issue details... STATUS

LEXEVS-583 - Getting issue details... STATUS

One other one related to API (Gilberto to find/create a Jira).

Craig to include in plan as part of Jira items. 

  
Clinical Trials DBWants to look at the CTS2 REST services and would like assistance.   Larry to direct to Scott.  

 

 

 

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
VSMC definitionNeed a dialog defining module use around ResolvedValueSets
Update LexEVS CTS2 Service to CTS2 1.1Need deployment tests
Work on a variety of EVS JIRA PrioritiesScripting, convenience methods, tree extension namespace issues

Risks, Issues, Dependencies

Risks

# Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

 

 

 

  • No labels