Skip to content

Commit

Permalink
placeholder for orchestrator in stand-alone setup
Browse files Browse the repository at this point in the history
  • Loading branch information
blankdots committed Nov 28, 2023
1 parent 0f405ec commit 6a6a652
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/structure.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ In a Federated setup, the `FederatedEGA` archive node setup locally need to exch
2. The process of the Submitter annotating the archived data in an online portal at `CentralEGA`, resulting in assigned accession numbers for items such as DataSet, Study, Files etc.


In a stand-alone setup, the deployed service has less remote synchronisation to worry about, but on the other hand need more components to also handle annotations/meta-data locally, as well as to deal with identifiers etc.
In a stand-alone setup, the deployed service has less remote synchronisation to worry about, but on the other hand more components might be required (e.g ([orchestrator](services/orchestrator))) to also handle annotations/meta-data locally, as well as to deal with identifiers etc.

The NeIC SDA is targeting both use cases in several projects in the Nordics.

Expand Down

0 comments on commit 6a6a652

Please sign in to comment.