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.

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

Implementing the PACS Query/Retrieve (Q/R) to use oxidicom. #1107

Open
PintoGideon opened this issue Mar 13, 2024 · 2 comments
Open

Implementing the PACS Query/Retrieve (Q/R) to use oxidicom. #1107

PintoGideon opened this issue Mar 13, 2024 · 2 comments
Assignees

Comments

@PintoGideon
Copy link
Collaborator

PintoGideon commented Mar 13, 2024

A detailed explaination of how Pacs Query Retrieve works is documented here:

https://github.com/FNNDSC/oxidicom/blob/master/CUSTOM_SPEC.md#suggested-client-implementation

@PintoGideon PintoGideon changed the title Possible re-implementation of the PACS Q/R Re-implementation of the PACS Q/R Mar 27, 2024
@PintoGideon PintoGideon changed the title Re-implementation of the PACS Q/R Implementing the PACS Query/Retrieve (Q/R) to use oxidicom. Mar 27, 2024
@PintoGideon
Copy link
Collaborator Author

When users initiate a retrieve one after the other, the UI currently relies solely on the file count in Cube to determine whether a retrieve operation was performed. However, this approach presents an issue: if the first retrieve is still in progress when the second retrieve is initiated, the UI displays the spinner due to the absence of files in Cube. Upon page refresh, the UI resumes the first retrieve operation, potentially leading to confusion regarding the status of the retrieves.

@PintoGideon
Copy link
Collaborator Author

The Series Card component currently lacks responsiveness, particularly on smaller screens. When viewed on devices with limited screen width, the gear icon within the card disappears behind the buttons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant