LexEVS 6.5.1 (Not Released) Release Highlights Include:

Note: This release includes all LexEVS 6.5.0 changes.

Features of this Release

New features in this release focus on updates of the value set loading system.  Since the source of value sets is the NCI Thesaurus (NCIt), and since the NCIt contains logical, computable assertions about what value sets are in its system, business logic has moved towards direct access to the code system rather than external defining files.  This has been a collaborative effort with NCIt curators and has resulted in improved loading efficiency of value set definitions and resolved value set coding schemes. 
An additional API that detects value set updates has also been made available.  This represents an additional efficiency for value set loading.  
Other assertions made in the NCIt about the hierarchical style storage of value sets also now have an API as well.  This is specific to the NCIt source at this time.  
This release will also contain a prototype of a direct to source value set resolution and search service, based on the kind of assertions the NCIt makes about its value sets.  Terminologies that make similar assertions my also make use of this API.  It should make some earlier value set API’s obsolete while retaining the ability of users to define and load their own value sets.
Some value set querying mechanisms are better optimized based on additional methods that provide more tailored object contents for methods requiring a list of value sets without resolving other attributes that may slow performance.

Issues Fixed in this Release

Many issues were reported with the large amount of new code written around value set loading and access.  This includes fixes to resolving value set function as well as value set hierarchy functions.  This also contains fixes to long standing history load issues, some tree extension issues and simple search API problems.  We updated an outdated tracking policy artifact in this release as well — removing a couple of failing value sets that were placeholders for issues that should be resolved.  This allows continuous integration to be more accurate and precise without any expected failures that can be ignored.  

 

LexEVS 6.5.1 - Features Implemented

FeatureSummaryType
LEXEVS-3509I would like to add a value set to the VS hierarchy implementation from an outside sourceImprovement
LEXEVS-3694Change the coding scheme name in ResolvedConceptReference returned by both search and resolution API. Improvement
LEXEVS-3781Increase memory on LoadMetaBatch scriptImprovement
LEXEVS-3640Place value set nodes in value set hierarchy using contributing source.New Feature
LEXEVS-3406I would like to have a value set service that runs directly against the NCItNew Feature
LEXEVS-3524Allow VS Hiearchy to be resolved from Source Asserted VS APINew Feature
LEXEVS-3475Write controller/business logic layer for Source Asserted VS APINew Feature
LEXEVS-3476Implement Source Asserted Value Set APINew Feature
LEXEVS-3540Implement Resolved Value Set Style API for Asserted Value SetsNew Feature
LEXEVS-3545Update the Resolved Value Set API to include access to Asserted Value SetsNew Feature
LEXEVS-3565Update and Verify Asserted Value Set Service API for Remote APINew Feature
LEXEVS-3564Update and Verify Asserted Value Set Search Service for Remote APINew Feature
LEXEVS-3639Change the URI in ResolvedConceptReference returned by Value Set Search and Resolution methods.New Feature
LEXEVS-3642Support search against a specific value set or any collection of value sets.New Feature
LEXEVS-3301I would like LexEVSTreeItem attributes to be made public or publicly accessibleNew Feature
LEXEVS-2961VS Workflow: Remove Dependency on value set definition files for NCIt defined Value SetsNew Feature
LEXEVS-2962VS Workflow: Generate all NCIt sourced resolved value set coding schemes from NCIt source in LexEVSNew Feature
LEXEVS-3058Value Set: Value Set Hierarchy will be defined from that in the NCIt and returned in a performant mannerNew Feature
LEXEVS-2967Value Set - (Browser) Efficient search by code or name - query for value set that this concept matchesNew Feature
LEXEVS-2966Value Set - (Browser) Efficient retrieval VS definition metadata resolution calls. Faster queries against the definitions themselves.New Feature
LEXEVS-3170Provide ability to add Non-NCIt value sets to asserted vs hierarchyNew Feature
LEXEVS-3057Value Set - Definition for LexEVS Value Set Definition Asserted Source TaskNew Feature
LEXEVS-3074Value Set: Create User Defined property name parameter for Concept Domain New Feature
LEXEVS-3063Implement Value Set Tree Integration for Browser APINew Feature
LEXEVS-3165Implement simpler approach to resolving a list of all value setsNew Feature
LEXEVS-3203Value Set - Update Resolved Value Set Query Mechanism for Optimized SearchNew Feature
LEXEVS-3220Determine if a NCIt Asserted Value Set has changedNew Feature
LEXEVS-3494Follow up code cleanup test expansion for Asserted Value Set IndexingNew Feature
LEXEVS-3474I would like an index access layer to be written for the source asserted value set searchNew Feature
LEXEVS-3339Modularize the full system test to allow individual modules to be runNew Feature
LEXEVS-3473I would like an Index creation layer to be written for Source Asserted Value SetsNew Feature
LEXEVS-3477Create Full Unit test suite for the APINew Feature
LEXEVS-3547Create and support a value set iterator that pages from the data baseNew Feature
LEXEVS-3603Iterators for Assserted Value Sets need to be adjusted for RMINew Feature
LEXEVS-3617Update AssertedValueSet Search Extension to work with RMINew Feature
LEXEVS-3518I would like to include external value sets in NCIt asserted value set indexNew Feature
LEXEVS-3517I would like to include Neoplasm Tree value set entities in asserted VS indexNew Feature
LEXEVS-3135Default page for lexevsapi6 needs to be updatedImprovement
LEXEVS-3749Update lexgrid.org to be localImprovement
LEXEVS-3789Services don't start up when asserted value sets are not present.Improvement
LEXEVS-3587Update Lexevs value set loader to work for CTS2 in memory testsImprovement
LEXEVS-3655Update to support CTS2 asserted resolved value set read Improvement
LEXEVS-3739Add ability to determine if Asserted Value Sets exist before requesting themImprovement

LexEVS 6.5.1 - Defects Fixed

Defect
Summary
Type
LEXEVS-3755LoadUmlsBatch fails to load MED-RTBug
LEXEVS-3748Unable to retrieve correct namespace of target entities in a mapping coding scheme.Bug
LEXEVS-3741Core.xsd has a typo in the value set namespace declarationBug
LEXEVS-3137Contains type search breaks on special characters.Bug
LEXEVS-3221Duplicate value sets accessing the same index will fail any queries against either schemeBug
LEXEVS-3067Value Set: Thread management for resolved value set loadsBug
LEXEVS-3071Value Set Publishing Value Needs to be used to determine VS LoadsBug
LEXEVS-3092Hierarchy Source adjustment in LEXEVS-1300 fix creates an unsupported associationBug
LEXEVS-3101Code clean up including refactoring, additional testing, any minor issuesBug
LEXEVS-3121Value Set (Browser) Create initial index for coding schemes (resolved value sets)Bug
LEXEVS-3277Providing support for failing iterator paging on tree service extensionBug
LEXEVS-3299OWL2 Loader -- ChEBI load runs out of memoryBug
LEXEVS-2712MappingExtension.getMappingCodingSchemesEntityParticipatesIn failure.Bug
LEXEVS-3305Loader - Value Set -- SourceAssertedResolvedValueSetLoad overwrites indexes with same nameBug
LEXEVS-3341NCIt History Load fails silently and throws other extraneous errorsBug
LEXEVS-3376ValueSetDefinition getEntityDescription().getContent() method does not return description.Bug
LEXEVS-3377Value sets with a Publish_Value_Set property set to ‘No’ are being loaded as definitions. Bug
LEXEVS-3386Replace the value of _code (currently, header concept code) by the (source asserted) value set URI. Bug
LEXEVS-3387In the source view value set tree returned by getFullServiceValueSetTree, sort nodes by value set names.Bug
LEXEVS-3388In the terminology view of value set hierarchy returned by getSourceDefinedTree, place the NCIt node first, and then sort the rest of the root nodes by value set names.Bug
LEXEVS-3385Populate _ns attribute in LexEVSTreeItem with proper namespaceBug
LEXEVS-2183Tree Extension: TreeService API returns JSON String containing anonymous nodes.Bug
LEXEVS-3510I would like to Implement a service layer for the asserted value set search mechanismBug
LEXEVS-3681Serialization Error against the RMI of Resolved Value Set iteratorBug
LEXEVS-3689AssertedValueset iterator cannot advance over paged next callBug
LEXEVS-3733Search Iterator Regression failure on Source Coding Scheme NameBug
LEXEVS-3779Orphaned Asserted VS Entity Service is not needed Bug
LEXEVS-3783OWL2Loader manifest causes failed update in asserted value set indexBug
LEXEVS-3830Target Namespace in mapping iterator ResolveConceptRefence incorrectBug

LexEVS Remote API 6.5.1 - Features Implemented

FeatureSummary
LEXEVSREM-149Updating Codebase to allow Full Value Set Hierarchy Use
LEXEVSREM-147Updating API to provide high performance resolution of value sets
LEXEVSREM-148Create/Improve/Configure for Distributed Complete set of Resolved Value Set Tests
LEXEVSREM-153Updating Tests and Configuration to support LEXEVS-3221
LEXEVSREM-145Support for Value Set Hierarchy in LexEVS Remote API
LEXEVSREM-169I would like to have Source Asserted Values in Resolved VS work in RMI
LEXEVSREM-179Unit testing and any adapatations for RMI Asserted VS Search
LEXEVSREM-157Create LexEVS Remote Dev Snapshot
LEXEVSREM-213Expand Iterator Tests for Asserted Value Sets
LEXEVSREM-255Test backwards compatibility - 6.5 client to 6.5.1 remote api service
LEXEVSREM-178Remote Service Requires updates to LexEVS source and tests
LEXEVSREM-198Fix remote API tests not running
LEXEVSREM-245Test remote API with no access to lexgrid.org

LexEVS Remote API 6.5.1 - Defects Fixed

DefectSummary
LEXEVSREM-60Tree Extension: TreeExtension ChildTreeNodeIterator method throws exceptions.
LEXEVSREM-146Test jars from LexEVS need to be updated to reflect current tests.
LEXEVSREM-194Update Tests for Distributed Service For Asserted VS Search
LEXEVSREM-228Search on uri for value set fails
LEXEVSREM-232Distributed Tests need updates to accommodate new Hierarchy features

LexEVS Remote Client 6.5.1 - Features Implemented

FeatureSummary
  

LexEVS Remote Client 6.5.1 - Defects Fixed 

DefectSummary
  

LexEVS CTS2 Service 1.6.1 - Features Implemented 

FeatureSummary
LEXEVSCTS2-200CTS2 Service: Test/Update service with no access to lexgrid.org
LEXEVSCTS2-156Remove dependcies that are no longer used/needed.
LEXEVSCTS2-190Documentation Updates - Update CTS2 on-line documentation to point to 6.5.0 lexevs-service
LEXEVSCTS2-210Investigate what needs to be updated for resolved value set read
LEXEVSCTS2-251Update service to work with asserted value set changes
LEXEVSCTS2-242Update Asserted Value Set default version to the PRODUCTION tag
LEXEVSCTS2-164Remove references to remote API in the POM and code
LEXEVSCTS2-191Upgrade Apache Commons Collections to v3.2.2
LEXEVSCTS2-205Update lexevs-service with latest 6.5.1 jar and fix existing issues
LEXEVSCTS2-224Adjust in Memory load to include load of Asserted Value Set Scheme
LEXEVSCTS2-216Adjust Loader for test to include Asserted Value Set Index Load
LEXEVSCTS2-228Update CTS2 Framework version of maven-surefire-plugin 
LEXEVSCTS2-217Update CTS2 for asserted resolved value set read inclusion
LEXEVSCTS2-235Update URLs of WSDLs from http to https
LEXEVSCTS2-236Update test and version of lexevs
LEXEVSCTS2-243Update to support CTS2 framework version with local XSDS

LexEVS CTS2 Service 1.6.1 - Defects Fixed  

DefectSummary
  

LexEVS CTS2 Framework 1.4.0 - Features Implemented 

FeatureSummary
CTS2FW-78Update URLs of WSDLs from http to https
CTS2FW-36CTS2 Framework: Remove Soap Implementation and testing from this Fork
CTS2FW-74Update XSD references and code to be local

LexEVS CTS2 Framework 1.4.0 - Defects Fixed

DefectSummary
  

 

URI Resolver 1.1.0 - Features Implemented 

FeatureSummary
  

URI Resolver 1.1.0 - Defects Fixed  

DefectSummary