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
As a repository administrator
I can export the entire repository
in order to
do backups, systematically or ad hoc
use large exports as inputs to other tools systems
publish to AAPB
input to CLAMS, Fix-IT, future systems
without getting gateway timeout errors.
Background
Currently there are some practical limitations on exporting large record sets that are not being handled very well. Ideally. we want our export/publish workflow to be able to scale up, and be reasonably performant up to the size of the entire repository and beyond.
Also created a smaller scope ticket (#891) to deal with the unhandled error for when exports/pushes are too large. If we don't want to tackle the scope of this ticket yet, then maybe start there.
The text was updated successfully, but these errors were encountered:
User story
As a repository administrator
I can export the entire repository
in order to
without getting gateway timeout errors.
Background
Currently there are some practical limitations on exporting large record sets that are not being handled very well. Ideally. we want our export/publish workflow to be able to scale up, and be reasonably performant up to the size of the entire repository and beyond.
Also created a smaller scope ticket (#891) to deal with the unhandled error for when exports/pushes are too large. If we don't want to tackle the scope of this ticket yet, then maybe start there.
The text was updated successfully, but these errors were encountered: