 |
Page History
...
2015 December Face-to-Face Meeting Prioritization List
All issues are considered after 6.4 related development.
Priority (1-high, 3-low) | Category | Topic | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1.5 | Tech Catalog | Migrate to centOS 7 | 6.5 Required for better Docker support. | ||||||||||
| 1 | Tech Catalog | Migrate to Java 8 | 6.5 | ||||||||||
| 1.5 | Tech Catalog | Migrate to Spring 4 | 6.5 | ||||||||||
| 2 | Development | Value Set Performance - review compiled Value Set Definitions | Development | Tree Performance - determine requirements and propose solution | Linked to the triple store discussions. | ||||||||
| 2 | Development | CTS2 Functionality - Expand to fully support browser | |||||||||||
| 1 | Development | CTS2 Functionality - CTRP Support - Determine specific requirements and propose solution (Partonomy, Disease Biomarker, and others) | TBD (early 2016Q2?) | ||||||||||
| Development | LexEVS Model - OWL and RRF Mapping use cases - Determine requirements and propose solution | This would include consulting with Harold Solbrig. Considerations for backward compatibility with suggested changes. | |||||||||||
| Development | Multi-namespace - determine requirements and propose solution | ||||||||||||
| Development | Query - Relationships - determine requirements and propose solution | ||||||||||||
| Development | Inferred Data - determine requirements and propose solution | ||||||||||||
| Development | Remove caCORE | ||||||||||||
| Development | Refactor Remote API | Suggested inclusion with Spring migration | |||||||||||
| 1 | Development | CTS2 Functionality - Ability to provide complete transitive closure | Will support CTRP requirement. | ||||||||||
| Development | CTS2 Functionality - Ability to restrict to association | ||||||||||||
| Development | CTS2 Functionality - Ability to provide history API functionality | May be required for CTRP | |||||||||||
| Development | CTS2 Functionality - Ability to group value sets together (FDA and SPL) | ||||||||||||
| Development | CTS2 Functionality - Report to OMG the issue pertaining to return all results | ||||||||||||
| Support | Documentation Updates - review and clean up "LexEVS Code Examples" | ||||||||||||
| Support | Documentation Updates - Update CTS2 API documentation | ||||||||||||
| Development | Presentation of Value Set and Mapping Data with Hierarchical structure - determine requirements and propose solution. | ||||||||||||
| Development | Lucene Implementation - Document query result differences and share with group to decide on solution. | ||||||||||||
| Loader | OWL2 -
| Gilberto to provide requirements. | |||||||||||
| Loader | OWL2 -
| Included as part of OWL2 implementation. | |||||||||||
| Loader | MedDRA - Provide comparison of MedDRA loaders to identify differences - determine requirements and propose a solution. | ||||||||||||
| Loader | HL7 -
| ||||||||||||
| Loader | MedDRA - Close
| ||||||||||||
| Loader | HL7 - Close
| ||||||||||||
| Loader | HL7 - Review HL7 website rendering of brach/hierarchy to determine requirements and to propose solution to support HL7 structure. | ||||||||||||
| Loader | Load Process Automation - determine requirements and propose a solution. | ||||||||||||
| Loader | Review all loader related JIRA issues and remove those that are no longer valid. | ||||||||||||
| Loader | MySQL 5.5 Table Locking issue - propose a solution. | ||||||||||||
| Loader | SNOMED -
| ||||||||||||
| Loader | OWL2 -
| ||||||||||||
| Loader | Value Set -
| ||||||||||||
| Loader | CLAML - Close -
| ||||||||||||
| Loader | Create an OWL2 to LexGrid Model spreadsheet (mapping). | ||||||||||||
| 2 | Development | Triple Store / SPARQL- Clarify the strengths and weaknesses in the tools (Blazegraph, Virtuoso, Stardog) to determine how to best address . | the browser and LexEVS needs. | This will be led by Kim and Jason. They will share their evaluation with the group to help determine the best approach. | |||||||||
| 2 | Development | Review of value set workflow (including resolution) to determine requirements and proposed changes. | |||||||||||
| Development | Review of admin workflow to determine requirements and proposed admin script changes and additions. | ||||||||||||
| Development | lbGUI - Provide viewing additional metadata in the GUI. |
...
