Course/Registration Structure #

This diagram shows the fundamental relationship of the most important tables in typical course registration and launch.

erDiagram COURSE ||--|| "COURSE_PROVIDER" :"" COURSE ||--o{ "REGISTRATION" :"" REALM ||--o{ "COURSE_PROVIDER" :"SCORM Cloud Apps" REALM ||--o{ "REALM USER" :"" REGISTRATION ||--|| "REALM USER" :"" USER ||--o{ "REALM USER" : "A user can be in multiple Bright realms" "USER" ||--o{ "API KEY" : ""

API Keys can be bound to a “realm” or “course provider” when created.

Data Tables #

erDiagram COURSE { string type "'ScormCloudApp'" uuid course_guid string title } USER { string email_address }

erDiagram REALM { string name uuid realm_guid string realm_secret_key } COURSE_PROVIDER { string sc_app_id "SCORM Cloud APP ID" string sc_secret_key "SCORM Cloud Secret Key" }

erDiagram REGISTRATION { uuid course_guid string learner_id "In most cases, email address" id realm_user_id FK "Bright internal ID" id course_id FK "Bright internal ID" string complete "complete|incomplete|unknown" string success "passed|failed|unknown" float score }