 |
Page History
...
LexEVS 6.5.1 - Features Implemented
| Feature | Summary | ||
|---|---|---|---|
| LEXEVS-3380 | I would like updates in LexEVSTreeItem/AssertedHierarchy to reflect original tree/treeItem implementation | ||
| LEXEVS-3509 | I would like to add a value set to the VS hierarchy implementation from an outside source | ||
| LEXEVS-3694 | Change the coding scheme name in ResolvedConceptReference returned by both search and resolution API. | ||
| LEXEVS-3781 | Increase memory on LoadMetaBatch script | ||
| LEXEVS-3640 | Place value set nodes in value set hierarchy using contributing source. | ||
| LEXEVS-1732 | Value Set: Modify coding scheme name and version of ResolvedConceptReference returned from a resolved value set coding scheme. | ||
| LEXEVS-3406 | I would like to have a value set service that runs directly against the NCIt | ||
| LEXEVS-3524 | Allow VS Hiearchy to be resolved from Source Asserted VS API | ||
| LEXEVS-3475 | Write controller/business logic layer for Source Asserted VS API | ||
| LEXEVS-3476 | Implement Source Asserted Value Set API | ||
| LEXEVS-3540 | Implement Resolved Value Set Style API for Asserted Value Sets | ||
| LEXEVS-3545 | Update the Resolved Value Set API to include access to Asserted Value Sets | ||
| LEXEVS-3565 | Update and Verify Asserted Value Set Service API for Remote API | ||
| LEXEVS-3564 | Update and Verify Asserted Value Set Search Service for Remote API | ||
| LEXEVS-3639 | Change the URI in ResolvedConceptReference returned by Value Set Search and Resolution methods. | ||
| LEXEVS-3642 | Support search against a specific value set or any collection of value sets. | ||
| LEXEVS-3301 | I would like LexEVSTreeItem attributes to be made public or publicly accessible | ||
| LEXEVS-2961 | VS Workflow: Remove Dependency on value set definition files for NCIt defined Value Sets | ||
| LEXEVS-2962 | VS Workflow: Generate all NCIt sourced resolved value set coding schemes from NCIt source in LexEVS | ||
| LEXEVS-29663058Value Set - (Browser) Efficient retrieval VS definition metadata resolution calls. Faster queries against the definitions themselves. | Value Set: Value Set Hierarchy will be defined from that in the NCIt and returned in a performant manner | ||
| LEXEVS-2967 | Value Set - (Browser) Efficient search by code or name - query for value set that this concept matches | ||
| LEXEVS-2966 | Value Set - (Browser) Efficient retrieval VS definition metadata resolution calls. Faster queries against the definitions themselves. | ||
| LEXEVS-3170 | Provide ability to add Non-NCIt value sets to asserted vs hierarchy | ||
| LEXEVS-3057 | Value Set - Definition for LexEVS Value Set Definition Asserted Source Task | ||
| LEXEVS-30583074 | Value Set: Value Set Hierarchy will be defined from that in the NCIt and returned in a performant mannerCreate User Defined property name parameter for Concept Domain | ||
| LEXEVS-3063 | Implement Value Set Tree Integration for Browser APILEXEVS-3074 | Value Set: Create User Defined property name parameter for Concept Domain | |
| LEXEVS-3165 | Implement simpler approach to resolving a list of all value sets | LEXEVS-3170 | Provide ability to add Non-NCIt value sets to asserted vs hierarchy |
| LEXEVS-3203 | Value Set - Update Resolved Value Set Query Mechanism for Optimized Search | ||
| LEXEVS-3220 | Determine if a NCIt Asserted Value Set has changed | ||
| LEXEVS-3494 | Follow up code cleanup test expansion for Asserted Value Set Indexing | ||
| LEXEVS-34743301 | I would like LexEVSTreeItem attributes to be made public or publicly accessiblean index access layer to be written for the source asserted value set search | ||
| LEXEVS-3339 | Modularize the full system test to allow individual modules to be run | ||
| LEXEVS-3473LEXEVS-3406 | I would like an Index creation layer to be written for Source Asserted Value Sets | ||
| LEXEVS-3477 | Create Full Unit test suite for the API | ||
| LEXEVS-3547 | Create and support to have a value set service that runs directly against the NCIt |
LexEVS 6.5.1 - Defects Fixed
| iterator that pages from the data base | |
| LEXEVS-3603 | Iterators for Assserted Value Sets need to be adjusted for RMI |
| LEXEVS-3617 | Update AssertedValueSet Search Extension to work with RMI |
| LEXEVS-3518 | I would like to include external value sets in NCIt asserted value set index |
| LEXEVS-3517 | I would like to include Neoplasm Tree value set entities in asserted VS index |
| LEXEVS-3445 | Create prioritization list from F2F activities |
| LEXEVS-3413 | I would like to be able to load mapping schemes as stand alone entities |
| LEXEVS-3636 | Update links to the CTS2 on-line documentation to NCI's URL and remove external instance |
| LEXEVS-3146 | Investigate HistoryService getDescendants failure |
| LEXEVS-3135 | Default page for lexevsapi6 needs to be updated |
| LEXEVS-3189 | Code review and merge of high performance resolved value set |
| LEXEVS-3032 | Investigate options to pull from different Docker repositories |
| LEXEVS-3040 | Investigate LexEVS API for creating/updating entities |
| LEXEVS-3105 | Hierarchy design/Investigation |
| LEXEVS-3171 | Investigate options for returning value sets with a non-NCIt default coding scheme (e.g., NDF-RT) |
| LEXEVS-3278 | Investigate coding scheme name and versions for value sets |
| LEXEVS-3597 | Update LexEVS version to 6.5.1.SNAPSHOT.6 |
| LEXEVS-3703 | Expand Iterator Tests for Asserted Value Sets |
| LEXEVS-3786 | LEXEVS-3783 Code review/Test and Merge |
| LEXEVS-3749 | Update lexgrid.org to be local |
| LEXEVS-3789 | Services don't start up when asserted value sets are not present. |
| LEXEVS-3743 | Update Asserted Value Set default version to the PRODUCTION tag |
| LEXEVS-3223 | Create LexEVS Dev Snapshot |
| LEXEVS-2517 | Value Set Loader: Investigate ability to update as needed (not have to load all 700 at the same time). |
| LEXEVS-3338 | I would like to know what the performance values of running with and without compiled value sets |
| LEXEVS-3587 | Update Lexevs value set loader to work for CTS2 in memory tests |
| LEXEVS-3655 | Update to support CTS2 asserted resolved value set read |
| LEXEVS-3750 | Admin: Provide continued Product Maintenance Support (Sprint 82) |
| LEXEVS-3739 | Add ability to determine if Asserted Value Sets exist before requesting them |
| LEXEVS-3760 | Updated LexEVS Interface Javadoc |
LexEVS 6.5.1 - Defects Fixed
Defect | Summary |
|---|---|
| LEXEVS-3755 | LoadUmlsBatch fails to load MED-RT |
| LEXEVS-3748 | Unable to retrieve correct namespace of target entities in a mapping coding scheme. |
| LEXEVS-3741 | Core.xsd has a typo in the value set namespace declaration |
| LEXEVS-1029 | Build: Fix build and runtime dependencies on hosted LexGrid and other LexEVS schemas |
| 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 |
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-3101 | Code clean up including refactoring, additional testing, any minor issues |
| LEXEVS-3121 | Value Set (Browser) Create initial index for coding schemes (resolved value sets) |
| LEXEVS-31373277 | Providing support for failing iterator paging on tree service extension |
| LEXEVS-3299 | OWL2 Loader -- ChEBI load runs out of memory |
| LEXEVS-2712 | MappingExtension.getMappingCodingSchemesEntityParticipatesIn failureContains type search breaks on special characters. |
| LEXEVS-32213305 | Loader - Value Set -- SourceAssertedResolvedValueSetLoad overwrites indexes with same nameDuplicate value sets accessing the same index will fail any queries against either scheme |
| LEXEVS-32773340 | Un-scrubbed NCIt load fails on null property nameProviding support for failing iterator paging on tree service extension |
| LEXEVS-3341 | NCIt History Load fails silently and throws other extraneous errors |
| LEXEVS-33853376 | 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. 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-3463Move Marker for LexEVS issues Kept as Unit tests3385 | Populate _ns attribute in LexEVSTreeItem with proper namespace |
| 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
...
| 2183 | Tree Extension: TreeService API returns JSON String containing anonymous nodes. |
| LEXEVS-3510 | I would like to Implement a service layer for the asserted value set search mechanism |
| LEXEVS-3681 | Serialization Error against the RMI of Resolved Value Set iterator |
| LEXEVS-3689 | AssertedValueset iterator cannot advance over paged next call |
| LEXEVS-3733 | Search Iterator Regression failure on Source Coding Scheme Name |
| LEXEVS-3779 | Orphaned Asserted VS Entity Service is not needed |
| LEXEVS-3783 | OWL2Loader manifest causes failed update in asserted value set index |
| LEXEVS-3830 | Target Namespace in mapping iterator ResolveConceptRefence incorrect |
...
LexEVS Remote API 6.5.1 - Features Implemented
...
