Querying Admin Data

ROAR's admin data is automatically exported from Firestore to BigQuery for analysis and reporting. This document explains how to query admin data in BigQuery.

Key Differences from Assessment Data

Admin data queries follow the same principles as querying assessment data, but with these important differences:

  • Location: Admin data is stored in a separate BigQuery project (gse-roar-admin) under the admin dataset
  • Privacy: Admin data includes personally identifiable information (PII) that requires special handling
  • Access: Admin data access is more restricted due to privacy requirements

Shared and Unique Tables

Shared Tables

These tables exist in both admin and assessment datasets with identical schemas:

  • classes
  • districts
  • families
  • groups
  • schools

Users Table Differences

The users table exists in both datasets but with different schemas:

  • Admin dataset (gse-roar-admin.admin.users): Contains complete user information including PII
  • Assessment dataset (gse-roar-assessment.assessment.users): PII fields are omitted for privacy

Available Tables

The admin dataset (gse-roar-admin.admin) contains the following tables: