IU SEAD Cloud is a default publication solution for the users of SEAD, a collaborative NSF-funded project to create tools and services in support of data publication needs of sustainability science research. It relies on the Indiana University Scholarly Data Archive (SDA) infrastructure, a distributed storage service co-located at IU data centers in Bloomington and Indianapolis, arranged in large files, with two copies of data made by default.
IU SEAD Cloud is supported by the team from the IU Data to Insight Center. It accepts data from any SEAD-affiliated user. To become a SEAD user, you will need to create an account and set up a project space. Visit SEAD help pages to learn how to do that.
What kinds of data does IU SEAD Cloud accept?
IU SEAD Cloud accepts research data from researchers and professionals who are working in the broad, multidisciplinary area of sustainability science and who do not have another place for publishing their data, for example, an institutional or a disciplinary repository. To be accepted into IU SEAD Cloud, your data must satisfy the following criteria:
- Dataset cannot exceed 1 GB. If you have data that exceeds 1 GB, it needs to be split into several smaller datasets.
- The maximum folder hierarchy depth of any dataset is 4.
- User or a group of users can publish multiple datasets, but the overall space allocated to one project cannot exceed 10 TB.
- Most types of files can be submitted for publication (e.g., text, spreadsheets, images, videos, software code). Compressed archives of multiple files (e.g., zip) are accepted too.
- Datasets must be released under one of the Creative Commons Family licenses.
- IU SEAD Cloud is not HIPAA-compliant, but it can accept submissions with sensitive data and restrict access to it. The data will not be available for download without the creators' permission, only metadata will be available.
- IU SEAD Cloud supports a variety of metadata formats, including Dublin Core and the Content Standard for Digital Geospatial Metadata (CSDGM). Datasets must be supplied with minimal metadata, which includes but is not limited to creator, date-created, project name, and restrictions in access. Metadata needs to be serialized in an XML file or in the OAI ORE map.