cometadata/datacite-titles-descriptions-related-identifiers huggingface dataset:
DOI: 10.25504/fairsharing.95c69f
title: FAIRsharing record for: FAIR Principles for Research Software - R1.1. Software is given a clear and accessible license
title: FAIR4RS - R1.1

description: This FAIRsharing record describes:  'R1.1. Software is given a clear and accessible license' states that to enable reuse, software must have a license that clearly describes how it can be used and reused, ideally with conditions that are readable by humans and machines. Licenses are often referred to by name, but machine readable licenses can be specified by reference to a standard vocabulary such as the SPDX License List4 (SPDX Consortium, 2020). To support a wide range of reuse scenarios, the license should be as unrestrictive as possible and, to avoid license proliferation, choosing a widely used and recognized license is strongly recommended. This license must also be compatible with the requirements of the licenses of the software’s dependencies so that the software can be legally combined.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.9bf822
title: FAIRsharing record for: FAIR Principles for Research Software - R1. Software is described with a plurality of accurate and relevant attributes
title: FAIR4RS - R1

description: This FAIRsharing record describes:  'R1. Software is described with a plurality of accurate and relevant attributes' states that it is easier to reuse (and find) software if there are many descriptive labels attached to it. F2 requires software to be described by rich metadata. References provided by applying I2 can help document the use and purpose of the  software. Software should be described for the categories of R1.1 (license), R1.2 (provenance), and additionally address the categories of metadata that facilitate reuse. Relevant attributes can be determined by repositories, and by communities who create and reuse software. Plurality means that, where possible, multiple
terms for the same, similar, or overlapping concepts should be provided to enable the broadest possible reuse. Metadata and documentation are distinct, potentially complementary, concepts. Metadata about software can be included in documentation, or in the code itself, or in a separate location. Metadata included in the documentation are generally not machine readable, or indexable. This does, however, support the reusability of software particularly from a human perspective.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.15468/dl.5k3ps5
title: Occurrence Download

description: A dataset containing 0 species occurrences available in GBIF matching the query:
{
 "and" : [
 "TaxonKey is one of (Rheocles pellegrini)",
 "BasisOfRecord is one of (Specimen, Literature Occurrence, Human Observation, Observation)",
 "HasCoordinate is true",
 "HasGeospatialIssue is false",
 "Year is greater than or equal to 1991",
 "Year is less than or equal to 2025"
 ]
}

 The dataset includes 0 records from 0 constituent datasets; see https://api.gbif.org/v1/occurrence/download/0068117-250717081556266/datasets/export for details.
DOI: 10.25504/fairsharing.6d7a69
title: FAIRsharing record for: FAIR Principles for Research Software - I2. Software includes qualified references to other objects
title: FAIR4RS - I2

description: This FAIRsharing record describes:  'I2. Software includes qualified references to other objects' states that some software includes references to external data objects required to execute the software (e.g., parameter files for certain applications). Ideally, the data would be FAIR as well, and references to external data would be fully qualified. Qualified references should be to digital objects (e.g., metadata, other software, data), as well as to non-digital objects that have a virtual presence in digital systems (e.g., samples, reagents, instruments, etc.) with which the software interacts. These qualified references should be described using identifiers and/or controlled vocabularies. “Qualified” means specifying the authoritative source for an identifier or vocabulary item, possibly including a resolvable reference to further information about the source. Ideally this is in a form that includes a resolver within the reference (e.g., in the form of a persistent identifier, or URL). This information can also improve the reusability of software by explicitly including references to articles and data sets that document its use. Examples of qualified references might include: software X is implemented using software A (a programming language); software X uses software B (a library/dependency); software X is tested within software C (a platform); software X extends software D.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.c889a8
title: FAIRsharing record for: FAIR Principles for Research Software - I1. Software reads, writes and exchanges data in a way that meets domain-relevant community standards
title: FAIR4RS - I1

description: This FAIRsharing record describes:  'I1. Software reads, writes and exchanges data in a way that meets domain-relevant community standards' states that software interoperates through the exchange of data. This includes the use of data and metadata types, controlled vocabularies, and formats that are formally defined through standards to facilitate the exchange. Whereas F4 requires that metadata describing the software are FAIR, this principle ensures that the way that software interacts with other software is clearly described. A domain-relevant standard is an agreed standard that addresses the needs of a given community (or communities). Examples of community standards for data are curated by FAIRsharing at https://fairsharing.org/standards/. Where software interacts via APIs, these should be documented so that their capabilities can be inspected and understood by humans and machines, and they should be open APIs where possible.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.8367a5
title: FAIRsharing record for: FAIR Principles for Research Software - A2. Metadata are accessible, even when the software is no longer available
title: FAIR4RS - A2

description: This FAIRsharing record describes:  'A2. Metadata are accessible, even when the software is no longer available' first acknowledges that the availability of software may change over time, because there is a cost to maintaining access or because the software has degraded and is no longer safely usable, or because dependencies are no longer available. A2 then states that the metadata describing the software should remain accessible as it is generally easier and cheaper to store and maintain than the software itself (e.g., in the software repository, or in a software registry or catalog) and there is value in understanding the details of the software even if it is no longer accessible.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.0c61dd
title: FAIRsharing record for: FAIR Principles for Research Software - A1.2. The protocol allows for an authentication and authorization procedure, where necessary
title: FAIR4RS - A1.2

description: This FAIRsharing record describes:  'A1.2. The protocol allows for an authentication and authorization procedure, where necessary' states that authentication and authorization must be possible, where necessary. The FAIR Guiding Principles put specific emphasis on enhancing the ability of machines to use digital objects. In the context of software, there are often conditions of access, for instance, requiring a license server to be contacted, requirement for payment before use, or restrictions based on the privilege level of the user.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.6fff5e
title: FAIRsharing record for: FAIR Principles for Research Software - A1.1. The protocol is open, free, and universally implementable
title: FAIR4RS - A1.1

description: This FAIRsharing record describes:  'A1.1. The protocol is open, free, and universally implementable' states that it is the openness of the communications protocol (including the resolver for the identifier) that is important, not the implementation of the infrastructure that supports it. Here “open” means that there are no restrictions to implementing it and “free” means that there are no fees or licensing costs to implement it.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.b93697
title: FAIRsharing record for: FAIR Principles for Research Software - A1. Software is retrievable by its identifier using a standardized communications protocol
title: FAIR4RS - A1

description: This FAIRsharing record describes:  'A1. Software is retrievable by its identifier using a standardized communications protocol' states that, although different types of software have different methods for access (for instance, software that is only available in source code form may be downloaded from a repository before being compiled locally, whereas software hosted as a service on a remote server may be accessed without retrieving it), obtaining the software should not require specialized or proprietary tools or communication methods. For much software, there are commonly used technical communications protocols used to access the software, such as HTTPS.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.aeef8a
title: FAIRsharing record for: FAIR Principles for Research Software - F4. Metadata are FAIR, searchable and indexable
title: FAIR4RS - F4

description: This FAIRsharing record describes:  'F4. Metadata are FAIR, searchable and indexable' requires that the metadata about the software is made FAIR, including making it readable and discoverable by both humans and machines. This improves the findability of software by supporting searching and indexing by others. It allows the metadata to be published in or harvested by a registry or catalog or repository, or by a search engine. FAIR metadata also enables and encourages citation of research software.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.9d893d
title: FAIRsharing record for: FAIR Principles for Research Software - F3. Metadata clearly and explicitly include the identifier of the software they describe
title: FAIR4RS - F3

description: This FAIRsharing record describes:  'F3. Metadata clearly and explicitly include the identifier of the software they describe' states that the association between the metadata (wherever it is stored; see F4) and the software should be made explicit by mentioning the software’s globally unique and persistent identifier in its associated metadata. In conjunction with A1, this means the metadata describes how the software can be obtained. Metadata are not required to include references for all of the softwares dependencies in order for software to be findable. I2 and R2 describe how references to dependencies increase the likelihood that software is interoperable and reusable.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.656e6c
title: FAIRsharing record for: FAIR Principles for Research Software - F1.2. Different versions of the software are assigned distinct identifiers
title: FAIR4RS - F1.2

description: This FAIRsharing record describes:  'F1.2. Different versions of the software are assigned distinct identifiers' states that to make different versions of the same software (or component) findable, each version needs to be assigned a different identifier. The relationship between versions is embodied in the associated metadata. What is considered a “version” is defined by the owner of the software: in many cases this will be something that the owner wants to specifically identify and use and/or “release” or “publish” so that others can use and reference/cite. There are existing software engineering practices (e.g., version control, semantic versioning) around the management and versioning of software that may form part of the implementation of these relationships. Capturing the relationships between different versions of software will lead to greater understanding of the evolution of code, its authorship, ownership, description and purpose, amongst other things.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.a712f1
title: FAIRsharing record for: FAIR Principles for Research Software - F2. Software is described with rich metadata
title: FAIR4RS - F2

description: This FAIRsharing record describes:  'F2. Software is described with rich metadata' states that software requires descriptive metadata to support indexing, search and discoverability. This metadata describing the software must itself be FAIR (F4), should follow community standards, and use controlled vocabularies. The FAIR4RS principles do not define which standards should be used, as this is better captured in guidance for implementing the principles coming out of each community. R1, R1.1, and R1.2 describe categories of metadata that enable reuse.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.378ec7
title: FAIRsharing record for: FAIR Principles for Research Software - F1.1. Components of the software representing levels of granularity are assigned distinct identifiers
title: FAIR4RS - F1.1

description: This FAIRsharing record describes:  'F1.1. Components of the software representing levels of granularity are assigned distinct identifiers' requires the use of identifiers for more than just the software project (often synonymous with “software concept” or “software product”) as this improves findability by enabling components to be assigned distinct identifiers e.g, a software library, and a function in that library. The relationship between these components is embodied in the associated metadata. These principles do not prescribe which granularity levels should be assigned identifiers, as this is likely to be implementation-specific.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.99299d
title: FAIRsharing record for: FAIR Principles for Research Software - F1. Software is assigned a globally unique and persistent identifier
title: FAIR4RS - F1

description: This FAIRsharing record describes:  'F1. Software is assigned a globally unique and persistent identifier'  requires that a piece of software is given an identifier which is both globally unique (not used to identify any other object, even on a different system) and persistent (long-lasting, including its resolution - the ability to use it to get to the identified source). The use of globally unique and persistent identifiers enables adherence to many of the other FAIR4RS Principles by removing ambiguity (for humans and machines) around what software (or part of it) is being referenced. Complexities around software granularity (the “level of detail being implemented”) and software
versions (the “changes between implementations”) are addressed by F1.1 and F1.2. This principle also relates to enabling accessibility to software, specifically A1.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.d2f63c
title: FAIRsharing record for: FAIR Principles for Research Software - Reusable
title: FAIR4RS - R

description: This FAIRsharing record describes:  'R: Software is both usable (can be executed) and reusable (can be understood, modified, built upon, or incorporated into other software)' acknowledges that the definitions of interoperability and reusability as defined by the FAIR Guiding Principles overlap when applied to software. To differentiate between the two, this principle - reusability (implicitly including usability)  - here focuses on the ability of humans and machines to execute, inspect, and understand the software, so it can be modified, built upon, or incorporated into other software. Note that the general intent of these principles is that software is “executable in principle” - not
“guaranteed to execute”. Also, different aspects of reusability may best apply to different forms of software. The form in which it is made available changes the way it can be used. For instance, source code might be modifiable but not executable without specialist infrastructure; libraries available as binaries can be built on and incorporated into other software but not easily modified. In general, source code is the most reusable form of software. The concept of software quality overlaps with the FAIR4RS Principles, particularly reusability, but is not directly addressed by them. Similar to openness, software quality is beneficial to making software FAIR but not required.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.25504/fairsharing.c72182
title: FAIRsharing record for: FAIR Principles for Research Software - Interoperable
title: FAIR4RS - I

description: This FAIRsharing record describes:  The FAIR4RS 'Interoperable' principle states that 'I: Software interoperates with other software by exchanging data and/or metadata, and/or through interaction via application programming interfaces (APIs), described through standards'. The definitions of interoperability and reusability as defined by the FAIR Guiding Principles overlap when applied to software. To differentiate between the two, interoperability here is limited to being concerned with the capacity to exchange data between independent software (i.e., software that can be executed separately). As an example, the sense of “integrated” that applies to data (where two pieces of data combine to form new data) does not apply in the same way to software where, in a sense, all software is “integrated” with, or depends on, other software (and this concept is placed under reusability, in R2). Software also has “agency”: software calls on other software. Two independent pieces of software can be said to interoperate when the functionality exists in both to read and write or otherwise exchange data.
description: The source of this description is the metadata record on FAIRsharing.org, an educational and informative resource that describes and links databases, standards, and data policies. FAIRsharing also creates collections of these resources and recommendations of databases and standards based on 3rd party data policies.
DOI: 10.15468/dl.6fuyra
title: Occurrence Download

description: A dataset containing 97987 species occurrences available in GBIF matching the query:
{
 "and" : [
 "HasGeospatialIssue is false",
 "HasCoordinate is true",
 "OccurrenceStatus is Present",
 "BasisOfRecord is one of (Human Observation, Machine Observation, Occurrence evidence, Observation)",
 "TaxonKey is one of (Melanocorypha calandra)",
 "Country is one of (Åland Islands, Albania, Andorra, Austria, Belarus, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Czechia, Denmark, Estonia, Faroe Islands, Finland, France, Germany, Gibraltar, Greece, Guernsey, Holy See, Hungary, Iceland, Ireland, Isle of Man, Italy, Jersey, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Moldova, Republic of, Monaco, Montenegro, Netherlands, North Macedonia, Norway, Poland, Portugal, Romania, Russian Federation, San Marino, Serbia, Slovakia, Slovenia, Spain, Svalbard and Jan Mayen, Sweden, Switzerland, Ukraine, United Kingdom of Great Britain and Northern Ireland)"
 ]
}

 The dataset includes 97987 records from 164 constituent datasets; see https://api.gbif.org/v1/occurrence/download/0068078-250717081556266/datasets/export for details.
 
Data from some individual datasets included in this download may be licensed under less restrictive terms.