|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
Provide example code to assist us with the understanding of the handling of value sets as coding schemes. This understanding will assist in our development of a Value Set Entity Search (GF#32794) which is part of the Term Browser 2.3 scope.
Provide a convenience method for resolving value sets from a resolved concept reference.
|6/19/13||6/25/13||10/26/13||Kim received the example code as part of the new release of LexEVS 6.1 to DEV.|
|Operations||Loading resolved value sets to test the performance to make sure additional work is not needed for the resolving value set performance.||6/19/13||6/21/13||Received a batch loader but the operations team needs to create a script before loading. Should be done by the end of this week.|
|Area of Interest||Details|
|LexEVS 6.1||Received a new tag of the API on Monday (7/15). Mayo is still working on a few issues with the new search extension. Having some issues with searching on multiple terms in the exact search functionality. Mayo is looking into the issue.|
|Term Browser 2.3 Release|
The new search extension method returns an iterator containing both named and anonymous classes. The Mayo team will modify the API to allow the user to optionally include or exclude anonymous classes. In the meantime, the browser code has been modified to make name and code of a matched anonymous class non-clickable.
|Term Browser 2.3 Release||Entered a DRT ticket to start the AppScan on DEV. The ticket is currently on hold until we can get the issue above figured out.|
|GF#32793||Extend the advanced search capabilities|
|GF#32746||Provide access to NCBO Bioportal ontology visualization widget|
Project Plan Changes
|GF#32816||Migrate to LexEVS API 6.1.||6/28/2013||1 Developer||We are still reviewing the new deployment of LexEVS 6.1 on DEV. This date is dependent on the value sets issues describe previously.|
|Moving up Development Time||7/17/2013||We are pushing to get the coding done for a July 17th review by the EVS users. This will give the users a chance to provide input on the implementation before we completely freeze the code.|
|Pushing back the start of the user evaluation||7/22/2013||Having an issue with the exact match search. Working with mayo to get it resolved but need it fixed before user can review.|
|Area of Interest||Details|
|Term Browser 2.3 Release||Complete AppScan and work through any potential vulnerabilities.|
|Term Browser 2.3 Release||Start the user evaluation of the new/changed functionality and make and required changes/fixes.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|6/19/13||9/30/13||Term Browser 2.3 and LexEVS 6.1 are in parallel development with the Term Browser having a dependency on LexEVS release. Both have a hard deployment date of 9/30/2013. Anticipating some QA resource limitations with both schedules being in parallel.||M||Jason||Monitoring both schedules and will provide status to QA to make sure resources are available.|
|7/17/2013||Removal of JAVA 1.6 from desktops. The Term Browser deployments using AntHillPro require JAVA 1.6. Putting in a request for a waiver until we can upgrade.|
|Term Browser 2.3 release dependent on the LexEVS 6.1 release. Mayo team says that they will start deployment through the tiers the second week in July pending any additional work needed on the Value Set resolution performance. Operations team is loading the value sets into DEV through next week and we can then evaluate the performance.|