Skip to aside Skip to content Skip to footer

Hosting environments: 7. Deploy to hosting environments

%%{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 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 class step_7 highlight 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 deploys the research object, its alternative representations and any supporting resources to one or more hosting environments that meet the functional, operational, security and preservation requirements of the FAIRification activity.

A hosting environment may be a domain repository, general-purpose repository, institutional service, object store, package registry, version-control platform, workflow repository, catalogue, knowledge-graph platform, secure processing environment or project-operated infrastructure.

The environment from which the research object was obtained may be retained, upgraded or complemented as part of the deployment. Source and target are roles: they may be fulfilled by the same environment, by overlapping services or by different systems.

Deployment does not have to wait until every FAIRification task is complete. Canonical and alternative representations may be deployed iteratively to development, staging or production environments during successive FAIRification cycles.

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

Research object access

Hosting
" } ~~~ hosting__ft-data-retrieval@{ shape: card, label: "

Research object retrieval

Hosting
" } ~~~ hosting__ft-data-hosting@{ shape: card, label: "

Research object deposition

Hosting
" } ~~~ hosting__ft-data-versioning@{ shape: card, label: "

Research object versioning

Hosting
" } hosting__ft-data-transfer@{ shape: card, label: "

Research object transfer

Hosting
" } ~~~ hosting__ft-data-licensing@{ shape: card, label: "

Rights and reuse conditions

Hosting
" } ~~~ hosting__ft-data-anonymisation@{ shape: card, label: "

Privacy and disclosure control

Hosting
" } ~~~ hosting__ft-data-release@{ shape: card, label: "

Release management

Hosting
" } end class hosting__ft-data-access fixed_height_card click hosting__ft-data-access href "/interoperability_2024-26/template_step_1" class hosting__ft-data-retrieval fixed_height_card click hosting__ft-data-retrieval href "/interoperability_2024-26/template_step_1" class hosting__ft-data-hosting fixed_height_card click hosting__ft-data-hosting href "/interoperability_2024-26/template_step_7" class hosting__ft-data-hosting highlight class hosting__ft-data-versioning fixed_height_card click hosting__ft-data-versioning href "/interoperability_2024-26/template_step_7" class hosting__ft-data-versioning highlight class hosting__ft-data-transfer fixed_height_card click hosting__ft-data-transfer href "/interoperability_2024-26/template_step_7" class hosting__ft-data-transfer highlight class hosting__ft-data-licensing fixed_height_card click hosting__ft-data-licensing href "/interoperability_2024-26/template_step_8" class hosting__ft-data-anonymisation fixed_height_card click hosting__ft-data-anonymisation href "/interoperability_2024-26/template_step_8" class hosting__ft-data-release fixed_height_card click hosting__ft-data-release href "/interoperability_2024-26/template_step_8" hosting

Research object deposition

Persist, manage, expose and operate research objects, metadata, mappings, alternative representations and supporting services in an environment suitable for their intended uses.

This capability includes selecting or confirming a hosting environment, deploying the required objects and services, and establishing the storage, preservation, discovery, security, operational and sustainability arrangements needed to support them.

The capability may be provided by an external repository, institutional infrastructure, community platform, secure environment, commercial provider or project-operated service. The FAIRification team does not necessarily have to operate the environment itself.

Resources

4 ELIXIR Stories items
4 FAIR Metroline items
7 FAIR Cookbook items

Research object versioning

Identify, relate, preserve and manage changes to deployed research objects and their associated metadata, mappings, representations and services.

This capability allows users and machines to distinguish a changing research object from a particular reproducible version and to understand how versions, releases, components and derived representations relate.

The capability may be provided by a repository, version-control system, package registry, storage service, workflow platform or project-operated versioning process.

Resources

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

Research object transfer

Move, ingest, synchronise or register research objects and associated information between environments securely, completely and verifiably.

This capability may involve transferring files or packages, migrating databases or object stores, depositing through a repository interface, synchronising environments or registering an object in place without copying it.

Transfer is distinct from retrieval. Retrieval concerns what a user or service can select and receive. Transfer concerns the operational movement or ingestion of research objects between source, staging and target environments.

Transfer is not required where the research object remains in place and the existing environment is upgraded to fulfil the target role.

Resources

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