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

Use last best data when file is down #9

Open
mariongalley opened this issue Jul 11, 2022 · 7 comments
Open

Use last best data when file is down #9

mariongalley opened this issue Jul 11, 2022 · 7 comments

Comments

@mariongalley
Copy link

No description provided.

@mariongalley
Copy link
Author

@mariongalley
Copy link
Author

Suggest we add a useful error instead indicating the data is currently down instead. Quality Dashboard should state the data is down as that's an issue.

@mariongalley
Copy link
Author

@KDuerden We do now have an error on the quality dashboard when data is down. Do we still want to show the heatmap, badges etc for latest best?

Image

@KDuerden
Copy link
Contributor

Do we still want to show the heatmap, badges etc for latest best?

Yes please.

If a funders' data falls out completely - eg goes 31+ days with no new access standard procedure is to remove those files from the Registry. Do we know what DQD will do in those cases - if there is any delay in taking down the fully dead link?

@mariongalley
Copy link
Author

@michaelwood Do you know how the DQD handles down short term vs down > 31 days currently?

When we do this ticket we can get it to match what the other tools do.

@michaelwood michaelwood transferred this issue from ThreeSixtyGiving/registry-classic Mar 4, 2024
@mariongalley
Copy link
Author

If file is down < 90 days, show the Quality features and use a warning to indicate we currently can't access the file

@michaelwood
Copy link
Member

Backend part of this work is ThreeSixtyGiving/datastore#237 (currently in code review)

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

3 participants