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

Backup historical dataset files to S3 Glacier #2114

Open
14 tasks
rija opened this issue Dec 3, 2024 · 0 comments
Open
14 tasks

Backup historical dataset files to S3 Glacier #2114

rija opened this issue Dec 3, 2024 · 0 comments

Comments

@rija
Copy link
Contributor

rija commented Dec 3, 2024

User story

As a curator
I want dataset files on Wasabi to be backed up to S3 glacier
So that I can have peace of mind regarding the resilience of our existing data

Acceptance criteria

Given I have a dataset already published
and its files are on Wasabi
When I navigate to S3 glacier buckets for dataset cold storage
Then I can see all the files for that dataset

Given that all dataset files are backed up on S3 glacier
When I navigate to /site/term
Then I can see under the "Hosting statement" tab information about the backup process

Additional Info

We need to make sure with the backup process within the limit of for free egress transfer on Wasabi.
(aim for 25% of total stored data per month)

Product Backlog Item Ready Checklist

  • Business value is clearly articulated
  • Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
  • Dependencies are identified and no external dependencies would block this item from being completed
  • At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
  • This item is estimated and small enough to comfortably be completed in one sprint
  • Acceptance criteria are clear and testable
  • Performance criteria, if any, are defined and testable
  • The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

  • Item(s) in increment pass all Acceptance Criteria
  • Code is refactored to best practices and coding standards
  • Documentation is updated as needed
  • Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
  • No deviation from the team technology stack and software architecture has been introduced
  • The product is in a releasable state (i.e. the increment has not broken anything)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To Estimate
Development

No branches or pull requests

2 participants