Date: Fri, 29 Mar 2024 03:15:35 -0400 (EDT) Message-ID: <1546401320.871.1711696535269@ip-10-208-26-37.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_870_1885729965.1711696535268" ------=_Part_870_1885729965.1711696535268 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
LexEVS is the central EVS terminology server, developed by the Mayo Clin=
ic with NCI and other support. LexEVS provides a common terminology model a=
nd open access to a wide range of terminologies, terminology value sets, an=
d cross-terminology mappings needed by NCI and its partners. For users want=
ing to install and run a local instance of LexEVS, the LexEVS server packag=
e provides a comprehensive set of software and services to load, publish, a=
nd deploy vocabulary in a variety of web-enabled environments. The LexEVS A=
PI serves users who want programmatic access to the data made available by =
LexEVS.
LexEVS 6.5.0 is the current embodiment of work started under the LexBIG pr=
oject (LexGrid Vocabulary Services for caBIG=C2=AE). This technology was ad=
opted as the strategic infrastructure for the caBIG=C2=AE community and NCI=
's Enterprise Vocabulary Services (EVS).
NCI's EVS is a big user of the LexEVS services, but there are many others =
(see EVS Use=
and Collaborations). You can consume controlled terminologies hosted b=
y NCI's EVS without setting up your own servers to do so. Seeing what NCI h=
as done with EVS is a good way to learn about what LexEVS can do. Refer to =
the EVS Wiki for further information.=
LexEVS provides a collection of programmable interfaces, affording users a=
nd developers open access to both controlled terminologies available from t=
he NCI EVS Downloads page and other supported=
terminologies. NCI's installation of LexEVS is not only a tool for the com=
munity to use, but also an example of what developers can build at their ow=
n sites. 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.
LexEVS includes the following components:
The name LexEVS highlights the merging of LexGrid, LexBIG, and EVS techn= ologies and designates an entire suite of applications. In this suite, LexG= rid is the underlying model for standard storage of controlled vocabularies= and ontologies. The LexBIG API is the set of services that EVS adapters us= e to store and retrieve terminology metadata. LexEVS APIs are a combination= of convenience methods and the LexBIG API (combining LexBIG and the EVS ad= apters into one set of services). For detailed information, refer to the LexEVS architecture overv= iew.
After you have a chance to get familiar with the LexEVS suite, consider = looking through the LexEVS 6.5.0 Functionality Overview. This lays out everything = that can be done from a developer's or ontologist's point of view.
The ins= tallation overview provides an introduction to the different environmen= ts that can be installed. Refer to the LexEVS 6.x Installation Guide for more informatio= n.
The LexEVS= 6.5.0 Installation Options identify the download files for each LexEVS= environment that can be installed (Local Runtime, Distributed, and Grid Se= rvices).
The LexEVS Widget Libr= ary lists many widgets that have been developed for use by particular c= ustomers. 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 appl= ication.
LexEVS Issues and Discussion
Users and developers can report and discuss issues regarding the LexEVS ap=
plication on its GitHub site.
Features - refer to LexEVS 6.5.0 Release Notes=
LexEVS 6.5.0 Technical stack updates.
CTS2 References on this Wiki
The contribution process is described in LexEVS Community Code Contribution. Lex= EVS source code is in the NCIP channel of Github
Refer to LexEVS Present= ations.