Differences

This shows you the differences between two versions of the page.

--- documentation:software:whiterabbit [2019/02/26 19:34] – ericavoss
+++ documentation:software:whiterabbit [2020/02/18 14:12] (current) – maximmoinat
@@ Line 1: / Line 1: @@
 ====== WhiteRabbit ======
+**NOTICE FEB 2020:** the current documentation can be found on Github
+http://ohdsi.github.io/WhiteRabbit
 {{ :documentation:software:whiterabbitlogo.png |}}
@@ Line 9: / Line 14: @@
 WhiteRabbit is a software tool to help prepare for ETLs (Extraction, Transformation, Loading) of
 longitudinal healthcare databases into the [[documentation:cdm:single-page|Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM)]]. The source data can be in
-comma-separated text files, or in a database (MySQL, SQL Server, Oracle, PostgreSQL, Microsoft APS, Microsoft Access, Amazon RedShift). Note that the CDM will need to be in one of a limited set of database platforms (SQL Server, Oracle, PostgreSQL, Microsoft APS, Amazon RedShift).
+comma-separated text files, or in a database (MySQL, SQL Server, Oracle, PostgreSQL, Microsoft APS, Microsoft Access, Amazon RedShift, Google BigQuery). Note that the CDM will need to be in one of a limited set of database platforms (SQL Server, Oracle, PostgreSQL, Microsoft APS, Amazon RedShift, Google BigQuery).
 WhiteRabbit’s main function is to perform a scan of the source data, providing detailed
@@ Line 52: / Line 57: @@
 Here you can specify the location of the source data. The following source types are supported:
-delimited text files, MySQL, Oracle, SQL Server, and PostgreSQL. Below are connection
+delimited text files, MySQL, Oracle, SQL Server, PostgreSQL, and Google BigQuery. Below are connection
 instructions for each data type of data source. Once you have entered the necessary
 information, the “Test connection” button can ensure a connection can be made.
@@ Line 90: / Line 95: @@
 **PostgreSQL**
   * //**Server location:**// this field contains the host name and database name (<host>/<database>)
   * //**User name:**// name of the user used to log into the server
   * //**Password:**// password for the supplied user name
   * //**Database name:**// this field contains the schema containing the source tables
+**Google BigQuery**
+Google BigQuery (GBQ) supports two different connection/authentication methods -- application default credentials and service account authentication. The former method is considered more secure because it writes auditing events to stackdriver. The specific method used is determined by the arguments provided to the configuration panel as described below.
+Authentication via application default credentials:
+When using application default credentials authentication, you must run the following gcloud command in the user account only once: 'gcloud auth application-default login' (do not include the single quote characters). An application key is written to ~/.config/gcloud/application_default_credentails.json.
+  * //**Server location:**// name of the GBQ ProjectID
+  * //**User name:**// not used
+  * //**Password:**// not used
+  * //**Database name:**// data set name within ProjectID named in Server location field
+Authentication via service account credentials:
+  * //**Server location:**// name of GBQ ProjectID
+  * //**User name:**// OAuth service account email address
+  * //**Password:**// OAuth private key path (file location of private key JSON file). Must be a valid full file pathname
+  * //**Database name:**// data set name within ProjectID named in Server location field
 ==== Scanning a Database ====