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

Determine Best Practices for Reverting To Previous Catalog Data (Meeting?) #249

Open
4 tasks
bwatson78 opened this issue Feb 19, 2021 · 0 comments
Open
4 tasks
Labels
Application Development Phase 2 Issues deferred to Phase 2 of the Blacklight Project Task Individual tasks associated with an issue

Comments

@bwatson78
Copy link
Contributor

bwatson78 commented Feb 19, 2021

My guess as to handling reversion of catalog data would be to cache the previous XML received from OAI every time it processes.
Questions:

  • Is that the best way to do this?
  • If so, how many XMLs should we cache (just the last one or more)?
  • Should we cache just a full reindex? Include on-demand reindexes?
  • If we cache on-demand reindexes, would that get too "messy"?
@bwatson78 bwatson78 added Application Development Task Individual tasks associated with an issue labels Feb 19, 2021
@tmiles2 tmiles2 added the Phase 2 Issues deferred to Phase 2 of the Blacklight Project label Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Application Development Phase 2 Issues deferred to Phase 2 of the Blacklight Project Task Individual tasks associated with an issue
Projects
None yet
Development

No branches or pull requests

2 participants