Page History
...
Wiki Markup |
---|
{scrollbar:icons=false} |
...
...
...
title | Contents of this Page |
---|
...
Panel | ||
---|---|---|
| ||
Author: Craig Stancl, Scott Bauer, Cory Endle |
...
...
...
Role
...
CBIIT or Stakeholder Organization
...
Reviewer's Comments (If disapproved indicate specific areas for improvement.)
...
---
...
—
...
—
...
---
...
Sherri de Coronado
...
—
...
—
...
---
...
—
...
Kumar Kuntipuran
...
---
...
—
...
—
...
—
Panel | ||||
---|---|---|---|---|
| ||||
|
The purpose of this document is to document the project requirements for the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT)LexEVS Release 6.23.
Requirements Definition
JIRA item | Functional Requirement | Design Reference | |||
---|---|---|---|---|---|
LEXEVS- | 570Loader messaging is poor and unhelpful | N/A | |||
LEXEVS-590 | Need a convenience method for identifying and retrieving resolved value set coding schemes. | LexEVS 6.2 Design Document - Detailed Design - Make it easy to do retrieval of only active concepts in a terminology through the/ a service | |||
LEXEVS-605 | New Script for Removing Tags | N/A | |||
LEXEVS-371 | Make it easy to do retrieval of only active concepts in a terminology through the/ a service | LexEVS 6.2 Design Document - Detailed Design - Make it easy to do retrieval of only active concepts in a terminology through the/ a service | |||
LEXEVS-633 | Remove Struts and all dependencies from the caCORE based implementation | N/A | |||
LEXEVS-639 | Remove CTS2 Java API from 6.2 release | N/A | |||
LEXEVS-617 | Provide any needed support for CENTOS upgrade | N/A | |||
LEXEVS-618 | Provide support, application changes as needed for moving the LexEVS api to Tomcat from JBoss | N/A | |||
LEXEVS-619 | Provide application changes to support MySQL 5.5 | N/A | |||
LEXEVS-608 | Update LexEVS to Java 1.7 compatability | N/A | |||
LEXEVS-621 | Remove Security Risk form caCORE lexevsapi implemenation (Struts issue) | N/A | |||
LEXEVS-624 | Upgrade of the Apache Struts to release 2.3.16.1 to LexEVS 6.1 | N/A | |||
LEXEVSCTS2-1 | UI - Create an NCI CTS2 Value Set Viewer | LexEVS 6.2 Design Document - Detailed Design - UI - Create an NCI CTS2 Value Set Viewer | |||
LEXEVSCTS2-2 | CTS2 Service - Update LexEVS CTS2 Service to the CTS2 1.1 specification as implemented in the CTS2 Development Framework | N/A | |||
LEXEVSCTS2-3 | CTS2 Service - Create CTS2 Value Set module | LexEVS 6.2 Design Document - Detailed Design - CTS2 Service - Create CTS2 Value Set module | |||
LEXEVSCTS2-22 | Upgrade to CTS 2 1.1 framework | N/A | |||
669 | Latest Version of SNOMEDCT Does not load transitivity table | ||||
LEXEVS-671 | SNOMEDCT does not load hierarchy or root nodes. | ||||
LEXEVS-598 | TreeService getTree method can fail when the root node code appears in multiple namespaces. | ||||
LEXEVS-667 | TreeService getTree method fails on remote call when the root node code appears in multiple namespaces. | ||||
LEXEVS-686 | lbRuntime scripts dependent on lexgrid.org | ||||
LEXEVS-685 | OWL2 Loader loads disJointWith association as equivalent class | ||||
LEXEVS-684 | OWL2 Loader does not properly Parse output from render | ||||
LEXEVS-623 | Mapping extension search methods fail on distributed mode. | ||||
LEXEVS-614 | OWL2 associations and annotations on associations. | ||||
LEXEVS-636 | LexEVSValueSetDefinitionServices exportValueSetResolution method returns unprocessible InputStream. | ||||
LEXEVS-688 | Resolved Value Set Doesn't persist Coding Scheme versions | ||||
LEXEVS-721 | OWL loader does not account for inconsistencies in namespace, coding scheme URL's | ||||
LEXEVS-680 | Remove GEM loader documentation | ||||
LEXEVS-681 | LexEVS distributed landing page typos | ||||
LEXEVS-641 | OWL2 loader uses VersionIRI, but doesn't have a wide enough column | ||||
LEXEVS-583 | OWL2 data: restrictions on a class using datatype properties | ||||
LEXEVS-679 | Expand loader documentation to include creating, running, and errors information. | ||||
LEXEVS-689 | Need to insure backward compatability for the convenience methods | ||||
LEXEVSCTS2-28 | NLM (VSAC) CTS2 Service authentication is failing | ||||
LEXEVSCTS2-8 | UI - Only 50 entries are returned for value sets that have more than 50 entries | ||||
LEXEVSCTS2-27 | Create interactive CTS2 API documentation | ||||
LEXEVSCTS2-21 | Value Set resolution fails when a value set name is more than a particular number of characters. | LEXEVSCTS2-25 | Adjust Landing and Service pages in the LexEVS CTS2 service application | LexEVS 6.2 Design Document - Detailed Design - Adjust Landing and Service pages in the LexEVS CTS2 service application |
Wiki Markup |
---|
{scrollbar:icons=false} |