IQSS / IQSS/dataverse

Feature Request/Idea: Improved Dataverse and Dataset Metrics

Open
#9,666 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Metrics + Reports Type: Feature User Role: Curator
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
I've been using (again) my for the past few days my Dataverse and I find recurrently the need of having more access metrics to both my dataverses and also datasets. Metrics such as total number of views and more importantly, and this is really important, who viewed or access it: For instance a list of users with their emails, phone numbers, or/and even IP addresses.

My open project related to this request can be found here.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
This is intended for API users, Guests, SysAdmin

What inspired the request?
I do work in open environments and this includes doing my scientific research In an open format. This means publishing frequent updates on "social media" and also on messaging apps such as WhatsApp and Telegram.
And I need to know my audiences, more, I need to know my audiences and where is being used my authored work.

What existing behavior do you want changed?
Add more metrics options on the metrics floating tab to the left of the webpage.

Any brand new behavior do you want to add to Dataverse?
total number of views
a list of users who views/ access it
a list of users who downloaded my datasets

Any open or closed issues related to this feature request?
no

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing metrics floating tab and current Dataverse and dataset metrics behavior. The issue does not name files, tests, or entry points, so first determine where metrics are implemented and clarify the privacy and access requirements for view, user, download, and IP data. Done criteria are not defined beyond adding these metric options.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.