Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Data Model for the catalogue: #1

Open
proccaserra opened this issue Feb 13, 2020 · 1 comment
Open

Define Data Model for the catalogue: #1

proccaserra opened this issue Feb 13, 2020 · 1 comment
Assignees

Comments

@proccaserra
Copy link
Contributor

proccaserra commented Feb 13, 2020

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
@proccaserra
Copy link
Contributor Author

review list of IMI projects to understand need to capture relations between projects (e.g. projects with subproject)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants