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

Improve clip calendar and clip album handling of missing archive objects. #152

Closed
HaroldMills opened this issue Dec 17, 2018 · 6 comments
Closed
Assignees

Comments

@HaroldMills
Copy link
Owner

Vesper currently does not handle missing archive objects very well in clip calendar and clip album views. As of fda628b, both views handle empty archives better than they use to (they deliver a 404 response rather than raising an exception), but not as well as they should. Both views should display a clear error message (on a page delivered with HTTP status 200) when the archive is empty, as well as when it is not but a requested station/mic, detector, or annotation does not exist.

This issue succeeds #150.

@RichardLitt
Copy link
Contributor

Hey @HaroldMills. This is still a real blocker for me, when it comes to setting up different archives. I can't remember how to fix this issue; I've tried manually importing Preferences.yaml, Classifier.yaml, Redux\ Detectors.yaml, and migrating databases, creating a new superuser after each migration, and importing audio. But I can't get see the clip calendar.

In lieu of fixing the bug, could you write the steps here for fixing the station_mic missing issue?

@RichardLitt
Copy link
Contributor

I got it evenutally. It looks like manually adding the right .yaml file - in my case, the one Archive Data/Vesper NBNC Archive Data.yaml, into the Import Archive Data solved this problem. Should we add this to the Wiki?

@HaroldMills
Copy link
Owner Author

Hi @RichardLitt - I've added an FAQ to the wiki, including a question that I hope will help with this issue. I'm working on getting Vesper 0.4.8 ready, including the create-an-archive tutorial mentioned in the FAQ, which I intend will take care of this issue.

@RichardLitt
Copy link
Contributor

Thanks, @HaroldMills.

@HaroldMills
Copy link
Owner Author

This issue was resolved by Vesper 0.4.8.

@RichardLitt
Copy link
Contributor

Thank you, @HaroldMills!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants