We don't want to rewrite the whole UI. Jena already does a good job, so we only want to add a few functionalities to their UI.
Somewhere close to the run button ⏯️ , there should be a gear ⚙️ that enables configuring the query execution.
[ ] A range slide 🎚️ for timeout or limit. When active it enables preemptive query by sending the values to the remote Sage x Jena server.
[ ] A checkbox ✔️ to run the query automatically as responses arrive and the query is not over. It should be possible to stop such automatic running at any time either by unchecking the box, or clicking the run button again ⏸️.
[ ] A state field 📝 allows user to copy/past Sage metadata in order to resume their query execution. The field is automatically filled by the response's state if the query didn't change between its sending and the receipt of its results. If it changed, the result should still be available but with a warning (⚠️ the query seem to have changed, the state might not be relevant anymore).
We don't want to rewrite the whole UI. Jena already does a good job, so we only want to add a few functionalities to their UI.
Somewhere close to the run button ⏯️ , there should be a gear ⚙️ that enables configuring the query execution.
timeout
orlimit
. When active it enables preemptive query by sending the values to the remoteSage x Jena
server.the query seem to have changed, the state might not be relevant anymore
).