IQSS / IQSS/dataverse-frontend
Feature Request/Idea: Dataverse metrics bar at sub-dataverse level
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
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?
https://github.com/IQSS/dataverse/issues/3527
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing GUI metrics bars at installation, dataset, and file levels, then read related issue #3527 for context. Done means the GUI exposes a usage metrics bar for sub-dataverses for collection managers and guests, with the required metrics defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100