Page History
...
New features in this release focus on updates of the value set loading system. Since the source of value sets it is the NCI Thesaurus (NCIt), and since the NCIt contains logical, computable assertions about what value sets are in it’s 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.
...
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 it’s 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.
...
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 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.
...
Defect | Summary |
---|---|
MappingExtension.getMappingCodingSchemesEntityParticipatesIn failure. | |
LEXEVS-3376 | ValueSetDefinition getEntityDescription().getContent() method does not return description. |
LEXEVS-3377 | Value sets with a Publish_Value_Set property set to ‘No’ are being loaded as definitions. |
LEXEVS-3067 | Value Set: Thread management for resolved value set loads |
LEXEVS-3071 | Value Set Publishing Value Needs to be used to determine VS Loads |
LEXEVS-3092 | Hierarchy Source adjustment in LEXEVS-1300 fix creates an unsupported association |
LEXEVS-3121 | Value Set (Browser) Create initial index for coding schemes (resolved value sets) |
LEXEVS-3137 | Contains type search breaks on special characters. |
LEXEVS-3221 | Duplicate value sets accessing the same index will fail any queries against either scheme |
LEXEVS-3277 | Providing support for failing iterator paging on tree service extension |
LEXEVS-3341 | NCIt History Load fails silently and throws other extraneous errors |
LEXEVS-3385 | Populate _ns attribute in LexEVSTreeItem with proper namespace |
LEXEVS-3386 | Replace the value of _code (currently, header concept code) by the (source asserted) value set URI. |
LEXEVS-3387 | In the source view value set tree returned by getFullServiceValueSetTree, sort nodes by value set names. |
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. |
LEXEVS-3463 | Move Marker for LexEVS issues Kept as Unit tests |
LEXEVS-3470 | Move Marker for LexEVS issues Kept as Unit tests for 6.5 branch |
LEXEVS-3305 | Loader - Value Set -- SourceAssertedResolvedValueSetLoad overwrites indexes with same name |
Features not yet done
LEXEVS-3473 | I would like an Index creation layer to be written for Source Asserted Value Sets |
LEXEVS-3474 | I would like an index access layer to be written for the source asserted value set search |
LEXEVS-3475 | Write controller/business logic layer for Source Asserted VS API |
LEXEVS-3476 | Implement Source Asserted Value Set API |
LEXEVS-3477 | Create Full Unit test suite for the API |
...