IQSS / IQSS/dataverse-frontend
Advanced Search: object "status" filter
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
Allow to filter for object status (Unpublished, Published, Draft, In revision) in the advanced search menu
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Curators
What inspired the request?
Request from curators to be able to set up all filters in the advanced search rather than in two steps
What existing behavior do you want changed?
Expand Advanced Search interface to be able to filter on the object status
Any open or closed issues related to this feature request?
Original JSF UI issue :
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 at the Advanced Search menu in the frontend and review the related original JSF UI issue, dataverse issue 9993, for expected behavior. Add filtering for Unpublished, Published, Draft, and In revision object statuses, and verify that curators can configure this filter alongside the existing advanced-search filters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100