Open-EO / Open-EO/openeo-python-client
user-friendly job-database view
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Problem
The job database now contains columns that are purely internal bookkeeping (running_start_time, cpu, memory, duration). Users who open their CSV or inspect job_db.df see these alongside their own data columns, which adds noise and can be confusing.
Could we expose a simplified "user view" of the database while keeping a full "developer view" internally?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the job_db.df object and the CSV view mentioned in the issue to identify how internal columns are currently exposed. Clarify which columns belong in the user view versus the developer view, then verify that users see only the simplified columns while internal bookkeeping remains available to the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100