Studies show that sharing your research data increases your impact. Partner with the library to take your data public, through Digital Commons @ Georgia Southern, OpenICPSR, or whatever data repository best fits your data.
Significant portions of this guide are adapted from the Cornell University Research Data Management Services Group website under a Creative Commons Attribution 4.0 International License.
In any data project, there are likely to be two components. The first is the data collected, assembled, or generated. Think of it as the raw content in the system. It could be hourly temperature readings from a sensor, the age of individuals in a survey, recordings of individual voices, or photographs of plant specimens. The second component is the data system in which the data is stored and managed.
We usually do not think of data content separate from the system in which it is stored, but the distinction is important in terms of intellectual property rights. The question is what, if anything, is protected by copyright. Data that is factual has no copyright protection under U.S. law; it is not possible to copyright facts. Not all data is in the public domain. A project might, for example, use copyrighted photographs; the photographs are part of the project’s “data.” In many cases, the data in a data management system as well as the metadata describing that data will be factual, and hence not protected by copyright.
A database, on the other hand, can have a thin layer of copyright protection. Deciding what data needs to be included in a database, how to organize the data, and how to relate different data elements are all creative decisions that may receive copyright protection.
Because of the different copyright status of databases and data content, different mechanisms are required to manage each. Copyright can govern the use of databases and some data content (that which is itself original), but contract law, trademarks, and other mechanisms are required to regulate factual data.
Creative Commons recommends use of the above licenses only. It does not recommend use of any NonCommercial (NC) or NoDerivatives (ND) licenses. For more information, see this article on the Creative Commons wiki.
In addition to Creative Commons, the Open Data Commons group (http://opendatacommons.org) has developed a number of legally binding tools to govern the use of databases and data. Using a combination of copyright and contractual standards, they have created three standard licenses. In addition, Open Data Commons has developed a suite of “community norms” that complement use of the formal licenses. While not carrying the force of law, these norms may be used to express your beliefs about appropriate data sharing and reuse.
The three ODC licenses are:
Selecting a License
There is no single right answer as to which license to assign to a database or data content. Note, however, that anything other than a CC0 or ODC PDDL license may present challenges for subsequent users of your data. This is because of the problem of "attribution stacking." It may be possible to extract data from a dataset, use it in a research project, and still maintain information as to the source of that data. It is possible to create a dataset derived from hundreds of sources with each source requiring acknowledgement. Furthermore, the data in the other databases may not have originated with it, but instead have been sourced from other databases that also demand attribution. Rather than legally require that everyone provide attribution to the data, it might be enough to express the community norm that says “if you make extensive use of data from this dataset, please credit the authors.”
The ownership of works produced by Georgia Southern faculty, students, and non-academic staff is governed by the University System of Georgia's Policy on the Use of Copyrighted Works in Education and Research and Georgia Southern University's Intellectual Property and Technology Transfer Policy. The precise answer will depend on whether the project was created as part of sponsored research; the employment status of the creator; whether the work was conducted pursuant to a specific direction or assigned duty; and, whether substantial university resources were used in the creation of the work. Please consult with the Office of Research and Economic Development to ensure that you are in compliance with these guidelines.
CC0 (+BY). Cohen, Dan. 2013. http://www.dancohen.org/2013/11/26/cc0-by/. A call for using CC0 with data, tempered by an ethical obligation to attribute.
Data Citation Developments. Kratz, John. 2013. http://datapub.cdlib.org/2013/10/11/data-citation-developments/. An update on efforts to standardize data attribution requirements.
How to License Research Data. Ball, Alex. 2012. http://www.dcc.ac.uk/resources/how-guides/license-research-data. Written with British law in mind, but it has a good discussion of the pros and cons of the ODC licenses.
Licensing Open Data: A Practical Guide. Korn, Naomi and Oppenheim, Charles. 2011. http://discovery.ac.uk/files/pdf/Licensing_Open_Data_A_Practical_Guide.pdf. Another guide written with UK law in mind, but with a helpful comparison of CC and ODC licensing options.
Open Data. Wikipedia. http://en.wikipedia.org/wiki/Open_data
Why we can't use the same open licensing approach for databases as we do for content and software. Hatcher, Jordan S. http://www.semantic-web.at/news/jordan-s-hatcher-x22-why-we-can-x27-t-use-the-same-open-licensing-approach-for-databases-a