Issue regarding display of number of files in a dataset
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
Considering a dataset (for example : https://dorel.univ-lorraine.fr/dataset.xhtml?persistentId=doi:10.12763/VWKNSA) with more than ten files, the first 10 files are displayed on page 1, and it is then possible to use the paginator to get access to other files ; you get then to page 2,3,4 and so on, depending of the total number of files.
If we then want to get a file using the search engine, we get, at the top of the list, the number of files displayed on this page, among the total amount of files for this particular dataset.
Example, for a dataset with 17 files, you get :
- 1 to 10 of 17 files for the first page
- 11 to 17 of 17 files for the second page
- When does this issue occur?
If we then use the search engine on the second or third page, as expected fewer files are on display (for example 8), and on top of the list, we have "11 to 8 of 8 files" (for page 2), which does not mean anything : it seems that the first number refers to the number of the first file of the page.
-
To whom does it occur (all users, curators, superusers)?
It occurs to all kind of users, including superusers. -
What did you expect to happen?
It would be better to see, refering to this particular dataset, '1 to 8 of 8 files', instead of '11 to 8 of 8 files'.
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
Reproduce the dataset file search on a later results page using the linked dataset example, and inspect the pagination and file-count display entry points. Confirm that the result range uses the filtered list rather than the dataset page offset; done means the example shows "1 to 8 of 8 files" and similar counts are correct for all users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100