Page History
...
- Create a method over the Graph API that allows a CodedNodeSet to be passed as a parameter along with an Enumeration value indicating direction, a value for the depth of the resolution, and one or more associations. Return a List of Minimally populated ResolvedConceptReferences.
Constraints:
- Will not require current RMI users to update their client jar
- Features:
- Will provide a loader for the graph database
- Will provide instructions on the use of the loader, including any dependencies on existing services
Architecture:
- Specify which Graph DB will need to be installed on which tiers
- Specify any other services that need to be installed on which tiers
1. Create a Method:
Method Signature
public List<ResolvedConceptReference> getAssociatedConcepts(CodedNodeSet cns, Direction direction, int depth, NameAndValueList association);
Parameters:
Parameter cns: This CodedNodeSet must have a set of restrictions appropriate for query building and fully ready to be resolved. Cannot be null
Parameter direction: incoming or outgoing edges will be designated by one of these Enumerations. Cannot be null
...
It will not contain any entities or their properties or targetOf or sourceOf links to other entities.
2. Constraints
Initial testing is complete. Will retest before release. Since this is not implemented in the RMI application we don't need to require runtime client changes, especially since extensions are called as plugins and not from local client code.
3. Features
We have a loader complete at this point and it should have the same profile as other loaders.
The loader requires a local install of Arangodb along with a configuration of LexEVS where lbconfig.props is updated with connection parameters. Instructions for loader use will be supplied in the usual loader documentation section of the Wiki
Loader use is documented here:
Loading the Graph Database into ArangoDb for a Given Terminology
4. Architecture
We will work with the Systems team to get the most optimal installation of Arangodb for each tier.
Each tier will also need to have a tomcat instance with the graph-resolve installed to produce REST services for the Graph Resolution API.
...
We'll provide the usual configuration parameters for the REST service that are normally defined for deployment tracks on Jenkins and/or PTE documents.
9 - Installing the Graph Node Resolution REST Service
5. Migration
Proposal Sign off
...
Federal Sponsor(s) | Signature |
---|---|
Lyubov Remennik | via email |
Sherri De Coronado | SDC |
User(s) | Signature |
---|---|
Kim Ong | via email |
NCI System Architect | Signature |
---|---|
Tracy Safran | approved during arch meeting 2020.01.14 |
LexEVS Rest Service API
List of terminologies
base url/databases
List of associations
base url/graphDbs/<coding scheme name from database list>
Get inbound edges for coding scheme, association and unique id.
base url/getInbound/<coding scheme name>/<association name from graph list>/<entity code>
Get inbound edges for depth, coding scheme, association and unique id.
base url/getInbound/<depth/<coding scheme name>/<association name from graph list>/<entity code>
Get outbound edges for coding scheme, association and unique id.
base url/getOutbound/<coding scheme name>/<association name from graph list>/<entity code>
Get outbound edges for depth, coding scheme, association and unique id.
base url/getOutbound/<depth/<coding scheme name>/<association name from graph list>/<entity code>
LexEVS GraphResolve Legacy Requirements and Knowledge Base
...