Hi Devin,
my suggested approach was to use the database only as frontend, because it provides an interface which is easy to customise to your needs (e.g. search, metadata displayed, a grid layout etc)
Each file should be its own activity (like it my demo course), I.e. you’ll track in each activity, not in the database.
Here’s what I wrote:
„Each file should then be configured with activity completion set to „require view“. This will enable you to easily track the first time a user opened the file. And each additional time can be seen in the logs.“
I am not aware that a report is available for the database itself.
Hope this helps!
Stefan
my suggested approach was to use the database only as frontend, because it provides an interface which is easy to customise to your needs (e.g. search, metadata displayed, a grid layout etc)
Each file should be its own activity (like it my demo course), I.e. you’ll track in each activity, not in the database.
Here’s what I wrote:
„Each file should then be configured with activity completion set to „require view“. This will enable you to easily track the first time a user opened the file. And each additional time can be seen in the logs.“
I am not aware that a report is available for the database itself.
Hope this helps!
Stefan