You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scope clarity:
what is that we are cataloguing: Project AND Datasets Project: should we index all known IMI projects listed from IMI site or only those FAIRplus (and eTRIKS) have engaged with Datasets: complex objects with many data modalities and many dataset releases (accrual datasets, longitudinal datasets -> versioning, relevant for all prospective cases, ie IMI engaging currently with FAIRplus). Note: for many finished projects, this is irrelevant (the retrospective use case
initial representation with DATS model:
main advantage:
json schema validation
json context files for:
DCAT: compatibility with other data catalogues implementing the w3c standard
schema.org : search engine visibility, indexing by Google Dataset Search
OBOfoundry like resources: mapping to bio entities of relevance
know limitation:
project information may be lacking -> extend by adding a project_schema.json component
The text was updated successfully, but these errors were encountered:
Scope clarity:
what is that we are cataloguing: Project AND Datasets
Project: should we index all known IMI projects listed from IMI site or only those FAIRplus (and eTRIKS) have engaged with
Datasets: complex objects with many data modalities and many dataset releases (accrual datasets, longitudinal datasets -> versioning, relevant for all prospective cases, ie IMI engaging currently with FAIRplus). Note: for many finished projects, this is irrelevant (the retrospective use case
initial representation with DATS model:
main advantage:
json schema validation
json context files for:
know limitation:
project_schema.json
componentThe text was updated successfully, but these errors were encountered: