Page History
...
ActivateScheme | Activates a coding scheme based on unique URN and version.
| |||||
CleanUpMetadata | Clean up metadata entries that are orphaned. Options: -h, --help, Prints usage information -f,--force, Force removal without prompting of metadata that doesn't have a corresponding coding scheme entry(orphaned). Example:
| |||||
DeactivateScheme | Deactivates a coding scheme based on unique URN and version.
| |||||
ListExtensions | List registered extensions to the LexEVS runtime environment.
| |||||
ListSchemes | List all currently registered vocabularies.
| |||||
LoadManifest | Load manifest data onto the codingscheme based on unique | RemoveTagScheme | Removes a tag ID (e.g. 'PRODUCTION' or 'TEST') from a coding scheme URN and version. Options: -u,--urn <urn> "urn"; URN uniquely identifying the code system. -v,--version <id> "versionId"; Version identifier. -mf,--manifest "manifest"; location of manifest xml file.
Note: If either the URN and or the version values are unspecified, a list of available coding schemes will be presented for user selection. Example:
RemoveTagScheme
| |||
RemoveTagScheme | Removes a tag ID (e.g. 'PRODUCTION' or 'TEST') from a coding scheme URN and version. | RemoveVSResolvedFromCodingScheme | Removes a resolved ValueSet based on coding scheme and version that was used for its resolution.
Options: -l, List of coding scheme versions to match when removing the ResolvedValueSetu,--urn <urn> URN uniquely identifying the code system. -fv,--force Force de-activation and removal without confirmation. Example:
version <id> Version identifier.
Note: If the URN and version values are unspecified, a list of available coding schemes will be presented for user selection. Example:
| |||
RemoveVSResolvedFromCodingScheme | Removes a resolved ValueSet based on coding scheme and version that was used for its resolution.
| RemoveResolvedValueSet | Removes a resolved ValueSet Options: -l, List of coding scheme versions to match when removing the ResolvedValueSet. -f,--force Force de-activation and removal without confirmation. Example:
| |||
RemoveResolvedValueSet | Removes a resolved ValueSet Options: -l, The list of resolved value sets to remove, separated The list of resolved value sets to remove, separated by comma. format "resolvedValueSetUri1::version1, resolvedValueSetUri2::version2,...". -f,--force Force de-activation and removal without confirmation.
Load Example:
| |||||
RemoveValueSetDefinition | Removes a coding scheme based on unique URN and versionURN and version. Options: -u,--urn <urn> URN uniquely identifying the code system.
Note: If the URN and version values are unspecified, a list of available coding schemes will be presented for user selection. Example: | |||||
TagScheme | Associates a tag ID (e.g. 'PRODUCTION' or 'TEST') with a coding scheme URN and version.
|
Lucene Index Administration
BuildAssertedValueSetIndex | Builds indexes associated with the source asserted value sets of the specified coding scheme. Options: -u,--urn <urn> URN uniquely identifying the code system. -v,--version <id> Version identifier. -f,--force Force clear (no confirmation).
Note: If the URN and version values are unspecified, a list of available coding schemes will be presented for user selection. Load Example:
RemoveValueSetDefinition
| TagScheme |
| ||||||
BuildResolvedAndAssertedValueSetIndexes | Builds indexes associated with the source asserted value sets of the specified coding scheme. Adds the value set entities of any resolved value sets external to the asserted source Options: -u,- | -u,-urn <urn> URN uniquely identifying the code system. -v,--version | <versionId> <id> Version identifier. - | tf, | -tag The tag ID (e.g. 'PRODUCTION' or 'TEST') to assign. --force Force clear (no confirmation).
Note: If the URN and version values are unspecified, a list of available coding schemes will be presented for user selection. Example:
| TagScheme
|
|
...
CleanUpLuceneIndex | Clean up orphaned indexes.
| |
RebuildIndex | Rebuilds indexes associated with the specified coding scheme.
| |
RemoveIndex | Clears an optional named index associated with the specified coding scheme. Note Built-in indices required by the LexEVS runtime cannot be removed. Options:
|
...
Load | A generic loader script that allows for the selection of a Loader Extension. Options: -in,--input <uri> URI or path specifying location of the source file -l, --loader <name> LexGrid Load Extension name -mf,--manifest <uri> URI or path specifying location of the manifest file -a, --activate ActivateScheme on successful load; if unspecified the vocabulary is loaded but not activated. -t, --tag <id> An optional tag ID (e.g. 'PRODUCTION' or 'TEST') to assign.
Example:
| ||
LoadLgXML | Loads a vocabulary file, provided in LexGrid canonical xml format.
| ||
LoadMedDRA | Loads a file specified in the Medical Dictionary for Regulatory Activities (MedDRA) format. Options:
Validation Example:
Load CUI Example:
| ||
LoadMetaData | Loads optional XML-based metadata to be associated with an existing coding scheme.
| ||
LoadMIFVocabulary | Loads from an the HL7 Vocabulary mif file. Options:
| ||
LoadMrMap | Loads mappings file(s), provided in UMLS RRF format. Specifically MRMAP.RRF and MRSAT.RRF.
| ||
LoadNCIHistory | Imports NCI History data to the LexEVS repository.
| ||
LoadOBO | Loads a file specified in the Open Biomedical Ontologies (OBO) format.
| ||
LoadOWL | Loads an OWL file. Note Load of the NCI Thesaurus should be performed via the LoadNCIThesOWL counterpart, since it will allow more precise handling of NCI semantics. Options:
| ||
LoadOWL2 | Loads an OWL file. You can provide a manifest file to configure coding scheme# meta data.
| ||
LoadResolvedValueSetDefinition | Loads Value Set Definition content, provided in LexGrid canonical xml format.
| ||
LoadText | Loads a file in LexGrid Text format. Options: -in,--input <uri> URI or path specifying location of the source file -d, --delimiter <character> defaults to tab the character used to delimit pair or triple components and the nesting. -mf,--manifest <uri> URI or path specifying location of the manifest file. -v, --validate <int> Perform validation of the candidate resource without loading data. If specified, the '-a' and '-t' options are ignored. Supported levels of validation include: 0 = Verify document is valid -a, --activate ActivateScheme on successful load; if unspecified the vocabulary is loaded but not activated. -t, --tag <id> An optional tag ID (e.g. 'PRODUCTION' or 'TEST') to assign.
Load Example: | ||
LoadUMLSHistory | Loads UMLS History
-in,--input <uri> URI or path specifying location of the source file -v, --validate <int> Perform validation of the candidate resource without loading data. If specified, the '-a' and '-t' options are ignored. Supported levels of validation include: 0 = Verify document is valid -a, --activate ActivateScheme on successful load; if unspecified the vocabulary is loaded but not activated. -r, --replace Replace exisiting file. -t, --tag <id> An optional tag ID (e.g. 'PRODUCTION' or 'TEST') to assign.
| ||
LoadUMLSSemnet.sh | Loads the UMLS Semantic Network, provided as a collection of files in a single directory. The following files are expected to be provided from the National Library of Medicine (NLM) distribution: Options: -in,--input <uri> URI or path of the directory containing the NLM files -v, --validate <int> Perform validation of the candidate resource without loading data. If specified, the '--a' and '-t' options are ignored. Supported levels of validation include: 0 = Verify the existence of each required file -a, --activate ActivateScheme on successful load; if unspecified the vocabulary is loaded but not activated. -t, --tag <id> An optional tag ID (e.g. 'PRODUCTION' or 'TEST') to assign. -il,--InheritanceLevel <int> If specified, indicates the extent of inherited relationships to import. 0 = none; 1 = all; 2 = all except is_a (default). All direct relationships are imported, regardless of option. Load Example:
|
...