-
Notifications
You must be signed in to change notification settings - Fork 109
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
Implement a UI component to trigger asynchronous operations on a resource #1559
Comments
Upon closing the modal, the execution state is to be captured in a separate modal (like export data) allowing user to perform a new upload action. @giohappy Kindly correct me if I'm missing something from our last discussion on this issue |
Resurrecting this old analysis.
I think you're correct. |
@allyoucanmap I have edited the description on the base of our call. |
Introduction
We want to replace the following legacy forms:
end restore the "replace" operation for datasets and documents, which wasn't ported from GN 3.
All these operations should provide a similar UI to configure, execute, and monitor the execution of an operation.
State and behavior
All these operations are asynchronous and blocking:
executions requests
endpoint to obtain the status of the operation, similar to the current upload operationThis kind of operation falls inside the lower right quadrant of the following matrix:
UI
The component will show in a modal window with a minimal design. In general, it encompasses 4 states:
Being a blocking operation, the modal cannot be closed until the operation is completed or canceled.
When the resource viewer is opened the client will check the execution request obtained from the REST API response for the resource. If there's an ongoing operation for the resource, the blocking modal for the specific operation will be shown.
State 1
State 2
State 3
State 4
Implementation notes
The component can be used inside any page of the GeoNode client. For the moment it will be adopted inside detail pages, but in the future, we could adopt it also for operations on the catalog.
The text was updated successfully, but these errors were encountered: