From 478d3915425859e76d18125edf917efe3bfeb302 Mon Sep 17 00:00:00 2001 From: Tobias Bengfort Date: Tue, 17 Sep 2019 13:52:19 +0200 Subject: [PATCH 1/3] add section about internal/external steps --- source/concepts/what.rst | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/source/concepts/what.rst b/source/concepts/what.rst index 7661245..cc2c8e9 100644 --- a/source/concepts/what.rst +++ b/source/concepts/what.rst @@ -52,3 +52,42 @@ pseudonym service Of these, castellum implements a recruting database, a contact database, and a pseudonym service. All data that is actually related to studies must be stored separately. + +Boundaries +---------- + +Internal steps +`````````````` + +Some steps need to be deeply integrated with contact management. A good example +for this is the recruitment, which is centered around communication with the +subject. + +Django works best when all data is in the same database. However, is is also +possible to split some data to a separate database. We use this mechanism for +contact data. The data is still held internally, but there is an additional +layer of security. + +External steps +`````````````` + +Some steps should be kept completely separated. For example, research data +should not be stored inside castellum. Note that there is no integration +necessary because research data is (or at least could be) handled by completely +different staff than contact data and recruitment. + +.. note:: + There are only two notable exceptions to this rule: Study participations and + search attributes both contain traces of research data, but are required for + the recruitment process. + +Steps will also be kept out of Castellum if there are well established +processes that do not need to be replaced. Examples might include calendars or +room management. + +The integration with external processes is usually manual. For example, a +pseudonym generated by castellum would usually be entered into a MRI device by +hand. + +However, if sufficiently established protocols are available, we try to support +them. For example, authentication can be handled via a central LDAP service. -- GitLab From 685dbc2aeeb7d81139a339cedc81b6c210f5202f Mon Sep 17 00:00:00 2001 From: Bengfort Date: Tue, 17 Sep 2019 14:16:28 +0200 Subject: [PATCH 2/3] Apply suggestion to source/concepts/what.rst --- source/concepts/what.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/concepts/what.rst b/source/concepts/what.rst index cc2c8e9..c08dfde 100644 --- a/source/concepts/what.rst +++ b/source/concepts/what.rst @@ -63,7 +63,7 @@ Some steps need to be deeply integrated with contact management. A good example for this is the recruitment, which is centered around communication with the subject. -Django works best when all data is in the same database. However, is is also +Django works best when all data is in the same database. However, it is also possible to split some data to a separate database. We use this mechanism for contact data. The data is still held internally, but there is an additional layer of security. -- GitLab From 8d81c86a78fc20e9bfd8aeb030a9061bbc455606 Mon Sep 17 00:00:00 2001 From: Tobias Bengfort Date: Wed, 6 Nov 2019 13:22:56 +0100 Subject: [PATCH 3/3] be more explicit about UI integration --- source/concepts/what.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/concepts/what.rst b/source/concepts/what.rst index c08dfde..7c60aff 100644 --- a/source/concepts/what.rst +++ b/source/concepts/what.rst @@ -72,9 +72,9 @@ External steps `````````````` Some steps should be kept completely separated. For example, research data -should not be stored inside castellum. Note that there is no integration -necessary because research data is (or at least could be) handled by completely -different staff than contact data and recruitment. +should not be stored inside castellum. Note that there is no need for a +streamlined, integrated UI because research data is (or at least could be) +handled by completely different staff than contact data and recruitment. .. note:: There are only two notable exceptions to this rule: Study participations and -- GitLab