IQSS / IQSS/dataverse

MyData API returns error for dataverseAdmin user on QA

Open
#12,385 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

SPA 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. Login as dataverseAdmin on QA, on the Modern UI or JSF frontend
  2. Go to the MyData Page
  3. The MyData API call returns an error

MyData API endpoint:
https://qa.dataverse.org/api/v1/mydata/retrieve?per_page=10&selected_page=1&role_ids=2&role_ids=3&role_ids=4&role_ids=5&role_ids=8&role_ids=12&role_ids=6&role_ids=13&role_ids=7&role_ids=1&userIdentifier=dataverseAdmin&dvobject_types=Dataverse&dvobject_types=Dataset&published_states=Published&published_states=Unpublished&published_states=Draft&published_states=Deaccessioned&published_states=In+Review

Response:
{
"success": false,
"error_message": "Sorry! There was an error with the search service."
}

  • When does this issue occur?
    For dataverseAdmin on QA. For other users, MyData works correctly

  • Which page(s) does it occurs on?
    Account Page -> MyData (Modern UI)

Which version of Dataverse are you using?
v. 6.10.1 build iqss-2
|
frontend version: 292a37430

Screenshots:
Image

Image

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

Start with the MyData API endpoint and reproduce the request as dataverseAdmin on QA, then inspect the server-side search-service error and relevant logs. The issue is done when the same MyData request succeeds for dataverseAdmin while preserving the existing behavior for other users.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.