Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate per-project matrix service output files in Data Browser S3 bucket #351

Closed
theathorn opened this issue Jul 22, 2019 · 6 comments
Closed
Assignees

Comments

@theathorn
Copy link

Moved from https://app.zenhub.com/workspaces/dcp-5ac7bcf9465cb172b77760d9/issues/databiosphere/azul/1098

@brianraymor
Copy link

Isn't this a duplicate of #331 which has already been addressed?

@theathorn
Copy link
Author

There's a requirement to generate the matrix output files in the specified Data Browser S3 bucket with the correct Content-Dispostion header as per https://app.zenhub.com/workspaces/dcp-5ac7bcf9465cb172b77760d9/issues/databiosphere/azul/1098 such that they can be directly downloaded by the user. #331 was closed 3 weeks ago which appears to pre-date this agreement (made during the Data Browser meeting of 7/15/19).

@theathorn
Copy link
Author

You also need to set cache control headers as per https://app.zenhub.com/workspaces/dcp-5ac7bcf9465cb172b77760d9/issues/databiosphere/azul/1146

@mckinsel
Copy link
Contributor

Just some clarification of what this ticket means: we have a plan to automate the creation of project matrices as part of ETL, and that is recorded in #352 . After further discussions with the data browser team, we decided it made sense to directly put the results of that automation into an S3 bucket that the browser reads to populate its matrix download buttons. But, there is a little more work for that than just copying results to a bucket. There is an expected structure and some header that need to be set. This issue represents that work.

@brianraymor
Copy link

@mckinsel - I think that we should close this issue since we have tracking issues for specific projects requiring manual intervention in Q3. We can then focus on #352 in Q4M1.

@brianraymor
Copy link

No objections to closing. Until #352 is addressed, individual issues will be opened for incoming Barcelona data sets for easier tracking by DataOps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants