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

JOSS Review warning about out of date local data #59

Closed
DrMattG opened this issue Sep 5, 2022 · 6 comments
Closed

JOSS Review warning about out of date local data #59

DrMattG opened this issue Sep 5, 2022 · 6 comments

Comments

@DrMattG
Copy link

DrMattG commented Sep 5, 2022

Warning message:
In wdpa_fetch("Norway", wait = TRUE, download_dir = rappdirs::user_data_dir("wdpar")) :
local data is out of date: jul 2022
(

### throw warning if out of date
)
What does it mean if the local data is out of date? Do I need to worry about this warning? It would be good to have some comment on this in the documentation (or somewhere).
openjournals/joss-reviews#4594

@jeffreyhanson
Copy link
Collaborator

jeffreyhanson commented Sep 5, 2022

The package will, by default, load the latest version of the database that is available on your computer (e.g., because you previously downloaded the data). This warning message is telling you that this version is now out of date, and a newer version is available online. I guess you would need to worry about this warning if you are running analyses that require the latest version, but generally this isn't the case. Sure, I can add some info to the docs on this message.

@jeffreyhanson
Copy link
Collaborator

Sorry for the slow progress on this @DrMattG. Just to keep you in the loop, I'm planning on creating a PR to incorperate this feedback - once I've merged the PR to address the issues raised by @Jo-Schie. Since I'm really bad at dealing with merge conflicts, I'd rather not create multiple branches at the same time and then have to juggle conflicts when merging them. Did you have any other issues/concerns (apart from #58 and #59) as part of your review? Or will I have addressed all your major concerns once these are addressed? Thanks for your patience!

@DrMattG
Copy link
Author

DrMattG commented Sep 20, 2022

Hi @jeffreyhanson - That's fine - I think I am happy with everything else - I understand the merge conflict issue!

@jeffreyhanson
Copy link
Collaborator

Ok awesome - thank you!

@jeffreyhanson
Copy link
Collaborator

@DrMattG, I've just created a PR to address this issue. When you get a chance, could you please take a look? I've put the changes specifically related to this issue in this commit: c83514c.

jeffreyhanson added a commit that referenced this issue Oct 3, 2022
* update README, fix #58
* update warning + docs on versions, #59
* update pkg docs
* skip DOIs in url checks
@jeffreyhanson
Copy link
Collaborator

Woops, forgot tag this issue in the commit when merging this PR, so I'll close this manually.

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