LexEVS 6.5.1 Release Highlights Include:
Note: This release includes all LexEVS 6.5.0 changes.
Features of this Release
Efficient Value Set Resolution using Source Asserted Value Sets
- 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.
Detection of Value Set Updates
- An additional API that detects value set updates has also been made available. This represents an additional efficiency for value set loading.
Representation of Value Set Hierarchy
- 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.
Fully Dynamic Source Asserted Value Set Resolution
- Source asserted value set API can fully resolve directly against the source coding scheme.
Source Asserted Value Set Search
- New search API implemented against Value Sets
LexEVS Services Support for Source Asserted Value Sets
- LexEVS Distributed API and LexEVS REST services updated to fully support Source Asserted Value Sets
Enhanced Loaders
- Continued enhancement of existing LexEVS Loaders
- Notably, expanded OWL2 and RRF support for MED-RT
Issues Fixed in this Release
- Numerous fixes were included.
LexEVS 6.5.1 - Features Implemented (43)
| Feature | Summary | Type |
|---|---|---|
| LEXEVS-3509 | I would like to add a value set to the VS hierarchy implementation from an outside source | Improvement |
| LEXEVS-3694 | Change the coding scheme name in ResolvedConceptReference returned by both search and resolution API. | Improvement |
| LEXEVS-3781 | Increase memory on LoadMetaBatch script | Improvement |
| LEXEVS-3640 | Place value set nodes in value set hierarchy using contributing source. | New Feature |
| LEXEVS-3406 | I would like to have a value set service that runs directly against the NCIt | New Feature |
| LEXEVS-3524 | Allow VS Hiearchy to be resolved from Source Asserted VS API | New Feature |
| LEXEVS-3475 | Write controller/business logic layer for Source Asserted VS API | New Feature |
| LEXEVS-3476 | Implement Source Asserted Value Set API | New Feature |
| LEXEVS-3540 | Implement Resolved Value Set Style API for Asserted Value Sets | New Feature |
| LEXEVS-3545 | Update the Resolved Value Set API to include access to Asserted Value Sets | New Feature |
| LEXEVS-3565 | Update and Verify Asserted Value Set Service API for Remote API | New Feature |
| LEXEVS-3564 | Update and Verify Asserted Value Set Search Service for Remote API | New Feature |
| LEXEVS-3639 | Change the URI in ResolvedConceptReference returned by Value Set Search and Resolution methods. | New Feature |
| LEXEVS-3642 | Support search against a specific value set or any collection of value sets. | New Feature |
| LEXEVS-3301 | I would like LexEVSTreeItem attributes to be made public or publicly accessible | New Feature |
| LEXEVS-2961 | VS Workflow: Remove Dependency on value set definition files for NCIt defined Value Sets | New Feature |
| LEXEVS-2962 | VS Workflow: Generate all NCIt sourced resolved value set coding schemes from NCIt source in LexEVS | New Feature |
| LEXEVS-3058 | Value Set: Value Set Hierarchy will be defined from that in the NCIt and returned in a performant manner | New Feature |
| LEXEVS-2967 | Value Set - (Browser) Efficient search by code or name - query for value set that this concept matches | New Feature |
| LEXEVS-2966 | Value Set - (Browser) Efficient retrieval VS definition metadata resolution calls. Faster queries against the definitions themselves. | New Feature |
| LEXEVS-3170 | Provide ability to add Non-NCIt value sets to asserted vs hierarchy | New Feature |
| LEXEVS-3057 | Value Set - Definition for LexEVS Value Set Definition Asserted Source Task | New Feature |
| LEXEVS-3074 | Value Set: Create User Defined property name parameter for Concept Domain | New Feature |
| LEXEVS-3063 | Implement Value Set Tree Integration for Browser API | New Feature |
| LEXEVS-3165 | Implement simpler approach to resolving a list of all value sets | New Feature |
| LEXEVS-3203 | Value Set - Update Resolved Value Set Query Mechanism for Optimized Search | New Feature |
| LEXEVS-3220 | Determine if a NCIt Asserted Value Set has changed | New Feature |
| LEXEVS-3494 | Follow up code cleanup test expansion for Asserted Value Set Indexing | New Feature |
| LEXEVS-3474 | I would like an index access layer to be written for the source asserted value set search | New Feature |
| LEXEVS-3339 | Modularize the full system test to allow individual modules to be run | New Feature |
| LEXEVS-3473 | I would like an Index creation layer to be written for Source Asserted Value Sets | New Feature |
| LEXEVS-3477 | Create Full Unit test suite for the API | New Feature |
| LEXEVS-3547 | Create and support a value set iterator that pages from the data base | New Feature |
| LEXEVS-3603 | Iterators for Assserted Value Sets need to be adjusted for RMI | New Feature |
| LEXEVS-3617 | Update AssertedValueSet Search Extension to work with RMI | New Feature |
| LEXEVS-3518 | I would like to include external value sets in NCIt asserted value set index | New Feature |
| LEXEVS-3517 | I would like to include Neoplasm Tree value set entities in asserted VS index | New Feature |
| LEXEVS-3135 | Default page for lexevsapi6 needs to be updated | Improvement |
| LEXEVS-3749 | Update lexgrid.org to be local | Improvement |
| LEXEVS-3789 | Services don't start up when asserted value sets are not present. | Improvement |
| LEXEVS-3587 | Update Lexevs value set loader to work for CTS2 in memory tests | Improvement |
| LEXEVS-3655 | Update to support CTS2 asserted resolved value set read | Improvement |
| LEXEVS-3739 | Add ability to determine if Asserted Value Sets exist before requesting them | Improvement |
LexEVS 6.5.1 - Defects Fixed (29)
Defect | Summary | Type |
|---|---|---|
| LEXEVS-3755 | LoadUmlsBatch fails to load MED-RT | Bug |
| LEXEVS-3748 | Unable to retrieve correct namespace of target entities in a mapping coding scheme. | Bug |
| LEXEVS-3741 | Core.xsd has a typo in the value set namespace declaration | Bug |
| LEXEVS-3137 | Contains type search breaks on special characters. | Bug |
| LEXEVS-3221 | Duplicate value sets accessing the same index will fail any queries against either scheme | Bug |
| LEXEVS-3067 | Value Set: Thread management for resolved value set loads | Bug |
| LEXEVS-3071 | Value Set Publishing Value Needs to be used to determine VS Loads | Bug |
| LEXEVS-3092 | Hierarchy Source adjustment in LEXEVS-1300 fix creates an unsupported association | Bug |
| LEXEVS-3101 | Code clean up including refactoring, additional testing, any minor issues | Bug |
| LEXEVS-3121 | Value Set (Browser) Create initial index for coding schemes (resolved value sets) | Bug |
| LEXEVS-3277 | Providing support for failing iterator paging on tree service extension | Bug |
| LEXEVS-3299 | OWL2 Loader -- ChEBI load runs out of memory | Bug |
| LEXEVS-2712 | MappingExtension.getMappingCodingSchemesEntityParticipatesIn failure. | Bug |
| LEXEVS-3305 | Loader - Value Set -- SourceAssertedResolvedValueSetLoad overwrites indexes with same name | Bug |
| LEXEVS-3341 | NCIt History Load fails silently and throws other extraneous errors | Bug |
| LEXEVS-3376 | ValueSetDefinition getEntityDescription().getContent() method does not return description. | Bug |
| LEXEVS-3377 | Value sets with a Publish_Value_Set property set to ‘No’ are being loaded as definitions. | Bug |
| LEXEVS-3386 | Replace the value of _code (currently, header concept code) by the (source asserted) value set URI. | Bug |
| LEXEVS-3387 | In the source view value set tree returned by getFullServiceValueSetTree, sort nodes by value set names. | Bug |
| LEXEVS-3388 | In 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-3385 | Populate _ns attribute in LexEVSTreeItem with proper namespace | Bug |
| LEXEVS-2183 | Tree Extension: TreeService API returns JSON String containing anonymous nodes. | Bug |
| LEXEVS-3510 | I would like to Implement a service layer for the asserted value set search mechanism | Bug |
| LEXEVS-3681 | Serialization Error against the RMI of Resolved Value Set iterator | Bug |
| LEXEVS-3689 | AssertedValueset iterator cannot advance over paged next call | Bug |
| LEXEVS-3733 | Search Iterator Regression failure on Source Coding Scheme Name | Bug |
| LEXEVS-3779 | Orphaned Asserted VS Entity Service is not needed | Bug |
| LEXEVS-3783 | OWL2Loader manifest causes failed update in asserted value set index | Bug |
| LEXEVS-3830 | Target Namespace in mapping iterator ResolveConceptRefence incorrect | Bug |
LexEVS Remote API 6.5.1 - Features Implemented (10)
| Feature | Summary | Type |
|---|---|---|
| LEXEVSREM-149 | Updating Codebase to allow Full Value Set Hierarchy Use | Improvement |
| LEXEVSREM-147 | Updating API to provide high performance resolution of value sets | Improvement |
| LEXEVSREM-148 | Create/Improve/Configure for Distributed Complete set of Resolved Value Set Tests | Improvement |
| LEXEVSREM-153 | Updating Tests and Configuration to support LEXEVS-3221 | Improvement |
| LEXEVSREM-145 | Support for Value Set Hierarchy in LexEVS Remote API | New Feature |
| LEXEVSREM-169 | I would like to have Source Asserted Values in Resolved VS work in RMI | New Feature |
| LEXEVSREM-179 | Unit testing and any adapatations for RMI Asserted VS Search | New Feature |
| LEXEVSREM-213 | Expand Iterator Tests for Asserted Value Sets | New Feature |
| LEXEVSREM-178 | Remote Service Requires updates to LexEVS source and tests | Improvement |
| LEXEVSREM-198 | Fix remote API tests not running | New Feature |
LexEVS Remote API 6.5.1 - Defects Fixed (5)
| Defect | Summary | Type |
|---|---|---|
| LEXEVSREM-60 | Tree Extension: TreeExtension ChildTreeNodeIterator method throws exceptions. | Bug |
| LEXEVSREM-146 | Test jars from LexEVS need to be updated to reflect current tests. | Bug |
| LEXEVSREM-194 | Update Tests for Distributed Service For Asserted VS Search | Bug |
| LEXEVSREM-228 | Search on uri for value set fails | Bug |
| LEXEVSREM-232 | Distributed Tests need updates to accommodate new Hierarchy features | Bug |
LexEVS Remote Client 6.5.1 - Features Implemented
| Feature | Summary |
|---|---|
LexEVS Remote Client 6.5.1 - Defects Fixed
| Defect | Summary |
|---|---|
LexEVS CTS2 Service 1.6.1 - Features Implemented (13)
| Feature | Summary | Type |
|---|---|---|
| LEXEVSCTS2-200 | CTS2 Service: Test/Update service with no access to lexgrid.org | New Feature |
| LEXEVSCTS2-156 | Remove dependcies that are no longer used/needed. | Improvement |
| LEXEVSCTS2-251 | Update service to work with asserted value set changes | New Feature |
| LEXEVSCTS2-164 | Remove references to remote API in the POM and code | Improvement |
| LEXEVSCTS2-191 | Upgrade Apache Commons Collections to v3.2.2 | Improvement |
| LEXEVSCTS2-205 | Update lexevs-service with latest 6.5.1 jar and fix existing issues | Improvement |
| LEXEVSCTS2-224 | Adjust in Memory load to include load of Asserted Value Set Scheme | New Feature |
| LEXEVSCTS2-216 | Adjust Loader for test to include Asserted Value Set Index Load | New Feature |
| LEXEVSCTS2-228 | Update CTS2 Framework version of maven-surefire-plugin | Improvement |
| LEXEVSCTS2-217 | Update CTS2 for asserted resolved value set read inclusion | New Feature |
| LEXEVSCTS2-235 | Update URLs of WSDLs from http to https | Improvement |
| LEXEVSCTS2-236 | Update test and version of lexevs | New Feature |
| LEXEVSCTS2-243 | Update to support CTS2 framework version with local XSDS | Improvement |
LexEVS CTS2 Service 1.6.1 - Defects Fixed
| Defect | Summary |
|---|---|
LexEVS CTS2 Framework 1.4.0 - Features Implemented (3)
| Feature | Summary | Type |
|---|---|---|
| CTS2FW-78 | Update URLs of WSDLs from http to https | Improvement |
| CTS2FW-36 | CTS2 Framework: Remove Soap Implementation and testing from this Fork | Improvement |
| CTS2FW-74 | Update XSD references and code to be local | Improvement |
LexEVS CTS2 Framework 1.4.0 - Defects Fixed
| Defect | Summary |
|---|---|
URI Resolver 1.1.0 - Features Implemented
| Feature | Summary |
|---|---|
URI Resolver 1.1.0 - Defects Fixed
| Defect | Summary |
|---|---|
