Open-EO / Open-EO/openeo-python-driver

UX of deleted job results

Open
#349 2 comments 0 reactions 1 assignee View on GitHub

@soxofaan is already working on this.

Since Jan 6, 2025.

Dominant language
Python
Stars
12
Forks
8
Avg merge
6d 3h
Merged PRs (30d)
4

Description

I have some older job results in my batch job overview.
In the Web Editor, it says the results are not available any longer. This is generally fine, we discussed this before.
The UX is a bit weird though:

(1) The batch job result is still "finished" although no results can be requested.
Should the job status change to created once the results get deleted?
I think that would make a little more sense to me.

(2) Also, as the job results have been deleted and the UDP is still stored, I tried to queue the job again to get the results computed again. Unfortunately, if I queue again that seems to not initiate any actions. I have to create a new job from the metadata. Why?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.