Falcony database differences compared to audits.io

This article describes the main differences between Falcony database structure compared to audits.io database structure. If you had been using audits.io analytics database connection this article should help how to transform existing database queries to adhere to Falcony structure.

Audit answers

In audits.io audit answers are stored in answer table
In Falcony the audit answers (as well as observation answers) are stored in observation_answer table

Audit select question values

In audits.io the select question values are stored in value_choices column of the answer table
In Falcony these answers are stored answer_choice table which holds a relationship to observation_answer as well as to observation_question_choice table.

Audit templates

In audits.io audit templates are stored in template table
In Falcony the audit templates (as well as observation templates) are stored in observation_category table

Places / targets

In audits.io the location in which the audit was conducted is stored in target table
In Falcony the location in which the audit was conducted is stored in place table

Sections / question groups

In audits.io each section / question group is stored in section table
In Falcony each section / question group is stored in observation_question_group table

Questions

In audits.io each audit question is stored in question table
In Falcony each audit question is stored in observation_question table
In audits.io each question can only belong to one section / question group. In Falcony this relationship is many-to-many and observation_question_group_question table is used for this relationship.