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
Brem, Larry  NIH/NCI [C]  x
Pan, JJ
NIH/NCI [E] 
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
72ScottAdd release date to Release notes when appropriate   open
79Corycomplete security requirements   done
100ScottCheck into source code, namespace application for code queries, javadoc availability for tree extension etc   on hold
106CraigConfirm and arrange meeting time for MedDRA review   open
117GilbertoCheck on the status of the Java 1.7 requirement   open

118

ScottDraw up a list of changes to documentation and entry points   done
119GilbertoCheck on the use of NIH ListServe for forum activity   open
120SherryCheck with Ann Wiley about the policy for forums   open
121ScottCheck windows version of Tomcat for Kim   open
122ScottInvestigate Loader server permissions issue   open
123ScottFinish Landing Pages   open
124CraigCoordinate meeting with Harold possibly Kevin around the implementation of value sets in the context of the VSMC   open
125ScottUpdate JSON documentation to indicate preliminary implementation of JSON standard present in 6.1 CTS2 Service for Lexevs   open
126Sherry, GilbertoLook into HUBzero forum for LexEVS issues   open

Progress

Contract Extension UpdateSome interest in exploring the issue of providing help around the next 6.2? deployment.  Scott to check windows tomcat version for Kim.  
6.1 QA and Deployment (Tin, Jason, Scott)Status: Done except firewall exception.  Suggested a possible install of the local runtime on dataqa to do smoketest on indexes.  Scott to talk to Jacob about better permissions for the loader machine.  Are we ready to announce LexEVS 6.1?  Need to do get landing pages finished first – scott.  Scott to check with Craig on this issue.  DataQA is still progressing  
DataQA inclusion in PTE's   
Priorities for the Extension (Scott, Craig)

JSON documentation to be updated to indicate this is a preliminary standard.  -scott.  Can we move this up the tiers early.  Possible if some guarantee of finalization JSON standard. 

Need to define our VSMC implementation around the CST2 Value Set Implementations.  Need to draw in Harold in others and define this more completely.  Craig to coordinate.

Need to set up a grid of nodes to test.  Sharing value sets may be the number one priority around VSMC or similar.  Terminologies may be another use case for this.  FDA Structured Product Labeling is a use case.  VSMC deployment location needs to be priority with Mayo taking the lead. 

Update the project plan

JIRA Item prioritization

https://tracker.nci.nih.gov/issues/?jql=project%20%3D%20LEXEVS%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC

https://tracker.nci.nih.gov/issues/?jql=project%20%3D%20LEXEVS%20AND%20status%20%3D%20%22On%20Hold%22%20ORDER%20BY%20priority%20DESC

Discuss possible early face to face technical planning meeting and or late deployment support.

  • Technical Planning
  • Current Deployment
  • Future Deployment Planning

 

  
Forums and user support (Gilberto and Sherry)List serve would require one of the NIH staff to be owner, and Mayo staff can be an owner.  HubZero is another likely place and forums are easy to set up.  Use case is a public site. Gilberto and Sherry to look at HubZero.   
Code coverage reports and QA JUnit documentation  (Tracy)   

 

 

 

JIRA Issues

Description
LEXEVS-570 - Getting issue details... STATUS
LEXEVS-572 - Getting issue details... STATUS
LEXEVS-573 - Getting issue details... STATUS
LEXEVS-574 - Getting issue details... STATUS
LEXEVS-576 - Getting issue details... STATUS
LEXEVS-579 - Getting issue details... STATUS
LEXEVS-583 - Getting issue details... STATUS
LEXEVS-584 - Getting issue details... STATUS
LEXEVS-585 - Getting issue details... STATUS
LEXEVS-586 - Getting issue details... STATUS
LEXEVS-587 - Getting issue details... STATUS
LEXEVS-588 - Getting issue details... STATUS
LEXEVS-589 - Getting issue details... STATUS
LEXEVS-592 - Getting issue details... STATUS
LEXEVS-593 - Getting issue details... STATUS
LEXEVS-594 - Getting issue details... STATUS
LEXEVS-595 - Getting issue details... STATUS
LEXEVS-596 - Getting issue details... STATUS
LEXEVS-597 - Getting issue details... STATUS
LEXEVS-598 - Getting issue details... STATUS
LEXEVS-599 - Getting issue details... STATUS
LEXEVS-600 - Getting issue details... STATUS
LEXEVS-601 - Getting issue details... STATUS
LEXEVS-602 - Getting issue details... STATUS
LEXEVS-603 - Getting issue details... STATUS
LEXEVS-604 - 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

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