NIH | National Cancer Institute | NCI Wiki  


Please be advised that NCI Wiki will be will be undergoing maintenance on Monday, June 24th between 1000 ET and 1100 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.


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,  CoryMayo 
Wynne, Robert    NIH/NCIx
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   

Kuntipuram, Kumar



Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold

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  on hold

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


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  open
185GilbertoCreate Jira for OWL 2 Annotation issue in the API.2014.05.28  open
192ScottCapture issues with Agile we may have2014.6.11  done
192ScottInvestigate logging or monitoring capabilities of URL Resolver2014.6.11  open
193CraigSend out updated Project Plan2014.6.11  done
194Craig/ScottSend a list of Known Common Value Set Client issues to Larry2014.6.11  done
195CraigUpdate Project Plan with performance testing  tasks2014.6.11  open
196JasonTo discuss Agile fit and questions with counter part2014.6.18  open
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  open
198ScottLook into whether git or github can fork from a fork2014.6.18  open
199ScottAsk Ann Wiley to create a sticky for the VKC forum directing users to post to appropriate gitHub2014.6.18  open
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  open


Gforge retirementAll the documents from Gforge are now on an ftp site.   
NLM Update


Contacted Ivor.  He is interested in looking at the prototype.  They have the beginnings of an RDF model for MESH.  Both are suggested as topics for the fall session.  No current time frame sent. 

Immediate Priorities and Problems (Mayo Team)

Scott: Tomcat verification testing, Loader testing against 5.5, Responding to requests around REST API. 

Final Tomcat verification tasks are in progress.

Cory:  Out

Craig: Project Plan Updates,  Delays in the 6116 environment and Shady Grove will impact this.  Might be an extra month. 




Goals and performance document (Larry)

This performance will need to be included in the project plan - include creating performance profiles of 6.2 on DEV hardware on Shady Grove and then evaluate performance at that point and determine what else would need to be done.   Additional work would need to be prioritized against the currently planned tasks at that time.  Ongoing task and concerns however plans for this are tracked in the current version of the project plan.


Agile adoption Schedule

Discuss issues and plan for any training/adoption framework.  The plan is still to start the discussion.  What are good ways to approach this.  Questions from Scott will be presented to an Agile expert who will comment on our current and future processes. TODO Jason.


caDSR and Value Set and other URIs (Weekly Status)

Report on URI Resolver logging (Scott) Scott has done some preliminary work.  Requirements for the logging service:  

  • Who is using the service. 
  • What URI's are hitting the resolver. 
  • Can old URI's be dropped. 
  • Might see people using URI's we do not yet support and use those as a standard for upgrades. 
  • Figure out if we have to change marketing. 
  • Can logging tell us where requests are coming from and who is making them. 

TODO Scott to look into this further.

Dev DRT request

Update.  See above in project plans updates.


GitHub, build workflow

Not much to add from the email from Gilberto.  NCI is not allowed to go to external sites for builds.  There is a local mirror. There is a mechanism allows them to create this.  In the case of LexEVS we will  have our own channels. We will notify systems about this.  The URL's for these will be entered in the PTE and the external github will be noted to the systems team.  Builds to be done from the local repository.  When we are ready to do a push to PROD at that point the code needs to be update the code in the NCIP channel.  A pull request will need to be made to do this.  NCIP Channel will be locked down – no code changes.  Pull request only for changes.  We should make the request that we do not fork from NCIP but from lexevs.  TODO look into how or whether you can fork from a fork – Scott


Forum Links on GitHub (Scott)

Recently received a forum posting from the old VKC forum.  Realized the readme was linking users to the VKC forum.  We can fix the readme, but now that we need to modify the files and push to NCIP channel, we need to figure out how we would make the change and push to both channels.  We will hold off and hope we don't have a lot more visitors to our current forum.   TODO Ask Ann Wiley to look into creating a forum sticky to direct users to our current github.


Plans for the future of caCORE webservices.Come up with a plan to evaluate usage and whether to remove this based on these evaluations. TODO send out a note to ask if users are using any of the web services.   




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

Risks, Issues, Dependencies


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


 #Opened DateDescriptionImpactAssignedStatus


Opened DateDescriptionAssigned





  • No labels