projects / org / mugo.ca / datasources
Find the Exponential Software extensions you want
UNIX name | Owner | Status |
---|---|---|
datasources | Mugo.ca | stable |
Version | Compatible with |
---|---|
N/A | N/A |
This project is all the data-source specific code for loading
BloomAPI's public data APIs. Each data-loader is its own binary.
The runner directory contains a tool to run all the binaries
available to update any given datasource. All other directories
contain data-source specific loading code.
To build the loader binaries + runner:
Every binary requires access to a local copy of config.toml, dbmapping.yaml, and searchmapping.yaml. Alternatively, you can reference a folder that contains config.toml by setting the environment variable BLOOM_CONFIG. For example, the following would be used to add a data source to BloomAPI (from the directory output by make go/bin/linux_amd64/datasources/sources/usgov.hhs.npi):
BLOOM_CONFIG=../../ ./npi bootstrap
BLOOM_CONFIG=../../ ./npi fetch
BLOOM_CONFIG=../../ ./npi search-index
It may make sense to also update a datasource via cron. If you wanted to update a given datasource, run:
BLOOM_CONFIG=../../ ./npi fetch
BLOOM_CONFIG=../../ ./npi search-index
Every command will have the commands:
If you want to run multiple datasources at once, you can use the runner. If you built using the makefile, you'll already have an example of how the directories + config have to be setup to work at $GOPATH/bin/linux_amd64/datasources. From this directory, on a linux machine, just run ./runner to see the available commands.