Feature Request/Idea: Dataverse metrics bar at sub-dataverse level

[philippconzett]

Overview of the Feature Request
Sub-collections (sub-dataverses) play an important role in many Dataverse installations. For example, in the national DataverseNO repository, each consortium member institutions has their own institutional collection. For the managers and users of such collections it's useful to have good usage metrics at different levels. As of v6.3, Dataverse already provides download and Make Data Count metrics in the GUI at the installation/top-level collection level, the dataset level, and the file level. Here's an example from the dataset level:

In addition, we need usage metrics bar in the GUI at sub-collection level. This helps collection managers and other stakeholder involved in sub-collections promote data sharing and in general increase the use of the sub-collection.

What kind of user is the feature intended for?
Collection Manager, Guest

What inspired the request?
Requests from DataverseNO collection managers.

What existing behavior do you want changed?
Usage metrics in the GUI not being available at sub-collection level.

Any brand-new behavior do you want to add to Dataverse?
Yes, a new metrics bar in the GUI at sub-collection level.

Any open or closed issues related to this feature request?
IQSS/dataverse#3527

[pdurbin]

It should be relatively straightforward to call into the Metrics API to get downloads for a collection. Other metrics are available.

To get a download count from https://dataverse.no/dataverse/uio you'd hit https://dataverse.no/api/info/metrics/downloads?parentAlias=uio

@philippconzett is downloads enough for a start? Are any other metrics exposed by that API of interest? Any thoughts on how you'd like this to look?

One thing to keep in mind is that the Metrics API doesn't use Make Data Count. It uses Dataverse's traditional method of counting downloads.

[philippconzett]

Thanks, @pdurbin! Sure, let's start with downloads metrics. I think a metrics bar like the one displayed on the landing page of the top/root level collection / the entire dataverse would be good: