Routines for ingesting metadata to a CanDIG repository
A Python package for batch ingestion and update of clinical and pipeline metadata of candig-server.
For more information related to the setup of a candig-server instance, check out https://candig-server.readthedocs.io/
You may also refer to the SETUP.rst at this repo, from https://github.com/CanDIG/candig-ingest/blob/develop/setup.py
This tool is not for standalone use. You must have an existing virtual environment where a candig-server is installed.
Once you are in the virtual environment of where your candig-server is, activate it, and run
pip install candig-ingest
Prepare data for ingestion
Once the package is installed, you may batch ingest or update data. The candig-ingest requires a specially-formatted json file for this purpose. This page describes the format of the data: https://candig-server.readthedocs.io/en/stable/data.html#clinical-and-pipeline-metadata
To help you get started quicker, we provide a few sample json files that are ready to use, you may retrieve them from https://github.com/CanDIG/candig-ingest/tree/develop/candig/ingest/mock_data
Alternatively, if you need to export data from RedCap APIs, we provide a conversion script that is available from https://github.com/CanDIG/redcap-cloud
Usage: ingest [-h Help] [-v Version] [-d Description] [--overwrite] [-p LoggingPath] <path_to_database> <dataset_name> <metadata_json>
As you can see from above, the ingest command only has 3 mandatory parameters.
If we download a mock data file from the github repo linked above, you will run something like below.
You may want to double check if you are in your candig-server’s virtualenv.
wget https://raw.githubusercontent.com/CanDIG/candig-ingest/develop/candig/ingest/mock_data/clinical_metadata_tier1.json ingest candig-example-data/registry.db mock1 clinical_metadata_tier1.json -d "A collection of data from Mars"
You may see some warning messages that say “Skipped: Missing 1 or more primary identifiers for record …” if you use the mock data, this is normal. We designed the mock data to be faulty on purpose. For production data, however, you should not see this message.
If you want to add a text description to your dataset, you should use the -d flag, note that the description cannot be updated at this time once the dataset is created. This is optional, however.
Assume you have data ingested to a database’s dataset already, and would like to update them in batch.
If this applies to you, you should specify the –overwrite flag, this will update all records.
If you do not see specify this flag, the system will warn you that a record with the same identifier exists.
ingest candig-example-data/registry.db mock1 updated_data.json --overwrite
Note that the description of the dataset cannot be changed once it’s created, so a -d flag won’t do anything.
By default all the actions performed by candig-ingest are logged and stored as log files on the same directory the ingest was called.
You may choose another place to store the log files by passing the -p argument every time you run the command:
ingest candig-example-data/registry.db mock1 updated_data.json -p /home/user/Documents/logs
Questions and comments
Please open an issue here and let us know!
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size candig_ingest-1.5.0-py3-none-any.whl (27.7 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size candig-ingest-1.5.0.tar.gz (29.3 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for candig_ingest-1.5.0-py3-none-any.whl