Import via Aidbox Configuration project
Last updated
Was this helpful?
Last updated
Was this helpful?
is used to configure Aidbox with various features. One of the things itβs used for is providing Aidbox with external terminologies.
, or FTR, is an efficient way to store and handle terminologies. It is the recommended way to work with CodeSystem and ValueSet resources in Aidbox. You can start using it by providing set up with FTR.
This approach is deprecated. Its support may end in the near future.
Specify path or url to zen terminology bundle in .
Source is either url
or path
. url
is used to download Aidbox project from a remote location; path
is used to load Aidbox project from the filesystem.
Aidbox imports terminology bundles found in zen paths. Bundles are just .ndjson.gz
files with filenames matching *terminology-bundle.ndjson.gz
wildcard. By default, the import is done asynchronously and you can . In some cases (e.g CI/CD pipeline) you might want to override such behavior. Setting BOX_FEATURES_TERMINOLOGY_IMPORT_SYNC
environment variable will change the import mode to synchronous.
Aidbox reads files from on startup and imports files whose names end with terminology-bundle.ndjson.gz
.
For example, path to terminology bundle GZIP fie is: /my/aidbox/project/my-terminology-bundle.ndjson.gz
.
To load the terminology bundle into Aidbox set the following environment variables:
You can read more about and in our .
Make sure that your Aidbox container on your system.
Zip-archive your terminology bundle that is my-terminology-budnle.ndjson.gz file in my-terminology.zip file.
Upload your my-terminology.zip to a remote server e.g. https://example.com/terminologies/my-terminology.zip
Aidbox will import terminology from the specified path on start.
Aidbox offers an RPC method to track the async import progress. The response shows bundles in the import queue, failed imports and currently importing bundle.
Request:
Response example:
Set