You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am pasting here the documentation from CRM-6335, in case there is no other copy (passwords omitted).
We now have a central database for OC4IDS data and a set of queries to assess data quality.
To load data into the database, use the OC4IDS Database - Import Data notebook. The database follows similar conventions to Kingfisher Process and Views, but with fewer features. It has the following tables:
collection - equivalent to the collection table in Kingfisher Process with one row per collection.
projects - equivalent to the join of the release and data tables in Kingfisher Process with one row per project.
collection_check - similar to release_check in Kingfisher Process, but with one row per collection.
field_counts - equivalent to field_counts in Kingfisher Views
oc4ids_schema - a flattened version of the OC4IDS schema, for use in coverage queries
I am pasting here the documentation from CRM-6335, in case there is no other copy (passwords omitted).
We now have a central database for OC4IDS data and a set of queries to assess data quality.
To load data into the database, use the OC4IDS Database - Import Data notebook. The database follows similar conventions to Kingfisher Process and Views, but with fewer features. It has the following tables:
To analyze data and prepare feedback, use the OC4IDS Data Feedback Notebook. The queries in the notebook cover:
To query the database, use the following details for the read-only user:
Host: oc4ids-database-2.cuujgua4wses.us-east-1.rds.amazonaws.com
Port: 5432 (default)
User: readonly
Things to note:
Host: oc4ids-database-2.cuujgua4wses.us-east-1.rds.amazonaws.com
Port: 5432 (default)
User: postgres
In the event we need to build a fresh copy of the database on a new server, I've documented the steps in the OC4IDS Database - Setup notebook.
The text was updated successfully, but these errors were encountered: