IQSS / IQSS/dataverse

Unexpected filtering in "My Data" page/API

Open
#11,754 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug
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?

  1. Open "My Data" page

  2. Apply the "Publication Status" facet.

    Example: filter to 45 "In Review" datasets

    Image

    (Screenshot 1)

    Image

    (Screenshot 2)

  3. Note that other facet counts update accordingly. For example, "Unpublished" shows 27, which includes only those matching the current "In Review" filter AND are "Unpublished".

  4. Click "Unpublished." Instead of narrowing to 27, the results expand to all datasets that are either "In Review" OR "Unpublished" (Screenshot 3).

    Image

    (Screenshot 3)

What did you expect to happen?

I think that it would be more intuitive if the facet counts indicated the number of results after applying that facet.
E.g., in Screenshot 2, "Unpublished" should already display 736.

Note that on the main search page, facets display the same counts initially, but when multiple are applied, the results narrow (e.g., to 27) because facets there are combined with AND:

Image

Image)

Which version of Dataverse are you using?

v6.6

Any related open or closed issues to this bug report?

Not aware of any

Are you thinking about creating a pull request for this issue?

Possibly yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior on the My Data page using the Publication Status and Unpublished facets, then compare it with facet behavior on the main search page. Trace how selected facets and their counts are combined across the page/API; the work is done when multiple facets narrow results consistently and the displayed counts reflect the intended filtering.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, frontend, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.