[FEAT-Lambda]: Create Lambda Output Structure (for s3 files)
Open
@martyheynbah is already working on this.
Since Jun 3, 2026.
3SP
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- create system to track and structure how outputs from the lambda scripts are nested in s3
- rethink naming conventions for each individual lambda / script
- For example there will be only 1 LCG output per study so the output in s3 can be named something like:
.../{project_id}_lcg.csv, but the hydrograph script can produce mutliple outpurs for a single study so there will need to a identifier appended to the naming convention.../{project_id}_{unique_identifer}_hydrograph.csv
- For example there will be only 1 LCG output per study so the output in s3 can be named something like:
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.
Assessment
This issue has not been assessed yet.