| alternative_standards_and_tools |
List of identifiers of standards and tools; those not explicitly planned to b... |
| anatomy |
Relevant anatomical locations, including gross anatomical parts, cell types, ... |
| availability_description |
A description of the availability of the data set, including any restrictions... |
| category |
CURIE for the high level ontology class in which this entity is categorized |
| collection |
Tags for specific sets of standards |
| concerns_data_topic |
Subject standard is generally applied in the context of object data topic |
| concerns_data_topics |
The data part includes these data topics |
| contribution_date |
The date on which the node was added |
| contributor_github_name |
The name of the github user who added this node |
| contributor_name |
The name of the person who added this node |
| contributor_orcid |
The ORCiD of the person who added this node |
| data_collection |
Collection of associated DataSet objects |
| data_part_description |
Description of the data part |
| data_part_name |
Name of the data part |
| data_parts |
Collection of associated DataPart objects |
| data_standardortools_collection |
Collection of associated data standards or tools |
| data_substrates |
Relevance of the use case to one or more data substrates |
| data_substrates_collection |
Collection of associated data substrates |
| data_topics |
Relevance of the use case to one or more data topics |
| data_topics_collection |
Collection of associated data topics |
| data_url |
URL where the data set can be accessed |
| datasets |
The manifest includes these datasets |
| datasheet |
List of one or more URLs pointing to related datasheets in the Datasheets for... |
| datasheet_url |
URL where the datasheet for the data set can be accessed |
| description |
A human-readable description for a thing |
| documentation_url |
URL where documentation for the data set can be accessed |
| edam_id |
Unique EDAM identifier |
| enables |
List of other use case(s) this use case supports or makes possible |
| file_extensions |
Commonly used file extensions for this substrate |
| formal_specification |
Relevant code repository or other location for a formal specification of the ... |
| has_application |
A list of one or more specific applications of this entity to a specific purp... |
| has_files |
Subject data set has the file(s) listed in this slot as parts |
| has_parts |
Subject data set has the data set(s) listed in this slot as parts |
| has_relevant_data_substrate |
Subject standard has some relationship to the object data substrate(s), inclu... |
| has_relevant_organization |
Subject standard has some relationship to the object organization(s), includi... |
| has_training_resource |
Relevant training resources, standard usage manuals, or other documentation f... |
| id |
A unique identifier for a thing |
| involved_in_experimental_design |
True if use case is likely to be implemented as part of an experimental proce... |
| involved_in_metadata_management |
True if use case is likely to be implemented as part of metadata indexing, sa... |
| involved_in_quality_control |
A value of True indicates a use case is likely to be implemented as part of d... |
| is_bridge2ai_data |
True if the data set is produced by a Bridge2AI consortium group |
| is_open |
Is the standard or tool FAIR and available free of cost? |
| is_public |
True if the data set is publicly available |
| known_limitations |
Any current obstacles to implementing this use case |
| limitations |
Potential obstacles particular to this substrate or implementation |
| manifest_collection |
Collection of associated Manifest objects |
| mesh_id |
Unique MeSH identifier |
| metadata_storage |
Data Substrate in which metadata is stored |
| name |
A human-readable name for a thing |
| ncit_id |
Unique NCIt Identifier |
| node_property |
A grouping for any property that holds between a node and a value |
| notes |
Any additional notes about the manifest or the data part |
| organization |
The manifest corresponds to this organization |
| organizations |
Collection of associated organizations |
| produced_by |
Subject data set was produced by the organization(s) listed in this slot |
| publication |
Relevant publication for the standard or tool |
| purpose_detail |
Text description of the standard or tool |
| references |
List of one or more URLs pointing to related publications, preprints, or othe... |
| related_to |
A relationship that is asserted between two named things |
| relevant_to_gcs |
Bridge2AI Grand Challenges related to this use case, generally because they a... |
| requires_registration |
Does usage of the standard or tool require registration of a user or group wi... |
| responsible_organization |
Organization(s) responsible for providing and/or supporting the standard or t... |
| ror_id |
Unique ROR identifier |
| standards_and_tools |
The data part includes these standards and tools |
| standards_and_tools_for_gc_use |
List of identifiers of standards and tools; those planned to be used, or alre... |
| subclass_of |
Holds between two classes where the domain class is a specialization of the r... |
| substrates |
Subject data set is relevant to the substrate(s) listed in this slot |
| topic_involves_anatomy |
A relationship between a DataTopic and an anatomical entity |
| topics |
Subject data set is relevant to the topic(s) listed in this slot |
| type |
A generic slot for any label corresponding to the label for an entity type as... |
| url |
URL for basic documentation of the standard or tool |
| use_case_category |
Category of the UseCase |
| use_cases |
Collection of associated use cases |
| use_conditions |
Applicable conditions on use, as defined by the Data Use Ontology (DUO) |
| used_in_bridge2ai |
True if the entity is used, developed, or otherwise related to work in the Br... |
| uses_data_substrates |
The data part includes these data substrates |
| wikidata_id |
Unique Wikidata identifier |
| xref |
URI of corresponding class in an ontology of experimental procedures, in CURI... |