Repository navigation
Tracking what class a user is in, for analytics #2
Description
Analytics in the user interfaces is keyed to the class the student is part of. We can modify the booking links in the manifest to have a query param that represents something meaningful to the analytics, so that someone accessing e.g. a spinner on course A, has the code '?course=A' and someone accessing the same hardware via course B's policy has the code '&course=B'. Add a description of this, with examples, to the documentation
Activity
timdrysdale commentedon Jan 24, 2023
A class will book according to one or more policies. Each policy contains one or more slots. Each slot references a UI set. That UI set references on ore more UI. The UI object contains a URL that can be modified to contain a static query parameter (i.e. not one we template) but one that we set in advance, and establish different UIsets for different classes, even if they eventually use the same user interface javascript, this way they get passed a different course code in the URL param.