 |
Page History
...
| Wiki Markup |
|---|
{multi-excerpt:name=LexEVSSummary}
LexEVS is the central EVS terminology server, developed by the Mayo Clinic with NCI and other support. LexEVS provides a common terminology model and open access to a wide range of terminologies, terminology value sets, and cross-terminology mappings needed by NCI and its partners. For users wanting to install and run a local instance of LexEVS, the LexEVS server package provides a comprehensive set of software and services to load, publish, and deploy vocabulary in a variety of web-enabled and grid environments. The LexEVS API serves users who want programmatic access to the data made available by LexEVS.
LexEVS 6.1 is the current embodiment of work started under the LexBIG project (LexGrid Vocabulary Services for caBIG®). This technology has been adopted as the strategic infrastructure for the caBIG® community and NCI's Enterprise Vocabulary Services (EVS).
NCI's EVS is a big user of the LexEVS services, but there are many others. You can consume controlled terminologies hosted by NCI's EVS without setting up your own servers to do so. Seeing what NCI has done with EVS is a good way to learn about what LexEVS can do. Refer to the [EVS Wiki|https://wiki.nci.nih.gov/x/paSl] for further information.
LexEVS provides a collection of programmable interfaces, affording users and developers open access to either controlled terminologies available from the [NCI EVS Project|http://ncicb.nci.nih.gov/download/evsportal.jsp] or their own terminologies. NCI's installation of LexEVS is not only a tool for the community to use, but also an example of what developers can build their own organization. By building an installation of LexEVS, an organization can control the content and have any set or subset of terminologies and mappings. One installation can be used by multiple applications in an enterprise.
{multi-excerpt} |
| Wiki Markup |
|---|
{multi-excerpt:name=LexEVS6.0a}LexEVS includes the following components:
* Terminology Server - An enterprise level terminology server
* Java API - A Java interface based on the LexGrid Object Model
* REST/HTTP Interface - Offers basic HTTP based query mechanism from which results are returned in either XML or HTML formats
* SOAP/Web Services Interface - Provides a programming language neutral Service-Oriented Architecture (SOA)
* Distributed API - A Java interface based on the LexGrid data model and relies on a LexEVS Proxy and *Distributed LexEVS Adapter to provide remote clients access to the native LexEVS API
* LexEVS Grid Services - An interface which uses the caGRID infrastructure to provide access to the native LexEVS API via the caGRID Services
* Developers GUIs - Server administration, query testing, and value set development can be performed by a developer
The name LexEVS highlights the merging of LexGrid, LexBIG, and EVS technologies and designates an entire suite of tools. In this suite, LexGrid is the underlying model for standard storage of controlled vocabularies and ontologies. The LexBIG API is the set of services that EVS adapters use to store and retrieve terminology metadata. LexEVS APIs are a combination of convenience methods and the LexBIG API (combining LexBIG and the EVS adapters into one set of services). For detailed information, refer to the [LexEVS architecture overview|LexEVS:LexEVS 6.0 Architecture].
After you have a chance to get familiar with the LexEVS suite, consider looking through the [LexEVS:LexEVS 6.0 Functionality Overview]. This lays out everything that can be done from a developer's or ontologist's point of view.
h2. Installation and Downloads
The [installation overview|LexEVS:1 - LexEVS 6.0 Installation Overview] provides an introduction to the different environments that can be installed. Refer to the [LexEVS:LexEVS 6.0 Installation Guide] for more information.
The [LexEVS:LexEVS 6.0 Installation Options] identifies the download files for each LexEVS environment that can be installed (Local Runtime, Distributed, and Grid Services).
The [LexEVS:LexEVS Widget Library] lists many widgets that have been developed for use by particular customers. These widgets have been found to be potentially useful to a wider audience. Each widget has a description for you to use in deciding if you'd like to dig deeper and find out the usefulness of the widget in your application.
{include:VKC:Code Download Disclaimer to Include}
h2. Forum and Support{multi-excerpt} |
...
| Wiki Markup |
|---|
{multi-excerpt:name=LexEVSSupportLinks}* [LexEVS FAQ]
Please visit our FAQs especially if you are new to LexEVS.
* [LexEVS End User forum |https://cabig-kc.nci.nih.gov/Vocab/forums/viewforum.php?f=13]
Forum for end users to discuss and submit support issues regarding the LexEVS application.
* [LexEVS Developer forum |https://cabig-kc.nci.nih.gov/Vocab/forums/viewforum.php?f=16]
Forum for developers to discuss and submit support issues regarding the LexEVS API.
* [LexEVS Documentation Feedback forum|https://cabig-kc.nci.nih.gov/Vocab/forums/viewforum.php?f=46]
Forum for all users to discuss and submit support issues regarding the LexEVS documentation.
* [Bug Tracker for LexEVS|https://tracker.nci.nih.gov/browse/LexEVS]
Please visit the LexEVS Jira project for bug and feature requests related to LexEVS.
* If you find the above mechanism are not going to work for you please contact [Application Support (email)|mailto:ncicb@pop.nci.nih.gov].{multi-excerpt} |
...
