Ticket #248 (new story)

Opened 13 years ago

Last modified 13 years ago

Portal queries user actions

Reported by: sylvia Owned by: anonymous
Priority: major Milestone:
Component: generic Version:
Keywords: portal Cc:
Time planned: Time remaining:
Time spent:

Description (last modified by sylvia) (diff)

This is to be able to provide a monthly statistic to WP4 incorporating the full span of user activities.

Discuss with WP4, how statistics need to be presented in the end (most likely grouping by country, school, teacher)

Change History

comment:1 Changed 13 years ago by sylvia

  • Type changed from defect to story
  • Description modified (diff)

comment:2 Changed 13 years ago by sylvia

  • Keywords portal added

comment:3 Changed 13 years ago by tarmo

Here's a (off the top of my head) list of actions that users can do in the Toolbox on content that is downloaded from the Portal (assuming it is open content). The list may change.

  • view it (the metadata, that is)
  • play it (see the actual content)
  • use it in a VLE
  • add it to another collection (possibly a lesson plan)
  • remove it from another collection
  • write a Story about it
  • translate its metadata
  • translate its contents
  • create an improvement (same content, with fixes)
  • create a variation (essentially a different object)
  • start a project around the content
  • add the content to an ongoing project

And all of this can happen in any Toolbox in the network, since the object is accessible to all of them. So the actions are spread quite wide. But what the user who downloaded the content from the Portal does is stored in the same Toolbox. All these actions can be tracked from the server's access log. Within Zope's own object database, anything that makes changes to an object is stored and is thus retrievable.

Note: See TracTickets for help on using tickets.