Page History
Page info | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Panel | ||
---|---|---|
| ||
Author: Craig Stancl Email: Stancl.craig@mayo.edu Team: LexEVS |
Sign off | Date | Role | CBIIT or Stakeholder Organization |
---|---|---|---|
The purpose of this document is to collect, analyze, and define high-level needs and features of the National Cancer Institute Center for LexEVS Release 6.1. This document focuses on the functions proposed by the product stakeholders and target users in order to make it a better product. The use-case and supplementary specifications document will detail how the framework will fulfill these needs.
Vision and Needs
The objective of this release of the LexEVS API is to provide a CTS2 compliant REST API, Enhanced Performance and new loaders.
Functional Requirements
Each enhancement, modification or new feature is described in detail below.
Functional Bug Fixes
Each bug fix included in this release is described in detail below.
Non-Functional Requirements
This section describes in detail all the related requirements which must be met for this release but do not add functionality. These requirements are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.
General Support Activities
This section describes in detail all the related activities which must be performed for this release but do not add functionality. These activities are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.
JIRA number (hyperlinked) | Brief description of general support activity | Status | Iteration |
---|---|---|---|
| LexEVS Level 2 Support - integration of help and training to the user community. |
| --- |
Stakeholder Summary
CBIIT Staff/Contractor Name | Role | Responsibilities |
---|---|---|
Craig Stancl | Mayo Clinic Technical Lead | Technical Direction and Implementation |
Mandy Ager | Mayo Clinic Project Manager | Project schedule and task management |
Out of Scope Items
Items that are out of scope were evaluated as part of the initial scoping activities for this release, and subsequently not included in the final approved scope. These items are also documented in the cumulative backlog of requirements found on the product GForge site. They include out-of-scope functional requirements (enhancements or new features), bug fixes, non-functional requirements, and general support activities.
JIRA number (hyperlinked) | Brief description of item moved from the in-scope section | Iteration during which the item |
---|---|---|
LEXEVS-505 | Case-insensitive concept code search support. | Inception |
LEXEVS-239 | OBO loaded data with roots that delcare disjointness do not display in hierarchy | Inception |
LEXEVS-236 | OBO optional synonym type name | Inception |
LEXEVS-370 | Export the content of ResolvedValueSetDefinition to StringBuffer in LexGrid XML format | Inception |
LEXEVS-372 | Extensions should be able to add properties to existing concepts | Inception |
LEXEVS-369 | Add a label or description member variable to EntityDescription. | Inception |
LEXEVS-367 | Support retrieval of ValueSetDefinition by multiple coding schemes. | Inception |
LEXEVS-366 | Modify output parameter of the getCodingSchemesInValueSetDefinition method in LexEVSValueSetDefinitionServices. | Inception |
LEXEVS-368 | Support retrieval of ValueSetDefinition by multiple concept domains. | Inception |
LEXEVS-365 | Resolve nested value set definition through distributed Value Set API. | Inception |
LEXEVS-363 | Extend MappingExtension functionalities to support restrictions. | Inception |
LEXEVS-354 | Load source qualifiers for generic properties in NCI-META RRF loader | Inception |
LEXEVS-350 | Examine use of LexBIG entity status | Inception |
LEXEVS-531 | Build scripts do not have path for dataqa | Inception |
LEXEVS-255 | Linux gui does not work | Inception |
LEXEVS-233 | SNOMED Role Groups not loading from RRF files | Inception |
LEXEVS-227 | Lucene Max Clause Count exceeded on broad NCI MetaThesaurus RegExp Restrictions | Inception |
LEXEVS-371 | Make it easy to do retrieval of only active concepts in a terminology through the/ a service | Inception |
LEXEVS-362 | Owl/rdf exporter limitation | Inception |
LEXEVS-345 | Convert codes in entity description of anonymous class to names. | Inception |
LEXEVS-512 | LexEVSValueSetDefinitionServices.getCodedNodeSetForValueSetDefinition method can be extremely slow. | Inception |
LEXEVS-508 | Mapping concepts don't always have a suitable target | Inception |
LEXEVS-507 | Inefficient query when trying to filter Metathesaurus by Source. | Inception |
LEXEVS-496 | LexEVS api calls do not populate directionalName in the association | Inception |
LEXEVS-515 | Caching of value sets don't always work | Inception |
LEXEVS-518 | Trying to load ICD10 results in error | Inception |
LEXEVS-516 | LexEVSValueSetDefinitionServices getValueSetDefinitionEntitiesForTerm fails on inactive coding schemes. | Inception |
LEXEVS-519 | Inconsistant package naming | Inception |
LEXEVS-461 | Necessity to rebuild indexes after load | Inception |
LEXEVS-538 | Loader should support unicode | Inception |
LEXEVS-521 | Transition table hangs in UMLS loader on large vocabs | Inception |
LEXEVS-244 | Unqueryable classes are registered by the grid service | Inception |
LEXEVS-232 | The codedNodeGraph is not displaying the top nodes correctly | Inception |
LEXEVS-235 | PDQ load shows multiple LT : TRD properties in browser | Inception |
LEXEVS-234 | RRF Snomed Loader not interpreting SNOMED status codes correctly | Inception |
LEXEVS-230 | The contains algorithm fails on search strings starting with a single character word such as 'a'. | Inception |
LEXEVS-442 | NCIt Loader preferences file with defaults | Inception |
LEXEVS-361 | Unregister coding scheme supplement through the LexBIG GUI application. | Inception |
LEXEVS-360 | Add a Boolean-Valued member variable applyToSubconcepts to EntityReference. | Inception |
LEXEVS-359 | Need an effective way of counting the size of a CNG. | Inception |
LEXEVS-356 | GUI should reflect administrative nomenclature | Inception |
LEXEVS-358 | Authoring Tool / Graphical User Interface (GUI) | Inception |
LEXEVS-353 | Need an option to exclude the focused node itself from ResolvedConceptReferenceList when resolving a CNG. | Inception |
LEXEVS-352 | Better validation on restrictions | Inception |
LEXEVS-347 | Control the setting of isActive via Loader preferences | Inception |
LEXEVS-348 | Ability to query for inferred data - implement ability to reason | Inception |
LEXEVS-344 | Enhance LexBIG query API to fetch AssociationData objects. | Inception |
LEXEVS-269 | Demonstrate cross ontology relationships | Inception |
LEXEVS-264 | Validation of UTF-8 subset | Inception |
LEXEVS-250 | Duplicate alias "_value" when quering LexEVSDataService | Inception |
LEXEVS-510 | Documentation location in the installer | Inception |
LEXEVS-511 | UMLS meta loader script is in the wrong format | Inception |
LEXEVS-509 | Sorting in Mapping tab in Term Browser can lead to 500 errors | Inception |
LEXEVS-500 | Load Progress indicators | Inception |
LEXEVS-517 | LexEVSAuthoringServiceImpl 'getEntity' restricts to types of 'concept' | Inception |
LEXEVS-469 | Attempted load of a MRMAP mapping failed with inscrutable error | Inception |
LEXEVS-482 | Ability to load metadata and mapping in one operation | Inception |
LEXEVS-481 | Ability to load metadata and coding scheme in one operation | Inception |
LEXEVS-475 | Enhancement to versioning of Mapping loads | Inception |
LEXEVS-480 | Better support for "Metathesaurus" data structures (e.g. accessing source hierarchies in NCI-META) | Inception |
LEXEVS-478 | Clean up GUI - functionality should match documentaion/presentation | Inception |
LEXEVS-476 | Ability to load MRMAP without a MRSAT entry | Inception |
LEXEVS-474 | Ability to add metadata to value set definitions | Inception |
LEXEVS-473 | Concept Sorting in Mappings when using local API | Inception |
LEXEVS-446 | UMLS loader should give an error if the SAB is not specified | Inception |
LEXEVS-454 | OWL Export exhibits memory leak. | Inception |
LEXEVS-493 | Search SNOMEDCT for '<' using the contains algorithm returns no matches. | Inception |
LEXEVS-464 | The NCI OWL loader is loading the "type" property inconsistently | Inception |
LEXEVS-463 | The NCI OWL loader is loading Metadata properties inconsistently. | Inception |
LEXEVS-462 | NCI OWL loader for LexBIG 6.0 is creating extraneous "label" property qualifiers | Inception |
LEXEVS-460 | Enable use of ALT keys in LexEVS Developer GUIs | Inception |
LEXEVS-459 | Batch Loader for LexEVS Value Set | Inception |
LEXEVS-529 | ValueSetDefinition getDefinitionEntryCount() returns incorrect number | Inception |
LEXEVS-537 | JIRA task - Unable to assign issues to QA person, and not Ready For QA status | Inception |
LEXEVS-536 | The ResolvedConceptReferencesIterator numberRemaining method can be quite inaccurate. | Inception |
LEXEVS-535 | Term Browser "View In Hierarchy" function fails for ICD10 root nodes | Inception |
LEXEVS-534 | Reduce error volume for hibernate issues | Inception |
LEXEVS-525 | Metathesaurus does not load completely | Inception |
LEXEVS-528 | Suppressable CUIs in RRF loader | Inception |
LEXEVS-223 | Anonymous class hierarchy with unions not showing up correctly. | Inception |
LEXEVS-341 | REST API Features | Inception |
LEXEVS-339 | MedDRA loading into LexEVS | Inception |
LEXEVS-497 | Documentation Issue | Inception |
LEXEVS-502 | Spelling error in loader | Inception |
Document History
Item | Information |
---|---|
Document Version: | Click the Info tab. View the Recent Changes or click the link to view the page history. |
Last Modified: | Refer to the first line displayed in the document window. |
Project JIRA site: |
|
Most current version: | Unless the display includes a notice that you are viewing a previous version, you are viewing the most current version of this Scope Document for the release indicated in the title. |
Revision history: | Click the Info tab. In the Recent Changes area, click the link to view the page history. |
Review history: | Click the Info tab. In the Recent Changes area, note the developer who made each change and the date and time. Refer to the Key People Directory for their roles. Click the link to view any page or to view the page history, and then click the link for a page. When the page opens, view the comments and changes made in that version. |
Related documents: |
Project Information
CBIIT Management | Role | Responsibilities |
---|---|---|