From 26d94e0789c89693671f2c6e0bb1456949aa0154 Mon Sep 17 00:00:00 2001 From: Stefan Negru Date: Tue, 28 Nov 2023 17:44:54 +0200 Subject: [PATCH] mention use cases rather than projects for setups --- docs/structure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/structure.md b/docs/structure.md index 6feab6e..2d97a77 100644 --- a/docs/structure.md +++ b/docs/structure.md @@ -18,7 +18,7 @@ In a Federated setup, the `FederatedEGA` archive node setup locally need to exch 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. +The NeIC SDA is targeting both types of setup, to open up the use of the re-use of components to more use cases than initially envisioned. ### Container deployment options