March 30, 2017 at 5:11 pm
#101
Anonymous
Inactive
CODAP does log user actions and it also uses Google analytics. But I don’t think anyone has tried to make use of either of these when a CODAP document is embedded in a web page.
To add to this:
- The production instance of CODAP automatically logs events to a log server that was built by Concord Consortium. The events logged correspond to user initiated actions. There is a high correspondence between events that are logged and events that are undoable, you can get a sense of what is logged by opening CODAP and observing the UNDO events (by mousing over the “Undo” button and observing the tooltip that comes up.)
- Although CODAP can store and retrieve files from several servers that require authorization, it does not natively require authentication. A consequence of this is that events recorded to the Log Server are anonymous. There is a session key that can be used to correlate events (although, due to a bug, this key is at this moment not always present in the log message.)
- The production instance of CODAP, meaning https://codap.concord.org/releases/latest, is bound to the Concord Consortium log server, but this is configurable. Another instance could be instantiated that logged to a different log server.
- Google analytics is also enabled for the production instance of CODAP. This events recorded and accessible through the Google analytics reporting include all the usual data as for any web site. I think this data would be considered proprietary to Concord Consortium.
- If you created a separate instance of CODAP with the intention to configure a separate Google Analytics dataset this would require a small code modification.
I hope this addresses your questions. If you can provide more information about your use case, we may be able to provide a specific answer.