Feature Request: enable to remove "Publication Year" facet
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
I would like to be able to manage the side facets in a more flexible way, especially I would like to be able to hide/disable them, mainly Publication year facet.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
This feature is intended for superuser or sysadmin role.
What inspired the request?
On harvester instances Publication year facet does not count harvested dataset, but only those created on harvester itself, like dataverses (collections). This makes this facet impractical and misleading
See also https://groups.google.com/g/dataverse-community/c/d2SRQjFK6Rs/m/8wBOlVJ1AgAJ
What existing behavior do you want changed?
Hard-coded facet Publication year.
Any brand new behavior do you want to add to Dataverse?
Probably curl action do disable Publication year facet.
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 locating the code that defines the hard-coded Publication year facet and review how facet settings are exposed to superusers or sysadmins. Clarify whether disabling it should be available through a curl/API action, then define completion as allowing that facet to be hidden without affecting other facets and documenting or testing the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100