Skip to aside Skip to content Skip to footer

Content & context: 2. Adopt a domain model

%%{init: { }}%% flowchart LR; %% General diagram structure start@{ shape: sm-circ } === step_1 edge__step_1_process@==> step_2 edge__step_2_process@==> step_3 edge__step_3_process@==> step_4 edge__step_4_process@==> step_5 edge__step_5_process@==> step_6 edge__step_6_process@==> step_7 edge__step_7_process@==> step_8 edge__step_8_process@==> finish@{ shape: framed-circle } subgraph process["Course of action"] step_1 step_2 step_3 step_4 step_5 step_6 step_7 step_8 end %% Labels step_1("`
Hosting
Obtain the research object`") click step_1 href "/interoperability_2024-26/template_step_1" "Go to Obtain the research object" class step_1 step_1 step_2("`
Content
Adopt a domain model`") click step_2 href "/interoperability_2024-26/template_step_2" "Go to Adopt a domain model" class step_2 step_2 class step_2 highlight step_3("`
Content
Select identifier schemes`") click step_3 href "/interoperability_2024-26/template_step_3" "Go to Select identifier schemes" class step_3 step_3 step_4("`
Formats
Convert to standard formats`") click step_4 href "/interoperability_2024-26/template_step_4" "Go to Convert to standard formats" class step_4 step_4 step_5("`
Content
Harmonise content elements`") click step_5 href "/interoperability_2024-26/template_step_5" "Go to Harmonise content elements" class step_5 step_5 step_6("`
Formats
Transform to match use cases`") click step_6 href "/interoperability_2024-26/template_step_6" "Go to Transform to match use cases" class step_6 step_6 step_7("`
Hosting
Deploy to hosting environments`") click step_7 href "/interoperability_2024-26/template_step_7" "Go to Deploy to hosting environments" class step_7 step_7 step_8("`
Hosting
Activate sharing and reuse`") click step_8 href "/interoperability_2024-26/template_step_8" "Go to Activate sharing and reuse" class step_8 step_8

This step establishes a shared understanding of the types of research objects, components, domain concepts and relationships involved in the FAIRification activity, and selects or defines a domain model to guide the work.

A domain model describes the entities, concepts, properties, relationships and constraints that are relevant to a particular subject area or intended use. It provides a conceptual basis for later decisions about identifiers, metadata, standards, vocabularies, mappings and hosting. The model may already be explicit in a schema, metadata profile or community specification. It may instead be implicit in the structure, documentation or practices surrounding the existing research object. The project may reuse an established model, adapt or extend one, combine compatible models, or define a new model where no suitable option exists.

This step builds on the research object scope, component inventory, metadata, documentation, provenance and dependencies obtained in Step 1. It identifies what the current research object represents, what the intended uses require and where the current and required models differ. Adopting a domain model does not mean that the research object must be transformed immediately. This step makes and records the modelling decisions that will guide implementation in later Template steps.

Use this step during project examination to identify relevant types, models and requirements and to compare the current and required states. During an implementation cycle, use it to select, adapt or define the domain model that will guide the agreed FAIRification work.

%%{init: { "htmlLabels": true, "flowchart": { "wrappingWidth": 120, "diagramPadding": 10, "padding": 1, "rankSpacing": 10, "nodeSpacing": 10, "subGraphTitleMargin": { "top": 5, "bottom": 15 } } }}%% flowchart TB; subgraph content[Content] direction LR content__ft-identify-data-types@{ shape: card, label: "

Identify research object types

Content
" } ~~~ content__ft-select-domain-model@{ shape: card, label: "

Select or define a domain model

Content
" } ~~~ content__ft-identifier-minting@{ shape: card, label: "

Identifier minting

Content
" } ~~~ content__ft-identifier-reuse@{ shape: card, label: "

Identifier discovery and reuse

Content
" } content__ft-select-data-vocabularies@{ shape: card, label: "

Vocabulary discovery and selection

Content
" } ~~~ content__ft-develop-data-vocabularies@{ shape: card, label: "

Vocabulary extension and development

Content
" } ~~~ content__ft-anotate-with-data-vocabularies@{ shape: card, label: "

Semantic annotation

Content
" } ~~~ content__ft-manage-vocabularies@{ shape: card, label: "

Vocabulary management

Content
" } end class content__ft-identify-data-types fixed_height_card click content__ft-identify-data-types href "/interoperability_2024-26/template_step_2" class content__ft-identify-data-types highlight class content__ft-select-domain-model fixed_height_card click content__ft-select-domain-model href "/interoperability_2024-26/template_step_2" class content__ft-select-domain-model highlight class content__ft-identifier-minting fixed_height_card click content__ft-identifier-minting href "/interoperability_2024-26/template_step_3" class content__ft-identifier-reuse fixed_height_card click content__ft-identifier-reuse href "/interoperability_2024-26/template_step_3" class content__ft-select-data-vocabularies fixed_height_card click content__ft-select-data-vocabularies href "/interoperability_2024-26/template_step_5" class content__ft-develop-data-vocabularies fixed_height_card click content__ft-develop-data-vocabularies href "/interoperability_2024-26/template_step_5" class content__ft-anotate-with-data-vocabularies fixed_height_card click content__ft-anotate-with-data-vocabularies href "/interoperability_2024-26/template_step_5" class content__ft-manage-vocabularies fixed_height_card click content__ft-manage-vocabularies href "/interoperability_2024-26/template_step_5" content

Identify research object types

Identify and describe the types of research objects and components included in the FAIRification activity.

Research object type identification informs the selection of appropriate domain models, metadata profiles, identifier schemes, standards, vocabularies and target hosting environments. It also helps determine which relationships and dependencies must be preserved.

Distinguish between:

  • Research object types, such as datasets, software, workflows, models, notebooks, protocols, and compound research objects.
  • Components, such as files, records, modules, workflow steps, metadata documents and referenced resources.
  • Domain entity types, such as samples, organisms, participants, observations, assays, images, sequences and variables.
  • Representation types, such as schemas, file formats and serialisations, which are examined and implemented in later steps.

A research object may have more than one type or contain several different types of components. Classification should therefore describe the composition of the research object set rather than force each object into a single category.

Resources

4 ELIXIR Stories items
4 FAIR Metroline items
2 FAIR Cookbook items

Select or define a domain model

Select, adapt or define a model that adequately represents the concepts, entities, relationships and constraints required by the FAIRification activity.

This connects the research object and domain model to practical identification requirements. It determines whether identifiers are needed for the research object set, individual objects, versions, components, domain entities and related resources, and whether existing identifiers can meet those needs.
The capability may be provided through expertise within the project or through support from data stewards, repository specialists, domain communities, identifier-service providers or other infrastructure operators.

Resources