De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS|
|Wynne, Robert||NIH/NCI [C]|
|Tran, Tin||NIH/NCI [C]||x|
|Carlsen, Brian||NIH/NCI [C]|
|Wong, Joanne||NIH/NCI [C]|
|Assigned||Description||Date Identified||Due Date||Date Completed||Status|
LEXEVS-1516 - Getting issue details... STATUS
|Brian||For the RRF issue, come up with some examples to send out to the group to explore.||2016.03.02||2016.03.09||open|
Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)
|Scott||Scott will send an email to Larry and the Mayo team to introduce each other on the Biomarker project.||2016.03.09||2016.03.16||done|
Current Sprint - Sprint 25 (March 03, 2016 – March 16, 2016)
We identified a couple of issues while updating the remote api with the latest 6.4 lexevs jars. These issues will be worked on in sprint 26. The performance work will also be finished up in sprint 26.
Value set resolution issues at NCI
Scott has been doing some research with the term browser against the DEV.
When selecting the values, it is retrieving resolved coding schemes. Scott is getting values for Neoplasm from DEV. Scott was asking if the dynamic resolution is working for Kim.
There have been changes/updates to the Neoplasm value set over the months.
Based on discussions from the morning meeting, we agreed that we should try updating permissions/ownership on the cvd files.
Jacob was asking why the Neoplasm cvd file is owned by tomcatb (not tomcata)? If the file is "touched" by tomcatb, it shouldn't change the ownership.
We also discussed just having one owner - tomcata. We will want to test the permission changes mentioned above first.
We all agreed that Jacob will change ownership to tomcata and change the permissions to be consistent for all cvd files on DEV. During the meeting,
Kim will test after this meeting and follow up with his findings.
Scott asked if we can we go to resolved value sets for all use cases? The NCI team mentioned there was an issue with the versions. That was why we used the cvd files.
|Dev Ops Meeting||Gilberto scheduled this meeting for this Friday at 12:00 noon Eastern time.|
|LexEVS External Users||No updates|
Recent LexEVS Related Bugs and Features (within last week)
|Key||Summary||T||Created||Reporter||P||Status||Affected Version/s||Fix Version/s|
Recent CTS2 Service Related Issues (within last week)
6.4 LexEVS Related Issues
6.4 CTS2 Service Related Issues
Project Plan Changes
|Area of Interest||Details|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
Action Item Backlog
|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|64||Scott||To follow up on URI's on OWL2 with Harold.||on hold|
|164||Cory||Cory to add implementation to CTS2 implementations page.||2014.04.30||on hold|
|197||Scott||Do a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs||2014.6.18||on hold|
|200||Larry/Sherry||Query current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's||2014.6.18||on hold|
|207||Cory||Write issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.||2014.07.30||on hold|
|210||Larry/Gilberto||Determine if there is a need to meet with the CTRP||2014.07.30||on hold|
|212||Larry||Include LexGrid XML Export as part of the 5.1 retirement notice.||2014.07.30|
|224||Scott||URI Resolver - Provide overview of how to access the URI Resolver||2014.09.03|
|225||Scott||URI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver||2014.09.03||on hold|
|244||Craig||Plan meeting with Tracy to discuss collaborative LexEVS development process||2014.12.03||on hold|
|281||Scott||Try to replicate what CTRP did to break our service (retrieve a tree through CTS2).||2015.03.25||on hold|
|282||Mayo Team||Look into implementing graph node in CTS2 for the path to root method (and path to leaf).||2015.03.25||on hold|