Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Some API calls on a lot of documents provide twice the same resource #886

Open
1 task
pronguen opened this issue Aug 17, 2022 · 0 comments
Open
1 task

Some API calls on a lot of documents provide twice the same resource #886

pronguen opened this issue Aug 17, 2022 · 0 comments
Labels
bug Breaks something but is not blocking client request

Comments

@pronguen
Copy link
Contributor

Bug description:

Some API calls on a lot of documents provide twice the same resource.

Expected behavior:

Each resource is provided only once.

Steps to Reproduce:

  1. Launch https://susi.usi.ch/api/documents/?sort=relevance&q=documentType:%22coar:c_6501%22&size=50
  2. Open the next pages until page 12
  3. Some records are provided twice

Context

Server:

  • production (specify your instance if relevant)

Version:

Version of 15.04.2022

Context

See RT 241 for details and an concrete example
@pronguen pronguen added bug Breaks something but is not blocking p-Medium To set a medium priority. labels Aug 17, 2022
@PascalRepond PascalRepond removed the p-Medium To set a medium priority. label Apr 4, 2023
@PascalRepond PascalRepond moved this to Inbox in SONAR issues Apr 4, 2023
@PascalRepond PascalRepond added the stale Stale or no longer relevant label Apr 17, 2023
@github-actions github-actions bot removed the stale Stale or no longer relevant label Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Breaks something but is not blocking client request
Projects
SONAR issues
Status: Inbox
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pronguen @PascalRepond