Aspect For Individual Researchers For Institutions and Projects For the Community/
GEO BON
Reference
Open Access Select open licenses, preferably the most open suitable Creative Commons license possible (CC0, otherwise CC-BY or, if necessary CC-BY-NC – avoid the ND, no-derivates and SA, share-alike options), for all published data sets unless one of a specific set of exceptions apply. Develop data policies in support of open access and open science, and standardise on Creative Commons licenses for all but specific exceptions. Support Creative Commons licenses, and work towards machine-readable, multi-jurisdiction licenses for the valid exceptions not supported by Creative Commons. [1], [4], [5], [8], [10], [39], [40], [42], [43], [46], [47], [48]
Federated Identity Make use of globally available resources in this regard, such as EduRoam If available, use EduRoam as a basis for service and system authentication, and ensure that researchers have access to it. Work with RDA to facilitate a globally available identity resolution framework that can be used by system and service developers. [1], [41], [42]
Data Citation Ensure that data sets are published with a persistent identifier, and make use of persistent identifiers when citing others. Ensure that mechanisms are available for persistent identifiers to be minted for data set publication, and that sufficient infrastructure spending is available for implementation of RDA guidelines in respect of data citation. Promote a culture of data citation and license respect/ maintenance. Contribute use cases to RDA working groups on data citation to ensure that the needs of the biodiversity community are included in guidance. [2], [8], [10], [40], [42]
Data Types (Data Families) Use the guidance below to select a data family appropriate to the data being published. Bear in mind that the publication format is not the same as the format in which the data is best applied in your own context. Make an effort to ensure that data type registries are supported once these become available. Ensure that tools and processing routines are designed and implemented in such a way that the data type registry can be supported. [3], [8], [10]
Metadata Interoperability Use the guidance below to select an appropriate metadata standard for the data to be published, and ensure that maximal use is made of name services (vocabularies, ontologies, registries of permanent identifiers). Work towards adoption of metadata standards within the institution. Ensure that catalogues of institutional data offer harvesting end points supported by widely accepted protocols (see below for guidance). Work towards adoption of metadata standards within the community and develop best practice/ guidelines in respect of name service usage, mandatory elements, quality, protocol and lineage description, and other elements supporting re-use of the data. [4], [8], [42], [43]
Name Service Interoperability Support appropriate name services (vocabularies, ontologies, and PID registries) wherever these are indicated. Refer to the guidance below in this regard. Develop institutional best practice/ guidance in respect of name service usage. Contribute to an support RDA efforts to improve name service interoperability, and actively promote the use of such services by the community. [4], [9], [42], [43]
Data Interoperability Use the guidance below to select a data family appropriate to the data being published. Specifically work towards making sure that the data is not only available in a standardised schema (format), but that it is also available via a standardised protocol (web service). Ensure that infrastructure exists for implementation of appropriate web services to enable access to standardised data sets. Seek consensus and endorsement within standards bodies of especially content standards for all data families identified below as requiring attention. [4], [8], [42], [43]
Trusted Repositories and Reliable Future Access Make sure that your data is published and archived in a Trusted Digital Repository, with long-term curation policies and contingency planning in place. Take steps to accredit your institutional repository/ data service with one of the recommended global initiatives, and register the repository with re3data. Implement recommendations of the RDA Practical Policies Working Group. Support the principle of deposit in Trusted Digital Repositories. [4], [6], [7], [8], [42]