Closed landreev closed 1 month ago
The "anonymized access" have been configured in demo. Asked Sonia to take a look/confirm. Another request from her: create another S3 bucket with a very large individual file size limit, so that we don't have to keep using the one that was created specifically for MIT when other collections need to upload giant files.
Dataverse 6.3 has been deployed on demo.dataverse.org. Please note that technically deploying on demo is one of the steps on our release checklist; but for whatever reason it was not done back then.
@sbarbosadataverse
This is the new storage volume with a 300G file size limit that has been created per request from Curation, so that they don't have to use the dedicated MIT volume whenever a collection needs to upload giant files:
I will switch any such non-MIT collections and already existing files to this volume separately (will confirm).
One extra volume, S3Direct
has been created, which can be used for enabling direct upload for users without increasing the file size limit:
There were a couple more things that ended up being time-consuming: had to look into some strange AWS issues with LTS last week; also, an exotic user upload issue. Documenting relevant info in the google docs.
Closing.
Regularly scheduled Devops issue.
One outstanding task transferred from last sprint:
Anonymized/double blind review feature need to be enabled in demo. From the guide:
curl -X PUT -d 'author, datasetContact, contributor, depositor, grantNumber, publication' http://localhost:8080/api/admin/settings/:AnonymizedFieldTypeNames
Related