opengeospatial / opengeospatial/ogcapi-processes
Part 4: Define which submission types for jobs are actually needed
Open
Nobody has claimed this yet.
Part 4 (Job Management)
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
There are so many options to get async/sync results from /jobs and /jobs/:id/results. It should probably be limited to a small subset so that there are not X options for "the same thing.
Discussion started in https://github.com/opengeospatial/ogcapi-processes/pull/437#discussion_r1796403346_
Contributor guide
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 with the discussion linked from pull request 437 and review the /jobs and /jobs/:id/results endpoint references in this issue. The work is complete when the needed submission types are agreed on and the relevant specification is updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100