-
Notifications
You must be signed in to change notification settings - Fork 2
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
document any moab remediation processes that might be re-usable #1396
Comments
i'm not sure using the zenhub blocking connection is the right approach here: but starting this should be blocked on at least one of the linked issues. but this could be started as soon as we've closed any of:
|
though it seems likely we'll want to collect documentation from most (maybe all) of the resolutions of those issues. |
probably can't quite complete this, but i think we can get started on it now |
removed the blocker about re-archiving, but ultimately that should be part of this documentation too (see #1396) |
@jmartin-sul if there is further work to be done on this ticket, please ticket separately; personally, I would be okay just closing this ticket. |
Start a Preservation Catalog wiki page for capturing re-usable moab remediation notes. These should be investigative procedures and remediation procedures that developers and repository admins can use for approaching preservation objects that fail audits in the future.
To prevent clutter, if a procedure will really only be used once, it might be better to keep it in the issue.
But it may also be a good idea to link remediation issues from the wiki, or at least to try and consistently tag them, for easier searching in the future.
I suspect that most remediations will be unique and hard to fully automate, but I also suspect it will be easier to approach any new remediation if there's some documentation about the types of problems we've encountered and solutions we've used.
The text was updated successfully, but these errors were encountered: