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

Google fusion tables will be deprecated at the end of 2019 - need to fix or remove /maps + links #619

Open
dlebauer opened this issue Jan 10, 2019 · 5 comments
Labels

Comments

@dlebauer
Copy link
Member

On the home page, both the 'model i/o' and the 'crop model maps' tabs link to https://www.betydb.org/maps

image

But https://www.betydb.org/maps is broken.

I suspect that this is related to the latest release, which was deployed in August, at which point pageviews went to zero (except 2 in Nov 2018)

image

In addition, the google fusion tables API will be deprecated at the end of 2019. Unless someone wants to write a replacement application, I would remove this page, keeping only the links to the underlying .csv files with model outputs.

@dlebauer dlebauer added the bug label Jan 10, 2019
@robkooper
Copy link
Member

is this related to #596 ?

@gsrohde
Copy link
Contributor

gsrohde commented Jan 11, 2019

I think it's essentially a duplicate (except for the added information here about the Google fusion tables API). @dlebauer This is one reason I don't close issues until the bug fix or feature has actually been deployed.

@dlebauer dlebauer changed the title https://www.betydb.org/maps broken Google fusion tables will be deprecated at the end of 2019 - need to fix or remove /maps + links Jan 11, 2019
@dlebauer
Copy link
Member Author

OK. I updated the name of this issue so that it focuses on google fusion tables. I kept the original images b/c it illustrates the links that would need to be removed / updated.

In the simple case of not fixing the maps, we could replace the model i/o tab on betydb.org with a dropdown like
image

that allows users to download the csv files. Alternatively, we could link to a shiny app.

@dlebauer
Copy link
Member Author

This is one reason I don't close issues until the bug fix or feature has actually been deployed.

@robkooper would the idea behind a 'hotfix' branch be that we can go ahead and deploy these to production so that we don't have to wait for an official release?

@robkooper
Copy link
Member

robkooper commented Jan 11, 2019

hotfix will still end up being a release, but will usually only fix 1 specific issue that breaks current deployments and is something that you want to fix really quickly.

Usually a hotfix will be patch (i.e. the 3rd number in a version Major.Minor.Patch).

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

No branches or pull requests

3 participants