-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
License? #6
Comments
I see you have this section: https://github.com/owid#can-i-use-or-reproduce-your-code-or-data, but it might be an idea to actually add the license files in the relevant repositories as well? |
Hi, yes that is a good point. In general, we try to make citation information readily available. In our interactive charts you can always click on "Learn more about this data" to get information about the sources, and often times there's also information on how to cite them. Sadly, we cannot hand out a plain Creative Commons license, since the licensing depends heavily on the data publisher behind it, and we are usually just republishing the data (with slight modifications at times, and normalized into our data format). In this repository that information is less readily available, sadly, but you can still find some source information in the Also, be aware that there are the repos https://github.com/owid/co2-data and https://github.com/owid/energy-data with more broad data on these two topics, if that helps. Let me know if you have any other questions! |
Thank you for your reply. To explain what I mean:
|
Hello again, and sorry for the late response. In this particular instance, the original source of this data is a pdf report that can be found on CDC Stacks here. CDC Stacks writes that many of its articles are available under a Creative Commons or similar license, but sadly it doesn't say anything specifically for this article. |
Hello,
I was wondering if you were planning to add some sort of open license (such as a Creative Commons license) to your datasets to enable reuse of your datasets?
The text was updated successfully, but these errors were encountered: