NIH | National Cancer Institute | NCI Wiki  


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

De Coronado, Sherri    


Safran, Tracy

Ong, Kim L
Lucas, Jason R
Bauer, Scott  Mayox
Stancl, Craig
Endle,  CoryMayox
Wynne, Robert    NIH/NCIx
Brem, Larry  NIH/NCI [C]   
Pan, JJ
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



Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
134ScottCreate a JIRA item to track the need to remove Struts   done
135JJFollow up on security scan to find out what kind found the Struts issue   open
136ScottPoint the CTS2 API page to Stage (wiki)   open
137ScottSet up a time to meet about Value Set Versions   done
138ScottTo note Grid Service retirement in 6 months   done
139KumarTo do an analysis of the Project plan for budgeting purposes.   open
140ScottUpdate struts jar to 2.3.16   


141JasonUpdate or Create a DRT to insure JSP page is not exposed on Production   open
142ScottUpdate the wiki page to point to the lexevs/lexevs issues   open
143ScottAsk Harold if he can stop into the next LexEVS meeting breifly   done
144ScottCreate an issue around the forward slash in search extension   open
145ScottScott to look at the indexes on DATA QA   open


Immediate Priorities and Problems (Mayo Team)

Value Set Module -  There are some framework 1.1 updates that need to be folded into that. Resolved VS versioning work needs to be done.

CTS2 Client UI  - (Cory) search implemented.  Worked on paging, ran into some issues

Tech Stack Notes

Going to Java 1.8.

  • Java 1.8 won't be available until May (JJ). 
  • If we require LexEVS instance to be stood up before May we will need to use Java 1.8 on our workstations. 
  • Date/time API will need to change for Java 1.8.  Can't put Java 1.8 on DEV until Systems has it there in May? (Gilberto).  
  • We can develop on our own workstations on Java 1.8.
  • Gilberto suggesting doing a straight migration to Java 1.8 until it is more stable.  (don't use new APIs of 1.8).
  • 1.7 will be deprecated a year after 1.8 comes out.
Continuing Development through next fiscal year (Larry)Some discussion.  Feeling was that it's important to do the tech stack updates to get to new hardware. VS work for CDISC/FDA - is that part of LexEVS api? can we get that done in this period.  CTS2 VS versions could be done later.
Needs continued discussion.  Particularly about the Value Sets.  Need some guidance on the use of RDF formatted output.
Kumar - going to do an analysis of the plan for budgeting and will get back to us.
Struts Security Update (Jason)


(Jason) Nessus scan passed.  Bruce Woodcock said that scan isn't the best indicator of Struts vulnerability.  
Struts vulnerability may have been discovered by some other tools?
Scott tested by pulling out a jars.  More testing needs to be done to determine the affects of removing the jar and involved JSP pages.
Downloaded latest Struts jar and it built cleanly.  Would like to deploy locally and test further.
Larry/Tracy agreed this would be a quick test and should try the testing.
Scott will proceed with testing the new jar.

6.1 DeploymentLexEVS 6.1 went live!
Visible externally.
PTE is wrong.  CTS2 Service is wrong. LexEVS service appears good.
Value Sets are not resolving beyond the lists.  Can't follow up on hrefs in return calls.
Need to look at the Tomcat logs on PROD.
LexEVS API - can get to the JSP page.  Should this be a hidden page?
Jason/Jacob to fix the DRT
HubZero or GitHub for forum (Jason)Preference was for GitHub.  This is the decision
To make it on lexevs/lexevs - put link to this (Scott)
Retiring Grid ServicesThe note on this is done – further reinforced by the retiring of the grid services we are running on version 1.x  
caDSR and Value SetsAre there rest services that caDSR should be using?    
Will they use the same URIs that are provided on browser?  
Harold suggested using resolvable URI that CTS2 could use.
Current URI are not resolvable.
Currently using the URI that defines the value set.
Need to assume that we will publish the URIs in the future, so they should be resolvable.
NCI is communicating this with caDSR (Gilberto)
Possibly get Harold for this meeting next week.  Scott to see if he's available.
Discuss consolidated vs separate indexes  for max clause count issue. Some searches against presentation would break
Some searches again properties would work
NCI Thesaurus - 
Search Extension - Global
Properties - working against a Code System.
Kim suggested to modify the analyzer - Scott doesn't think this is the problem.
Scott doesn't think this is an easy fix
Scott suggested 2 ways to search against the presentation
provide global search too.
Max clause can be raised pretty high  (Larry)
One option would be to break the indexes up.  
Summary: May be able to reconfigure the Max clause count. Increase to a higher number and see if it works.
Discuss search issues around forward slash / in contains searchScott to look into the search extension further.  May need to work with Kevin.
Scott to put this into a JIRA item and work on it.
Mapping Index issuesEditors are reporting issues during the mapping. - said some indexes were missing.
Scott to look at the indexes on DATA QA




JIRA Issues

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

 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


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


 #Opened DateDescriptionImpactAssignedStatus


Opened DateDescriptionAssigned





  • No labels