Issue 17547

NHM London looking for means of compiling dataset activity for regular reporting

Reporter: thirsch
Assignee: thirsch
Type: NewFeature
Summary: NHM London looking for means of compiling dataset activity for regular reporting
Environment: Dataset 'activity' pages
Priority: Major
Resolution: Duplicate
Status: Closed
Created: 2015-04-16 07:53:21.216
Updated: 2016-06-03 16:25:22.527
Resolved: 2016-06-03 16:25:22.453
Description: Vince Smith from Natural History Museum, London needs to report regularly on the usage of their newly-published dataset and requested access to Google Analytics for this purpose, which we have given him. When I pointed out the Activity tab on the dataset page as an additional source of information he replied as follows:

"Thanks Tim,

Yes - I've seen the tab - the stats are very impressive. More so than direct from the NHM portal. I just need a sustainable way (beyond me having to remember to click on the tab) to incorporate these into the reporting stats that I use for the NHM portal.

Thanks again,


It raises the point made by many data publishers that having access to regular, aggregated usage updates from GBIF would be very helpful in demonstrating the value of publishing their datasets on]]>

Created: 2015-04-16 09:59:36.019
Updated: 2015-04-16 10:00:40.239
What kind of aggregated statistics would be desirable then?
Would it help if we added some stats like the following:
 - number of downloads & total records per year & month
 - number of downloaded records per year per kingdom
 - number of downloaded records per year per country of occurrence
 - breakdown of users origin or other user attribute? we would need to capture that for every registered user

Or would an Activity tab for the publisher aggregating all its published datasets be more useful?

Comment: [] all of these sound good options but rather than making assumptions, I suggest conducting a quick informal needs-capture inquiry with a small number of key institutions who have expressed interest in this issue (NHM, Canadian Museum and Kew are ones I am aware of). I am happy to organise this and report back the result, but what would help is if you could list the options - the above and any more with some indication of which are straightforward and which require more effort, so we can set some realistic expectations. 
Created: 2015-04-16 10:20:28.363
Updated: 2015-04-16 10:20:28.363

Created: 2015-04-16 12:32:54.774
Updated: 2015-04-16 12:32:54.774
[] An informal inquiry sounds very good. As for available options and amount of work I see that:
 - any information in our registry is readily available. That is number of downloads & total records by date for datasets and aggregated for publishers. Doing graphs by time (month or year) should be straight forward
 - grouping by a downloading users home country would technically be doable as we require it at user registration time (not sure if this has other sensitive personal rights implications)
 - grouping records by kingdom, country of occurrences or other occurrence properties is far more demanding and we should probably not advertise this as doable, but it might still be interesting to know if any of those questions are high on the shopping list of those organisations
 - getting stats about other data access than downloads (e.g. portal page views or external use of our non download webservices) is a completely new endeavour for us which we should avoid at this stage

Comment: Thanks [], this is very helpful. I suggest we leave this issue open and assign it to me (I've done that) and once I have some feedback to report I will compile it into a further comment then hand it back to you guys to prioritize. OK?
Created: 2015-04-16 12:51:12.816
Updated: 2015-04-16 12:51:12.816

Comment: merged into POR-1651
Created: 2016-06-03 16:25:22.514
Updated: 2016-06-03 16:25:22.514