Manually Repairing Bright Registration Data
Use Case
A course registration in Bright is "entangled" with its associated course provider. This is shown a few fields in the registration record itself:
course_guid = "mod0172bfd224-e2f6-4ec4-85fb-c81388577d94"
course_provider_id = "5" # referenced in the database.
type = "ScormCloudRegistration"
If you were going to "hard-code" values in a registration, the record must be 'de-entangled' from the course provider record.
This can be done by setting "ignore" to true
ignore=true
In this case, the record can no longer be crawled by Bright Server.
How to set the ignore flag
This field can be set by the Registration API or from the Registration Explorer.
Limitations
Stopping the registration from being refreshed includes refresh after launch.
