Interface

Overview


DataMine allows you to run custom queries which allows you to easily access and manipulate your raw data. As your write each query, everything is saved dynamically to our servers which allows you to pick up where you left off from any device. Results will be available for up to 7 days after running a query.

Note Queries are unique to each user and not shared across organizations.

Overview

Add a New Query


To add a query:

  1. Log into your dashboard and navigate to EXPLORATION > DATAMINE > ADD A NEW QUERY.
  2. Give a name to your query which is easily identifiable.
  3. Start typing your HQL query. Your progress is saved automatically.
  4. Hit RUN once you are finished with your query.

Add Query

Renaming a Query


To edit a query:

  1. Log into your dashboard and navigate to EXPLORATION > DATAMINE.
  2. Select the query you want to edit.
  3. Hover over the query and select the pencil icon to edit the name of your query.
  4. You can also make modifications to your query if you have any changes.
  5. Hit RUN AGAIN after you have finished any modifications to your query.

Edit Query

Delete a Query


To delete a query:

  1. Log into your dashboard and navigate to EXPLORATION > DATAMINE.
  2. Select the query you want to delete.
  3. Hover over the query you want to delete and select the trash icon.
  4. Select YES to confirm deletion of the query.

Delete Query

Results Panel


To download your results:

  1. Log into your dashboard and navigate to EXPLORATION > DATAMINE and select your query.
  2. Hit RUN if your query has not run.
  3. Select DOWNLOAD to download your query results as a CSV.

Note You can select the dropdown next to DOWNLOAD to select to download as either CSV or Excel. Excel exports are limited to one million rows.

Download Query

CSV Format


Data Mine uses the following CSV format for exporting data from the system.

CSV Properties

  1. Columns delimited by ,
  2. Mapkeys are separated by :
  3. Array elements are separated by ;
  4. ,, :, and ; are all escaped by \

Validation Rules

  1. Only string type columns are allowed to have data of empty string.
  2. NULL data value is represented by \N (backslash capital n). Any column type can be NULL.
  3. Extra columns in a row are ignored.
  4. Unspecified columns are treated as NULL.
  5. Column types are enforced.
  6. Arrays elements are separated by ;
  7. Mapkeys are separated by :.
  8. Delimiters are escaped by \.
  9. Quoting of fields is not supported.
  10. Leading space between field and delimiter is not allowed unless column is of type string.

Example Validations

string | int | int valid rule comment
abc,1,2 Yes. 5 Column data types are correct.
,1,2 Yes. 1 The first column is a string and is allowed to be empty.
abc,,2 No. 1 The second column is an int and is not allowed to be empty.
abc,\N,2 Yes. 2 The second column is an int and is set to NULL.
abc,1,2,3,4 Yes. 3 More columns in row than in table is ok.
abc Yes. 4 Less columns in row than in table is ok. The tailing columns will have the value of NULL.
abc,foo,3 No 5 The second column value foo is not an integer.
one\, two\, and three,4,5 Yes 8 The comma in the string column is escaped by \.
"abc","2","3" No 9 Fields can not be quoted.
abc, 2,3 No 5,10 The leading space in column two is not allowed.
array | int valid rule comment
abc;def;hij,1 Yes. 6
abc;;hij,2 Yes. 6,1 The array elements are checked for validity. Since the array is a string an empty array element is valid.
one\;two;three\;four,3 Yes. 6,8 The semicolon is escaped by \.
array | string valid rule comment
1;2;3,abc Yes. 6
1;hi;3,abc No. 6,5 Array elements are type enforced as well.
1;;3,abc No. 6,1 The second element in the array can not be empty because the array is of type int.
1;\N;3,abc Yes. 6,2 The second element in the array is represented as NULL.