From 3408a813e321dc4c35d3a01418a02db61dbaf976 Mon Sep 17 00:00:00 2001 From: Tobias Bengfort Date: Tue, 19 May 2020 11:19:07 +0200 Subject: [PATCH 1/2] refine what --- source/concepts/what.rst | 63 ++++++++++++++++------------------------ 1 file changed, 25 insertions(+), 38 deletions(-) diff --git a/source/concepts/what.rst b/source/concepts/what.rst index 76d53ce..529a4f4 100644 --- a/source/concepts/what.rst +++ b/source/concepts/what.rst @@ -13,25 +13,7 @@ Classification -------------- You can think of many kinds of scientific databases that handle personal -information: - -study database - contains all data that is collected during a study - - only the researchers that are involved with the study have access to - the data - -study archive - contains data from past studies that is relevant for scientific - reasons, e.g. reproducibility - -research archive - contains data that has been collected during one study, but may be - reused in another one - - reusing data saves time for both the researcher and the test subject - - examples include image archives and biobanks +information. What castellum is: recruting database contains some data about (potential) test subjects that allows you to @@ -49,30 +31,35 @@ contact database pseudonym service used to store relations between the different datasets -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. +What castellum is not: + +study database + contains all data that is collected during a study + + only the researchers that are involved with the study have access to + the data + +study archive + contains data from past studies that is relevant for scientific + reasons, e.g. reproducibility -Boundaries ----------- +research archive + contains data that has been collected during one study, but may be + reused in another one -Internal steps -`````````````` + reusing data saves time for both the researcher and the test subject -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. + examples include image archives and biobanks -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. +How do we decide what to integrate? +----------------------------------- -External steps -`````````````` +Some workflows need to be deeply integrated with contact management. A good +example for this is the recruitment, which is centered around communication +with the subject. These workflows are integrated in castellum. -Some steps should be kept completely separated. For example, research data -should not be stored inside castellum. Note that there is no need for a +Any other workflows should be kept completely separated. For example, research +data 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. @@ -81,7 +68,7 @@ handled by completely different staff than contact data and recruitment. 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 +Workflows 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. -- GitLab From 2e17a640b074b2190452a3c50f85e702ab8f99fe Mon Sep 17 00:00:00 2001 From: TiG Date: Fri, 26 Jun 2020 11:28:33 +0200 Subject: [PATCH 2/2] edit to upper case Castellum --- source/concepts/what.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/concepts/what.rst b/source/concepts/what.rst index 529a4f4..18c776c 100644 --- a/source/concepts/what.rst +++ b/source/concepts/what.rst @@ -13,7 +13,7 @@ Classification -------------- You can think of many kinds of scientific databases that handle personal -information. What castellum is: +information. What Castellum is: recruting database contains some data about (potential) test subjects that allows you to @@ -31,7 +31,7 @@ contact database pseudonym service used to store relations between the different datasets -What castellum is not: +What Castellum is not: study database contains all data that is collected during a study @@ -56,10 +56,10 @@ How do we decide what to integrate? Some workflows need to be deeply integrated with contact management. A good example for this is the recruitment, which is centered around communication -with the subject. These workflows are integrated in castellum. +with the subject. These workflows are integrated in Castellum. Any other workflows should be kept completely separated. For example, research -data should not be stored inside castellum. Note that there is no need for a +data 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. @@ -73,7 +73,7 @@ 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 +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 -- GitLab