De Coronado, Sherri
|Ong, Kim L ||IS||x|
|Lucas, Jason R ||IS|
|Wynne, Robert||NIH/NCI [C]||x|
|Tran, Tin||NIH/NCI [C]||x|
|Carlsen, Brian||NIH/NCI [C]||x|
|Wong, Joanne||NIH/NCI [C]|
|Assigned||Description||Date Identified||Due Date||Date Completed||Status|
LEXEVS-1516 - Getting issue details... STATUS
Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)
|Craig||Create JIRA issue to remove caCore legacy code||2016.04.20||2016.04.30||Open|
|Cory||Update wiki to describe what DBs are supported/tested going forward||2016.04.27||2016.04.30||Open|
Set up an ARC meeting for LexEVS 6.4
Current Sprint - Sprint 33 (June 23, 2016 – July 6, 2016)LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint33
Dev - RC.1
This deployment will be done through the PTE and Anthill Pro process.
TODO: Mayo team needs to set up an ARC meeting for LexEVS 6.4.
NCI team will run user acceptance tests (from Tin) against the LexEVS API. NCI doesn't need any additional resources from the Mayo team at this time.
After LexEVS is deployed, Tin will update the URLs from his test suite to hit the DEV deployment and test his scripts.
NCI will test LexEVS 6.3 and LexEVS 6.4 side by side to make sure they both work together.
Planning for QA deployment and beyond
|This deployment will be done through the PTE and Anthill Pro process.|
OWL2 Loaders - planned time with Gilberto
We have time set up for the next several Fridays (Gilberto, Rob, Tracy, Scott, Deepak, and Cory) to review OWL2 loader changes.
There are several other cardinality use cases that are not in scope for this issue. They will need to be addressed.
These issues will be discussed at the meeting set up during the next several Fridays.
We will also need to discuss how OWL fits into LexEVS in the future.
HL7 Loader issue - create issue for the flipped internal code and entity code.
|The internal code and the entity code were reversed during the HL7 MIF load. These will need to be swapped to fix the issue.|
LexEVS External Users
The javadocs are working as designed.
When the javadocs are created, the filename convention is to be lowercase. Any camel case filenames will therefore break.
One possible solution is to create a specialized doclet to create camel case file names/paths.
A couple other possible work arounds may be to do the following:
|Rob noted that getIsPreffered() on the presentation is returning null for Thesaurus|
The return type is a Boolean type, which can return a null.
If the property name is the preferred name, Rob thought it would use that property.
Tracy suggested that the Thesaurus should have a preferred name.
Rob will create a JIRA issue for this.
|The Mayo team will investigate this issue next sprint.|
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|