De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS||x|
|Tran, Tin||NIH/NCI [C]||x|
|Carlsen, Brian||(NIH/NCI) [C]|
|#||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||open|
|246||Cory||Investigate if possible to use Apache as a proxy for NodeJS (if an issue with security appscan)||2014.12.10|
|264||Rob||Update download links once code on NCIP Channel||2015.01.28|
|266||Craig||Set up Lucene Search Review||2015.02.18|
|271||Cory||Add note to 6.2 wiki to mention the change in behavior in 6.2 active not active.||2015.03.11||done|
|272||Scott/Cory||Review the RRF loader and determine what is hard-coded and needs to be tracked when changes are made. This is to be placed on the wiki||2015.03.11||done|
|274||Cory||Discuss with Gilberto the creation of a CTS2 Framework JIRA project.||2015.03.18||done|
|275||Cory||Create a JIRA issue for the JSON serializer issue - date format.||2015.03.18||done|
|276||Scott||Continue to investigate OWL2 differences on the DEV system at NCI. This is the last issue before finishing 6.3.||2015.03.18||done|
|277||Scott||Add SNOMED Load Documentation to the Project Meeting agenda for next week.||2015.03.18||done|
|278||Scott||Add the browser 2.7 scope/release (with respect to the LexEVS 6.3 release) to the Project Meeting agenda for next week.||2015.03.18||done|
|279||Tracy||Request sample code of how CTRP is calling the CTS2 services.||2015.03.18||done|
|280||Mayo Team||Look into FishEye for JIRA||2015.03.18||done|
|281||Scott||Try to replicate what CTRP did to break our service (retrieve a tree through CTS2).||2015.03.25||open|
|282||Mayo Team||Look into implementing graph node in CTS2 for the path to root method (and path to leaf).||2015.03.25||open|
|283||Craig||Discuss what it means to deploy 6.3 to PROD at our next meeting (4/1/2015).||2015.03.25||open|
|API Doc API|
Appscan complete. Passed. Can start pushing it up to PROD. Should start with DEV. Cory will work with NCI to get installed on DEV.
There have been no Arch. meeting for this. Cory/Craig to fill out architecture template and send to Jason.
|OWL2 Closure||All outsanding issues are resolved/noted. There is a plan to revisit known concerns at a later date.|
|6.3 Deployment||Tagged, branched and deployed to NCI DEV.|
Scott reviewed FishEye features. Links JIRA to Git. Installed at NCI.
Are we interested in adding this to our JIRA project? We are willing to try it out.
|CTRP - CTS2 Service Load Limits|
No new information. They stopped doing the multiple, parallel loads.
They are trying to retrieve a tree through CTS2.
TODO: Try to replicate what CTRP did to break our service.
TODO: Look into implementing graph node in CTS2 for the path to root method (and path to leaf).
|Lucene and Agile process|
Discussed the active/inactive search issue in 6.2 and was fixed in 6.3.
TODO: discuss what it means to deploy 6.3 to PROD at our next meeting (4/1/2015).
Recent LexEVS Related Issues (within last week)
Recent CTS2 Service Related Issues (within last week)
6.3 LexEVS Related Issues
6.3 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|