search

CLARIAH / clariah-plus

This is the project planning repository for the CLARIAH-PLUS project. It groups all technical documents and discussions pertaining to CLARIAH-PLUS in a central place and should facilitate findability, transparency and project planning, for the project as a whole.
9 stars 6 forks source link

Define dataset description data model #66

Open ddeboer opened 2 years ago

ddeboer commented 2 years ago

Describe an RDF data model for storing dataset descriptions, which must contain items such as:

A starting point could be the NDE Requirements for Datasets. Note that the CLARIAH data model will only be used by the CLARIAH registry internally rather than prescribed to dataset description publishers (as in the case of NDE).

I recommend starting from a minimal common denominator ontology between the different institutions (#47), which can be extended later for more expressiveness. This minimal ontology must align with basic facets in Ineo (#57).

jblom commented 2 years ago

@ddeboer yes we should not mix-up this internal ontology (actually data model) with something we publish to the world, so we can keep it very to the point and simple (and gradually extend it later on; also possible to be able to publish to more elaborate standards).

ddeboer commented 2 years ago

@jblom Actually I intended this process:

  1. Harvest dataset descriptions from heterogenous CLARIAH partner registries.
  2. Map the heterogenous data to the CLARIAH data model and store that in the CLARIAH Dataset Registry.
  3. Expose dataset descriptions in the CLARIAH data model to the outside world (including Ineo) through APIs (#67).

So the data model used to store dataset descriptions is the same as the data model exposed to the outside world.

jblom commented 2 years ago

@ddeboer yup agree. Sorry for being a bit unclear.