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
Pan, JJ
Tran, Tin    NIH/NCI [C]  
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
136ScottPoint the CTS2 API page to PROD (wiki) - originally planned on Stage, but now planning on PROD.   done

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



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

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




Include the value set and namespace tacks back into plan (in case we do have time or extension)

2014.04.30  open

Jason to send note to Michael and Jacob (include Scott) to understand what the work around is for Struts

2014.04.30  open
159Tracy/Scott Tracy/Scott to provide example  for UMLS problem and send that on to Alameda team. 2014.04.30  open
160ScottScott to submit feature request to expand value set definitions (requires a model change).2014.04.30  


161CoryAdd service information to include links (rest calls).2014.04.30  open

Talk with Kevin about NCBO and what is exposed via value set client. 

2014.04.30  done

Jason has dependencies so Craig to work with Jason on plans and will update and send out to the group.

2014.04.30  open
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  open


Immediate Priorities and Problems (Mayo Team)


MySQL 5.5 update, max clause count error on phrase, Lucene cleanup failure, failure of value sets to resolve on informatics

  • MySQL 5.5 upgrade - moving to linux environment to test in.  Following up on JUnit failures.
  • Max Clause issue on a phrase.  Searching on separate characters in a phrase.  Further research is needed.
  • Resolved VS issue on informatics - tracking down.


Cory:  CTS2 Client UI

  • NLM testing - authentication to be resolved ASAP.
  • Tested on FF, IE, Safari, and Chrome
  • Added URL in Service Profile
  • NLM authentication bugs are largely fixed except for the service info.
  • Added browsers supported on About page.

Craig: Project Plan Updates

  • Closing out UI VS work and CTS2 1.1
  • Working on MySQL and Java upgrades
  • Meeting with Systems
  • ARC meeting this Friday - 11:00 AM
  • Look at the Browser plan - Craig to contact Jason to take care of.



Struts update
  • No classes dependent on the CookieInterceptor class. Waiting for further direction from the Security Team.  JJ to forward the note from the Security team.
caDSR and Value Set and other URIs (Weekly Status)

Term browser and other API places URI's are adhoc.  Discussion continuing with caDSR.  What is the format and requirements.  A couple of choices – domain either NCI or Purl.  What follows would be /valueset/<Identifier>   Identifier would be from the NCIt.  Suggested using a concept in the conceptual entities domain that would describe the value set.  This could support concepts in other terminologies such as those supported for the NDFRT.  It would be good to get these changed before the adhoc version get to be used.

UMLS Mapping FilesTracy tried to load and still has it failing.  Scott to check environments and try another load – so far he's not had any failures.  
ARC Meeting

Consistent environments for all tiers discussed. Government sponsors for different silos of responsibility could be a problem for coordinating resources for the fall deployment.

  • Scheduled for Friday.
  • Dev and QA are VMs - Would be nice to have actual servers.
  • Attendees should be:Scott, Craig, Tracy, Jason, QA team, Larry
Value Set URI proposalSee above  
Project Plan and JIRA Item management around additional requests.

Priority of how these responses are handled discussed. 

  • Prod issues should be highest priority.
  • Possibly enter issues in JIRA to track (not in email)




JIRA Issues

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

 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