This application allows you to rate clinical trials. You can retrieve trials to rank by searching for NCT ID or MeSH Term
You are encouraged to use rvm for Ruby version and gemset management. Once RVM is installed, switch to the correct Ruby and gemset as follows:
rvm use ruby-2.5.3@clinwiki --install --createThen, from the project root directory:
bundle install
bundle exec rake db:create
bundle exec rake db:migrateOnce the dependencies are installed and the database is initialized, you can run the server with:
bundle exec rails sNote that we are using dotenv to make the handling of database variables easier.
We use a handful of environment variables to run the server.
You can expose these when running locally by creating a .env
file in the project root level directory. Here's an example:
# needed to connect to aact
AACT_DATABASE_URL=postgres://aact:aact@aact-db.ctti-clinicaltrials.org:5432/aact
REDIS_URL=redis://127.0.0.1:6379/0
DATABASE_URL=postgres://postgres@localhost:5432/clinwiki
#Optional
JWT_EXPIRATION_TIME_SECS=86400 # JWT expiration timeNOTE: The use of the DATABASE_URL environment variable should prevent
the need for a database.yml file in when running the server in development
mode.
The AACT Clinical Trials Database provides data the data we use for clinical trials.
While the database is available online, you are encouraged to download a copy of the database for ease of access.
We maintain a separate postgres database for data related to users. Please refer to the Installation section for additional info.
If you don't have postgres installed locally, you can do so using homebrew:
brew install postgresWe use searchkick to enable search.
Follow the instructions in the searchkick docs for setting up Elasticsearch locally.
Indexing is performed in the background by Sidekiq. You can run Sidekiq as follows:
bundle exec sidekiq -C config/sidekiq.ymlNote that with about 32 concurrent workers, it should take roughly 8 hours to fully reindex.
It's also worth noting that we run a background job every ten seconds to
handle batch reindexing. This is important because it optimizes queries using
ActiveRecord's includes functionality. Refer to the Study model's
search_import scope for more details.
Scheduled jobs can be configured in ./config/schedule.yml.
To disable Auto indexing set env variables for sidekiq process:
AUTO_INDEX_LAST_DAYS=0
A full reindex can be performed by running:
bundle exec rake search:indexA development environments can bootstrap a subset of search results as follows:
bundle exec rake search:bootstrap_devSearching for studies is handled by Searchkick through the Studies model. Results are directly brokered through the Elasticsearch index, which brokers data from the annotation database along with the AACT database.
CSVs expect a header with the following format:
nct_id,Type,Value,Action
We support Tag as a type, with Add or Remove as an action.
For crowd values, there are two types of crowd values and both can use the 'Add' and 'Remove' options.
For native fields that are crowd overwriteable, Add will add or overwrite a crowd
definition for that field, and Remove will remove the crowd definition.
For crowd values that produce custom facets, the "Type" in the csv ("label" value in the UI) will be the name of the facet. The "Value" in the csv ("description" in the UI) is the value(s) in the facet. For multiple values of the crowd facet, enter as multiple lines or separated on a single line by '|' (example Type = "Karnofsky Score Allowed", Value = "100|90|80|70")
The CSV should be exported to the imports/ within the root project folder.
You can commit the CSV with the following workflow, which assumes
you have set up heroku's command line tools, and that the heroku
remote points to the clinwiki-prod project:
git add imports
git commit -m 'Added import file'# you can write any comment you'd like
git push origin master # add to clinwiki-org/clinwiki
git push heroku master # add to heroku -- this should kick off a deploy# if your file is in imports/foo.csv, $MY_FILE should be foo.csv
heroku run -a clinwiki-prod rake import:csv["$MY_FILE"]heroku run -a clinwiki-prod rake export:front_matter_csv > my-front-matter.csvMake sure you have a copy of cw-app located as a sibling of the root project
directory.
You can once you've installed vagrant,
you can install the vagrant VM by running vagrant up from the project
root directory.
You can access the vagrant instance via vagrant ssh.
The following scripts are available
| Script | Function |
|---|---|
./scripts/vagrant/server | runs the server through vagrant, serving the API at port 3000 |
./scripts/vagrant/worker | runs the worker within the vagrant server |
./scripts/vagrant/frontend | runs a hot-reloading version of the frontend |
We have already enqueued several tasks for the worker to run while provisioning Vagrant, but you will need to make sure to run the worker for those jobs to be handled.
In one vagrant SSH session, you will want to run the following:
cd /clinwki
./scripts/serverThis will expose localhost:3000 to API requests.
From another session, run the following:
cd /cw-app
yarn startThis will run a hot-reloading session of the cw-app frontend.
To make sure reindexing and the like are handled on save,
make sure to run ./scripts/worker in a separate session as well.
- Create a .env file in root with the following contents
AACT_DATABASE_URL=postgres://$AACT_USER:$AACT_PASS@aact-db.ctti-clinicaltrials.org:5432/aact
MAILGUN_API_KEY=""
MAILGUN_DOMAIN="localhost:3000"
CW_HOST="localhost:3000"
CLINWIKI_DOMAIN="localhost:3000"
SECRET_KEY_BASE="lkdfjgldgjkdflgjlkdfjgldfkjg"- Precompile assets
export$(cat .env | xargs)&& RAILS_ENV=production rake assets:precompile- Start server
export$(cat .env | xargs)&& RAILS_ENV=production rails s