...
3) All data and metadata generated through the use of committed resources in connection with this agreement will be made available in a way that it can be exchanged with other NDS services through a standard API and/or serialized export formats. Acceptable option(s) will be defined within the next 6 months through NDS participants, specifically through the work of interoperability-related pilot projects and the coordination activities of the NDS Interoperability Working Group being proposedTechnical Advisory Committee's Interoperability Task Force.
4) Resources must be provided openly to all NDS participants
...
<Org Name> will provide, as part of NDS Share, storage for published data, up to <size, e.g. 200TB>, and associated cloud computing resources to support access <and possibly co-located computing> that would be maintained, on a best-effort basis, for a minimum of <# years, e.g. 3? 5?> years. These resources are intended to support active US research efforts producing data with ongoing scientific value and for which alternative data repository options do not exist. Use of the <Org Name> resources in NDS Share will be managed by policies developed by <Org Name> in collaboration with NDS participants. For projects requesting less than <size, e.g. 1 TB> of storage for data publication and having no computational needs beyond those required for data access, permission to use the <Org Name> Share resources would be automatic based upon a request from the leadership of a funded research project in the US and a self-assertion of the value of the data and the appropriateness of NDS Share as a publication option at a level equivalent to the justification in an NSF Data Management Plan. For projects that require more space and/or significant cloud resources, a statement from a community(ies) of potential users attesting to the data’s value and to the need for NDS Share resources, e.g. because there is no alternative repository available and/or because co-location with the tools and services being developed in NDS Labs would add significant value, will be required and will be reviewed by <review team, e.g. an <Org Name>/NDS committee>. <Org Name> reserves the right to immediately revoke allocations and/or to block access to data publications and reclaim the storage space if it determines that continued access would be inconsistent with the stated purposes of the provided resource.
...
- The data publications and derived data products created using this resource will be associated with a citable persistent identifier
- The data published to or generated with this resource will be available under an open (Creative Commons or similar) license
- Any software required for publication and access that will run within this resource must be compatible with the containerized deployment methods used within NDS Labs. (Note this is a resource-specific requirement)
- The software must—either natively or through the use of an open source tool—allow programmatic access to all the data and metadata comprising the publication through a common API and/or standards-based serialized format (e.g. a file). Acceptable option(s) will be defined within the next 6 months through NDS participants, specifically through the work of interoperability-related pilot projects and the coordination activities of the NDS Interoperability Working Group being proposedTechnical Advisory Committee's Interoperability Task Force.
<Existing Repository/Project/Service example, e.g. DIBBS, DataNet, operational repositories, etc.>
...
- The data exchanged with other NDS services will be associated with a citable persistent identifier
- The data produced through the use of <Repository/Project Name> capabilities and or published through <Repository/Project Name> and/or shared with other NDS Share capabilities will be available under an open (Creative Commons or similar) license
- All data and metadata generated through the use of <Repository/Project Name> services in connection with this agreement will be made available in a way that they can be exchanged with other NDS services through a standard API and/or serialized export formats. Acceptable option(s) will be defined within the next 6 months through NDS participants, specifically through the work of interoperability-related pilot projects and the coordination activities of the NDS Interoperability Working Group being proposedTechnical Advisory Committee's Interoperability Task Force.