![]() |
Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
| ||||
Section | ||||
Column | | width | 25%
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| unmigrated-wiki-markup||||||||||
* Author: * \[Project Manager/Technical Lead\] *Email:* \[Email address for Scope Document contact\] *Team:* \[For example caDSR, EVS, caGRID, and so on.\] *Contract:* \[Contract number\] *Client:* NCI CBIIT National Institutes of Heath US Department of Health and Human Services
Column | LexEVS Team/Craig Stancl |
Sign off | Date | Role | CBIIT or Stakeholder Organization | Reviewer's Comments (If disapproved indicate specific areas for improvement.) |
---|
...
— |
...
— |
...
— |
...
...
...
...
...
...
Wiki Markup |
---|
The *purpose of this document* is to collect loader topic discussion and resolution for \[LexEVS\]. The focus is on the processing of source content as loaded into LexEVS terminology server proposed by the stakeholders and target users to make a better product. |
Info | ||
---|---|---|
| ||
Use the sub-headings that you need for details of your Design Scope, Solution Architecture, and Implementation Requirements. Delete the ones you do not need, along with this note. |
Loader Topics
GForge items
— | — |
The purpose of this document is to collect loader topic discussion and resolution for LexEVS. The focus is on the processing of source content as loaded into the LexEVS terminology server, proposed by the stakeholders and target users to make a better product.
Control the setting of isActive via Loader preferences
GForge | Issue | Resolution |
---|---|---|
Different vocabs have their own way of determining whether a concept is active or not. For OWL we can use Deprecated status. For OBO or RRF we don't have that. We would like to be able to specify what method a vocab is using to indicate deprecated concepts in the loader preferences. | TBD |
Discussion: Control the setting of isActive via Loader preferences
Capture discussion here.
Examine use of LexBIG entity status
GForge | Issue | Resolution |
---|---|---|
The entity status for concepts should use a designated set of statuses that are mappable across vocabularies. For example: | TBD |
Discussion: Examine use of LexBIG entity status
Capture discussion here.
The isDefined column in the entity table should accurately reflect the source data
GForge | Issue | Resolution |
---|---|---|
All concepts loaded from RRF show as defined, which is unlikely to be true. We need to examine the various sources and see what changes need to be made to the loader to correctly represent the defined/primitive status of concepts in the source data. Pasted below is the email discussion that led to this item. | TBD |
Discussion: The isDefined column in the entity table should accurately reflect the source data
Capture discussion here.
Scrollbar | ||
---|---|---|
|
...