ga4gh / ga4gh/task-execution-schemas

DIRECTORY Output processing lack of clarification

Open
#236 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
95
Forks
32
PR merge metrics
No merged PRs in 30d

Description

The standard doesn't clarify how should the outputs of `type` `DIRECTORY` be processed, whether output specified as `DIRECTORY` should be recursively uploaded file by file, or whether outputs can be treated and/or specified as `ARCHIVE` or similar to make the default choice for the TES server to `tar` the directory and curl the archive to the specified `url` , I am working on an implementation of the TES Server, [tesp-api](https://github.com/CESNET/tesp-api).

Contributor guide

Open the contributing guide

Research direction

Start with the standard's definition of `DIRECTORY` outputs and compare it with the implementation context described for tesp-api. Resolve whether directories are uploaded recursively or packaged as archives, then update the standard so the required processing and URL behavior are explicit and implementers can verify compliance.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.