refresh preservation_catalog wiki

[jmartin-sul]

ticket definition is WIP, and will probably spawn a number of more focused sub-tickets

TODO:

• grep for resque. disposition any page that mentions it: should we keep the page and edit it for sidekiq? delete it because it's no longer relevant? re-write the page to provide the same high level help, but for our current sidekiq setup? if a page needs an update or a re-write, it's fine to spawn a separate ticket for that.
• add a page about dealing with stuck jobs (see [blocked] Write wiki entry with instructions for killing stuck jobs (e.g. validate_moab) #2495)
• freshen the landing/navigation page
• freshen the TOC sidebar
• go through all the pages and disposition (update, re-write, or delete). if the page needs an update or a re-write, it's fine to spawn a separate ticket for that.
• update the DB wiki page ER diagram (use the gen_er_diagram docker container after spinning up your DB and running migrations locally)
• update replication flow wiki page (in light of major changes from Refactors replication. #2518 and follow-on PRs)
• ...

NOTE: the wiki is a git repo. some of this work may be easier if you clone the repo locally and work with it that way (something like greping it may require that?). 🚨 please don't force-push the wiki repo! if multiple people are doing this work simultaneously, we should figure out a way to coordinate any git based manipulation of the wiki.

[justinlittman]

Here is my recommendations (updated with replies as sub-bullets by @jmartin-sul 2026-01-28):

• Home -> Update
  • https://github.com/sul-dlss/preservation_catalog/wiki
  • jmartin done
• Audits (basic info) -> Needs update (possibly remove "See" references, as out of sync)
  • https://github.com/sul-dlss/preservation_catalog/wiki/Audits-%28basic-info%29
  • wiki update: Audits (basic info) #2588
• Ceph Errors -> Needs update
  • https://github.com/sul-dlss/preservation_catalog/wiki/Ceph-Errors
  • wiki update: Ceph Errors #2589
• Data model and DB schema -> Needs update (jlit done)
• DB best practices -> Move to legacy section of sidebar
  • https://github.com/sul-dlss/preservation_catalog/wiki/DB-best-practices
  • jmartin done
• DB Migration Checklist -> Move to legacy
  • jmartin -- i'd actually prefer to keep this page. the postgres dump/restore command is useful. though to be fair, i was looking for it when we migrated earlier this month. didn't recall we'd captured this in the wiki, was looking through issues and dev playbook. which... maybe reworking for dev playbook is more appropriate?
  • needs update, at least to swap resque refs for sidekiq
  • wiki update: disposition "DB Migration Checklist" #2590
• Deleting a Moab from PresCat -> Mark as needing update when next used
  • https://github.com/sul-dlss/preservation_catalog/wiki/Deleting-a-Moab-from-PresCat
  • wiki update: Deleting a Moab from PresCat #2591
• Deposit bag was missing -> ??
  • https://github.com/sul-dlss/preservation_catalog/wiki/Deposit-bag-was-missing
  • wiki update: disposition "Deposit bag was missing" #2592
• Extract druids from Honeybadger alerts -> Move to legacy
  • jmartin done
• Fixing an Incomplete Moab Upload -> Move to legacy
  • jmartin done
• Job queues -> Remove Sidekiq configuration section (jlit done)
• Moab Audit Failures -> Move to legacy (does not contain useful info)
  • https://github.com/sul-dlss/preservation_catalog/wiki/Moab-Audit-Failures
  • jmartin -- i think the admonishment to get approval from the repository manager for prod edits of pres content is useful
• More than the expected number of Resque workers are running too many resque workers worker count high -> Delete
  • jmartin done
• Moving a Moab -> OK
• Overview -> Update (jlit done)
• Replication errors -> Update
  • https://github.com/sul-dlss/preservation_catalog/wiki/Replication-errors
  • wiki update: Replication errors #2593
• Replication Flow -> Update
  • https://github.com/sul-dlss/preservation_catalog/wiki/Replication-Flow
  • wiki update: Replication Flow #2594
• S3 Deletions -> OK
• S3 location already has content. Perhaps a failed replication was pruned from the database, but was not removed from the cloud. If so, prune this content from the database again... -> Move to legacy
  • jmartin done
• Validate moab step fails during preservationIngestWF -> ??
  • jmartin updated
• Zip Creation -> Update (jlit done)
• ZipmakerJob failures -> Move to legacy
  • jmartin done

jmartin adds:

• clearly mark all legacy section pages as such at the top (but not in the title, so you can avoid breaking/updating links)
  • wiki update: clearly leave a note indicating no future updates on all legacy section pages, at the top (but not in the title) #2595

[justinlittman]

Here's some new docs on replication that might be useful for the wiki: https://docs.google.com/document/d/1DqPnbyv_y_7XwgRLsFYQbGDNOzVkyOGrDxGP_7M4A90/edit?usp=sharing

[jmartin-sul]

Here's some new docs on replication that might be useful for the wiki: https://docs.google.com/document/d/1DqPnbyv_y_7XwgRLsFYQbGDNOzVkyOGrDxGP_7M4A90/edit?usp=sharing

@justinlittman i've only had a chance to skim this, but i think we should consider turning this into a wiki page, maybe even just something like "Replication Architecture Explainer (2026)". seems like a good detailed overview to orient someone dealing with the code for the first time.