You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data publishers should not be penalized for success.
For data publishers that want to control their bandwidth costs, but still want to give "fast lane" access for high-volume, commercial users, S3's Requester Pays feature is a great option.
When this option is selected when publishing a file, the file will also be published in a Requester Pays bucket.
Since this is an option for advanced users, I think there's no need to go beyond exposing the file download link in the requester pays bucket, with instructions to use s3cmd CLI or a tool like s3browser.
Do you have an idea/mockup of how you'd display this in the resource UI? This is simple from a functional standpoint, but harder to display without cluttering the UX. Will definitely need the "How to use" blurb next to it.
Maybe we only show it on the individual resource explorer view, and keep it off the list views?
Zharktas
added a commit
to 6aika/ckanext-cloudstorage
that referenced
this issue
Dec 19, 2022
Data publishers should not be penalized for success.
For data publishers that want to control their bandwidth costs, but still want to give "fast lane" access for high-volume, commercial users, S3's Requester Pays feature is a great option.
When this option is selected when publishing a file, the file will also be published in a Requester Pays bucket.
Since this is an option for advanced users, I think there's no need to go beyond exposing the file download link in the requester pays bucket, with instructions to use s3cmd CLI or a tool like s3browser.
Note this is how Cornell university is distributing bulk data from arxiv.org - https://arxiv.org/help/bulk_data_s3
The text was updated successfully, but these errors were encountered: