You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The component will be able to receive a configuration object when instantiated, which might contain:
the type of operation (d, name, sync/async)
the API endpoints
etc.
In the case of an asynchronous operation:
The executions requests endpoint will be queried to obtain the status of the operation, as we have for uploads.
Users can close and reopen the modal window without losing the state of the operation.
The operation can be canceled
UI
The component will show in a modal window with a minimal design. In general, it encompasses 4 states:
File selection
Ready to execute
In progress
Completed
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.
@allyoucanmap please add any additional note and comment.
The text was updated successfully, but these errors were encountered:
giohappy
changed the title
Implement UI componente for trigger asynchronous operations on a resource
Implement a UI component to trigger asynchronous operations on a resource
Sep 12, 2023
Users can close and reopen the modal window without losing the state of the operation.
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.
Any manner of error during the upload process is expected to be handled by the backend. The error is shown as an info icon with a tooltip next to file as shown in the screenshot above. And a loading spinner icon when the execution is in progress.
@giohappy Kindly correct me if I'm missing something from our last discussion on this issue
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
The component will be able to receive a configuration object when instantiated, which might contain:
In the case of an asynchronous operation:
executions requests
endpoint will be queried to obtain the status of the operation, as we have for uploads.UI
The component will show in a modal window with a minimal design. In general, it encompasses 4 states:
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.
@allyoucanmap please add any additional note and comment.
The text was updated successfully, but these errors were encountered: