Publishing Workflow

Events are only sent from Harris if their creators check a box labeled "Real Time Feed" in the Harris UI. Supposedly. Harris users can force the update of a *single* event by logging into Sundial and editing it; on the edit event page, a brief summary appears with the Harris Event ID and a refresh button.

Each Harris orgCode =~ /COU[A-Z]?/ maps to a user in Sundial named Harris_Feed_$0. If no such user is found for the orgCode, we default to the COU user. Each user has a default permissions structure [like any Sundial user] which is applied to their events; they also have an entry in a table called User_Autopublish, which specifies one or more populations and statuses. In this way, events can be automatically suggested (this is our policy for clients we haven't made specific arrangements with), or approved (UAR, CCAAD, etc.).

Autopublish doesn't have any UI at the moment, only SQL. Bad form!