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
Sharma, Deepak
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.   open
72ScottAdd release date to Release notes when appropriate   open
79Corycomplete security requirements   open
89DeepakInvestigate resumebatch – where and how does it pick up threads after failed loads   in progress
100ScottCheck into source code, namespace application for code queries, javadoc availability for tree extension etc   on hold
101RobRecheck the load time issue for NCIt in one month (On next release of the NCIt)   done
106CraigConfirm and arrange meeting time for MedDRA review   open
112TracySend Scott the out of memory errors on startup   done
113ScottCreate JIRA Item for resumeBatch   done
114ScottWrap up release artifacts   done
115ScottAdd the log notes for URI failover for the URI Resolver to the PTE   done
116JasonContact Jacob about sorting out the URI Resolver issues with the database connections   done
117Craig/Larry W.Start creating the agenda for the face to face meeting   done


6.1 QA and Deployment (Tin, Jason)Nessus Scan came up with a couple of issues.  JBoss server is the issue – a waiver has been submitted.  CTS2 REST service on stage may be down.
Face to Face plans (Craig)Review of Agenda.  Draft Agenda – Issues to talk through.  Need enough focus without too much constraint.  CTS2 seen as a harmonization and integration tool  – pressures to broaden that.  CTS2 need not be the central focus at the start.  Introduction CTS2 designed to meet need, inputs taken, CTS2 participants and issues.  Issues later possibly.  NCBO needs to be able to be a part of the discussion when he is only able to be attend a short period of time.  LexEVS to be included in the terminology background.  Apelon tool might be discussed as well.  Should we focus on issues and objectives around interoperability and shared resources.  Suggesting an Analytical approach to evaluating.  Larry to tweak the agenda around this.  Technical discussion should focus on a technical details if possible.  How do we start to use resources LexEVS or others including NCBO and others.  caDSR folks to attend with the idea of getting to the more detailed information on use.  Global text search in java for James Tan might be of use/interest. Graph database and hierarchical retrieval.  Looking at distribution of services if NCBO has more efficient ways of achieving things.  Prefer a general discussion based on what issues have remained current over the years. Could we come up with Pilots for use of CTS2.
Widget progress (Scott)Update.  Ready for deployment, and arrangements for that on the Mayo side are nearly complete.
Multiple Namespace reportCTS2 rest call has no namespace.   Multiple namespaces exist for some sets of codes.   JIRA #597  Status: This is implemented and works as expected in the CTS2 service.  We need to fix issues on Dev so Kim can use these.
6.1 Documentation overviewstatus.  See JIRA issue 599.  New forums and remove the links for old forums.  LexEVS needs to have a forum as well.  Mayo to discuss.
Thoughts on the release process and announcement

Two stage, browsers first, then the cts2 after production with some documentation adjustments as necessary. EVS announcements and ListServes including NCIP list serve.  Or the NCIP page. 

NCI Loader issueNCI may run some post processing scripts to verify loads.  lexbigdataqa is the application.
caGrid update investigationJIRA issue 600
MetaLoader – if time allowsResumebatch to be adjusted to try to fix more failures if practical.  Informative output still on the table and may provide feedback as to where the batch load is failing. 




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

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation

 Planned Activities

Area of InterestDetails
List of Issues, adjustmentsLoaders and smaller issues
Continue work on widgets 

Risks, Issues, Dependencies


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


 #Opened DateDescriptionImpactAssignedStatus


Opened DateDescriptionAssigned





  • No labels