Group list paging
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
We use the Shibboleth authorization in our Dataverse installation and we preload the research users and assign them to a researchers group that has the proper role. We currently have preloaded aprox 5000 researchers and notice very slow performance when editing the group in Dataverse. The action times out a couple of times before showing the list of members.
Any changes to the group results in a reload of the data. The save and cancel buttons are located on the bottom of the screen and thus requires to scroll through the entire list.
The user experience would be much improved if the group membership list would be paginated.
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 from the Dataverse group-editing view and trace how the membership list is loaded and reloaded after changes. Check the existing group and authorization entry points, then verify that a group with roughly 5,000 members loads in pages, avoids repeated timeouts, and leaves save and cancel accessible without scrolling through the entire list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100