Hi Huda,
Those kinds of user actions are logged, but the log events are anonymized so it would currently be impossible to pull out a specific stream of log events from our logs.
You have three options:
- We discuss a contract to extend CODAP to allow for an optional input that would be passed on as part of each log event. Then we could extract log reports from our database for you and have events grouped by that input value. Your system could pass whatever input value you wanted to attach to the logs (like a student ID).
- Host and run your own version of CODAP. Modify it so that you can inject some information about the user. Capture your own logs to your own server.
- Write a small plugin for CODAP that would monitor CODAP for events you care about and send those to your own log server. It might be possible for the plugin to retrieve some information about the student who is using your platform, so that information could be added to your own logs. This “plugin” could be code that runs in the webpage that is embedding CODAP rather than the traditional style of having an iframed plugin sitting inside of CODAP, which would also work.
I would recommend #3. It would require someone on your end to write the code for the plugin and to maintain your own database of log events, but with AI coding assistance this kind of thing is now possible for many with only minimal technical skills required. We have information about how to create plugins on our website and would be happy to answer questions.