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

Discuss how we should react when availability API is down. #22

Open
nodanaonlyzuul opened this issue Jun 7, 2017 · 1 comment
Open

Comments

@nodanaonlyzuul
Copy link
Contributor

When SCSB's availability API is down or times out...we have a few options.
We can:

  • "null out" availability info in our response.
  • Trust the last availability information we got from ElasticSearch
  • Mark items we know to be dubious as possibly out of date and signal that in the UI.

This may be out of scope for this release but I wanted to record the conversation here.

CCing: @natalietsch, @nonword, @kfriedman, @jobinthomasnypl

@nodanaonlyzuul
Copy link
Contributor Author

This is in Jira here: https://jira.nypl.org/browse/SRCH-39

@kfriedman kfriedman marked this as a duplicate of #58 Jul 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant