Slight changes to services description

app/__init__.py

@@ -99,7 +99,7 @@ def create_app(config: Config = Config) -> Flask:
 
     from .users import bp as users_blueprint
     default_breadcrumb_root(users_blueprint, '.users')
-    app.register_blueprint(users_blueprint, cli_group='user', url_prefix='/users')
+    app.register_blueprint(users_blueprint, url_prefix='/users')
 
     from .workshops import bp as workshops_blueprint
     app.register_blueprint(workshops_blueprint, url_prefix='/workshops')

app/corpora/routes.py

@@ -97,14 +97,14 @@ def analysis(corpus_id):
     )
 
 
-@bp.route('/<hashid:corpus_id>/follow/<token>')
-def follow_corpus(corpus_id, token):
-    corpus = Corpus.query.get_or_404(corpus_id)
-    if current_user.follow_corpus_by_token(token):
-        db.session.commit()
-        flash(f'You are following "{corpus.title}" now', category='corpus')
-        return redirect(url_for('corpora.corpus', corpus_id=corpus_id))
-    abort(403)
+# @bp.route('/<hashid:corpus_id>/follow/<token>')
+# def follow_corpus(corpus_id, token):
+#     corpus = Corpus.query.get_or_404(corpus_id)
+#     if current_user.follow_corpus_by_token(token):
+#         db.session.commit()
+#         flash(f'You are following "{corpus.title}" now', category='corpus')
+#         return redirect(url_for('corpora.corpus', corpus_id=corpus_id))
+#     abort(403)
 
 
 @bp.route('/import', methods=['GET', 'POST'])

app/templates/_base/_modals/_manual/01_introduction.html.j2

@@ -1,9 +1,34 @@
 <h3 class="manual-chapter-title">Introduction</h3>
+<h4>Introduction</h4>
 <p>
-  nopaque is a web-based digital working environment. It implements a
-  workflow based on the research process in the humanities and supports its
-  users in processing their data in order to subsequently apply digital
-  analysis methods to them. All processes are implemented in a specially
-  provided cloud environment with established open source software. This
-  always ensures that no personal data of the users is disclosed.
+  Nopaque is a web application that offers different services and tools to support 
+  researchers working with image and text-based data. These services are logically 
+  connected and build upon each other. They include:
 </p>
+ <ol style="list-style-type:disc; margin-left:2em; padding-bottom:0;">
+  <li><b>File setup</b>, which converts and merges different data  (e.g., books, letters) 
+  for further processing.</li>
+  <li><b>Image-to-text conversion tools:</b></li>
+    <ol style="list-style-type:circle; margin-left:1em; padding-bottom:0;"><li><b>Optical Character Recognition</b> converts photos and 
+    scans into text data, making them machine-readable.</li>
+    <li><b>Transkribus HTR (Handwritten Text Recognition) Pipeline</b> (currently deactivated)* 
+    also converts images into text data, making them machine-readable.</li>
+    </ol>
+  <li><b>Natural Language Processing</b> extracts information from your text via 
+  computational linguistic data processing (tokenization, lemmatization, part-of-speech 
+  tagging and named-entity recognition.</li>
+  <li><b>Corpus analysis</b> makes use of CQP Query Language to search through text 
+  corpora with the aid of metadata and Natural Language Processing tags.</li>
+ </ol>
+
+Nopaque also features a <b>Social Area</b>, where researchers can create a personal profile, connect with other users and share corpora if desired.
+These services can be accessed from the sidebar in nopaque.
+All processes are implemented in a specially provided cloud environment with established open-source software. 
+This always ensures that no personal data of the users is disclosed.
+<p>
+*Note: the Transkribus HTR Pipeline is currently 
+deactivated; we are working on an alternative solution. You can try using Tesseract OCR, 
+though the results will likely be poor.
+</p>
+
+

app/templates/_base/_modals/_manual/02_getting_started.html.j2

@@ -0,0 +1,104 @@
+<h3 class="manual-chapter-title">Getting Started</h3>
+<h4>Getting Started</h4>
+<p>
+In this section, we will take you through all the steps you need to start analyzing your data with nopaque.
+</p>
+
+<div style="border: 1px solid; padding-left: 20px; margin-right: 400px; margin-bottom: 40px;">
+  <h5>Content</h5>
+  <ol style="list-style-type:disc">
+    <li><a href="#registration-and-login">Registration and login</a></li>
+    <li><a href="#preparing-files">Preparing files for analysis</a></li>
+    <li><a href="#converting-a-pdf-into-text">Converting a PDF into text data</a></li>
+    <li><a href="#extracting-linguistic-data">Extracting linguistic data from text</a></li>
+    <li><a href="#creating-a-corpus">Creating a corpus</a></li>
+    <li><a href="#analyzing-a-corpus">Analyzing a corpus</a></li>
+  </ol>
+</div>
+
+<p></p>
+
+<h5 id="registration-and-login">Registration and login</h5>
+<p>Before you can begin using nopaque, you will need to create a personal user account. 
+Open the menu (three dots) at the top right of the screen and choose “Register.” Enter 
+the required details listed on the registration page (username, password, email address). 
+After verifying your account via the link sent to your email, you can log in.</p>
+
+<h5 id="preparing-files">Preparing files for analysis</h5>
+<p>A few steps need to be taken before images, scans, or other text data are ready for 
+analysis in nopaque. The SpaCy NLP Pipeline service can only extract linguistic data 
+from texts in plain text (.txt) format. If your text is already in this format, you 
+can skip the next steps and go directly to <b>Extracting linguistic data from text</b>. 
+Otherwise, the next steps assume that you are starting off with image data.</p>
+<p>
+First, all data needs to be converted into PDF format. Using the <b>File Setup</b> service, 
+you can bundle images together – even of different formats – and convert them all into 
+one PDF file. Note that the File Setup service will sort the images based on their file 
+name in ascending order. It is thus recommended to name them accordingly, for example: 
+page-01.png, page-02.jpg, page-03.tiff.
+</p>
+<p>
+Add a title and description to your job and select the File Setup version* you want to use.
+After uploading the images and completing the File Setup job, the list of files added 
+can be seen under “Inputs.” Further below, under “Results,” you can find and download 
+the PDF output.</p>
+
+<h5 id="converting-a-pdf-into-text">Converting a PDF into text data</h5>
+<p>Select an image-to-text conversion tool depending on whether your PDF is primarily 
+composed of handwritten text or printed text. For printed text, select the <b>Tesseract OCR 
+Pipeline</b>. For handwritten text, select the <b>Transkribus HTR Pipeline</b>. Select the desired 
+language model or upload your own. Select the version* of Tesseract OCR you want to use 
+and click on submit to start the conversion. When the job is finished, various output 
+files can be seen and downloaded further below, under “Results.” You may want to review 
+the text output for errors and coherence. (Note: the Transkribus HTR Pipeline is currently 
+deactivated; we are working on an alternative solution. You can try using Tesseract OCR, 
+though the results will likely be poor.)
+</p>
+
+<h5 id="extracting-linguistic-data">Extracting linguistic data from text</h5>
+<p>The <b>SpaCy NLP Pipeline</b> service extracts linguistic information from plain text files 
+(in .txt format). Select the corresponding .txt file, the language model, and the 
+version* you want to use. When the job is finished, find and download the files in 
+<b>.json</b> and <b>.vrt</b> format under “Results.”</p>
+
+<h5 id="creating-a-corpus">Creating a corpus</h5>
+<p>Now, using the files in .vrt format, you can create a corpus. This can be done 
+in the <a href="{{ url_for('main.dashboard') }}">Dashboard</a> or 
+<a href="{{ url_for('services.corpus_analysis') }}">Corpus Analysis</a> sections under “My Corpora.” Click on “Create corpus” 
+and add a title and description for your corpus. After submitting, you will automatically 
+be taken to the corpus overview page (which can be called up again via the corpus lists) 
+of your new, still empty corpus. </p>
+<p>
+Further down in the “Corpus files” section, you can add texts in .vrt format 
+(results of the NLP service) to your new corpus. To do this, use the "Add Corpus File" 
+button and fill in the form that appears. Here, you can add 
+metadata to each text. After adding all texts to the corpus, it must 
+be prepared for analysis. This process can be initiated by clicking on the 
+"Build" button under "Actions". 
+On the corpus overview page, you can see information about the current status of 
+the corpus in the upper right corner. After the build process, the status "built" should be shown here.
+Now, your corpus is ready for analysis.</p>
+
+<h5 id="analyzing-a-corpus">Analyzing a corpus</h5>
+<p>Navigate to the corpus you would like to analyze and click on the Analyze button. 
+This will take you to an analysis overview page for your corpus. Here, you can find a 
+visualization of general linguistic information of your corpus, including tokens, 
+sentences, unique words, unique lemmas, unique parts of speech and unique simple parts 
+of speech. You will also find a pie chart of the proportional textual makeup of your 
+corpus and can view the linguistic information for each individual text file. A more 
+detailed visualization of token frequencies with a search option is also on this page.</p>
+<p>From the corpus analysis overview page, you can navigate to other analysis modules: 
+the <b>Query Builder</b> (under <b>Concordance</b>) and the <b>Reader</b>. With the Reader, you can read 
+your corpus texts tokenized with the associated linguistic information. The tokens can 
+be shown as lemmas, parts of speech, words, and can be displayed in different ways: 
+visually as plain text with the option of highlighted entities or as chips.</p>
+<p>The <b>Concordance</b> module allows for more specific, query-oriented text analyses. 
+Here, you can filter out text parameters and structural attributes in different 
+combinations. This is explained in more detail in the Query Builder section of the 
+manual.</p>
+
+<br>
+<br>
+*For all services, it is recommended to use the latest version unless you need a model 
+only available in an earlier version or are looking to reproduce data that was originally generated 
+using an older version.

app/templates/_base/_modals/_manual/02_registration_and_log_in.html.j2

@@ -1,18 +0,0 @@
-<h3 class="manual-chapter-title">Registration and Log in</h3>
-<div class="row">
-  <div class="col s12 m4">
-    <img alt="Registration and Log in" class="materialboxed responsive-img" src="{{ url_for('static', filename='images/manual/registration-and-log-in.png') }}">
-  </div>
-  <div class="col s12 m8">
-    <p>
-      Before you can start using the web platform, you need to create a user
-      account. This requires only a few details: just a user name, an e-mail
-      address and a password are needed. In order to register yourself, fill out
-      the form on the <a href="{{ url_for('auth.register') }}">registration page</a>. After successful registration, the
-      created account must be verified. To do this, follow the instructions
-      given in the automatically sent e-mail. Afterwards, you can log in as
-      usual with your username/email address and password in the log-in form
-      located next to the registration button.
-    </p>
-  </div>
-</div>

app/templates/_base/_modals/_manual/03_dashboard.html.j2

@@ -1,15 +1,22 @@
 <h3 class="manual-chapter-title">Dashboard</h3>
+<h4>About the dashboard</h4>
+<br>
 <div class="row">
   <div class="col s12 m4">
     <img alt="Dashboard" class="materialboxed responsive-img" src="{{ url_for('static', filename='images/manual/dashboard.png') }}">
   </div>
   <div class="col s12 m8">
     <p>
-      The <a href="{{ url_for('main.dashboard') }}">dashboard</a> provides a central overview of all resources assigned to the
-      user. These are <a href="{{ url_for('main.dashboard', _anchor='corpora') }}">corpora</a> and created <a href="{{ url_for('main.dashboard', _anchor='jobs') }}">jobs</a>. Corpora are freely composable
-      annotated text collections and jobs are the initiated file processing
-      procedures. One can search for jobs as well as corpus listings using
-      the search field displayed above them.
+      The <a href="{{ url_for('main.dashboard') }}">dashboard</a> provides a central 
+      overview of all user-specific resources.
+      These are <a href="{{ url_for('main.dashboard', _anchor='corpora') }}">corpora</a>, 
+      created <a href="{{ url_for('main.dashboard', _anchor='jobs') }}">jobs</a>, and 
+      model <a href="{{ url_for('main.dashboard', _anchor='contributions') }}"">contributions</a>. 
+      A <b>corpus</b> is a freely composable annotated text collection. 
+      A <b>job</b> is an initiated file processing procedure. 
+      A <b>model</b> is a mathematical system for pattern recognition based on data examples that have been processed by AI. One can search for jobs as 
+      well as corpus listings using the search field displayed above them on the dashboard. 
+      Uploaded models can be found and edited by clicking on the corresponding service under <b>My Contributions</b>.      
     </p>
   </div>
   <div class="col s12">&nbsp;</div>

app/templates/_base/_modals/_manual/06_services.html.j2

@@ -1,52 +1,107 @@
 <h3 class="manual-chapter-title">Services</h5>
+<h4>Services</h4>
+<p>
+In this section, we will describe the different services nopaque has to offer.
+</p>
+
 <div class="row">
   <div class="col s12 m4">
     <img alt="Services" class="materialboxed responsive-img" src="{{ url_for('static', filename='images/manual/services.png') }}">
   </div>
   <div class="col s12 m8">
     <p>
-      nopaque was designed from the ground up to be modular. This modularity
-      means that the offered workflow provides variable entry and exit points,
-      so that different starting points and goals can be flexibly addressed.
-      Each of these modules are implemented in a self-contained service, each of
-      which represents a step in the workflow. The services are coordinated in
-      such a way that they can be used consecutively. The order can either be
-      taken from the listing of the services in the left sidebar or from the
-      roadmap (accessible via the pink compass in the upper right corner). All
-      services are versioned, so the data generated with nopaque is always
+      Nopaque was designed to be modular. Its modules are implemented in 
+      self-contained <b>services</b>, each of which represents a step in the 
+      workflow. The typical workflow involves using services one after another, 
+      consecutively.
+      The typical workflow order can be taken from the listing of the 
+      services in the left sidebar or from the nopaque manual (accessible via the pink 
+      button in the upper right corner). 
+      The services can also be applied at different starting and ending points, 
+      which allows you to conduct your work flexibly.
+      All services are versioned, so the data generated with nopaque is always
       reproducible.
+      
+      <p>For all services, it is recommended to use the latest version (selected 
+      in the drop-down menu on the service page) unless you need a model 
+      only available in an earlier version or are looking to reproduce data that was originally generated 
+      using an older version.</p>
     </p>
   </div>
 </div>
 
-<h4 class="manual-chapter-title">File Setup</h4>
+
+
+<h4>File Setup</h4>
 <p>
   The <a href="{{ url_for('services.file_setup_pipeline') }}">File Setup Service</a> bundles image data, such as scans and photos,
   together in a handy PDF file. To use this service, use the job form to
   select the images to be bundled, choose the desired service version, and
-  specify a title and description. Please note that the service sorts the
-  images into the resulting PDF file based on the file names. So naming the
-  images correctly is of great importance. It has proven to be a good practice
-  to name the files according to the following scheme:
-  page-01.png, page-02.jpg, page-03.tiff, etc. In general, you can assume
+  specify a title and description.
+  Note that the File Setup service will sort the images based on their file name in 
+  ascending order. It is thus important and highly recommended to name 
+  them accordingly, for example: 
+  page-01.png, page-02.jpg, page-03.tiff. Generally, you can assume
   that the images will be sorted in the order in which the file explorer of
   your operating system lists them when you view the files in a folder
   sorted in ascending order by file name.
 </p>
 
 <h4>Optical Character Recognition (OCR)</h4>
-<p>Coming soon...</p>
+<p>
+  The <a href="{{ url_for('services.tesseract_ocr_pipeline') }}">Tesseract OCR Pipeline</a> 
+  converts image data - like photos and scans - into text data, making them machine-readable. 
+  This step enables you to proceed with the computational analysis of your documents. 
+  To use this service, use the job form to select the file you want to convert into text data. 
+  Then, choose the language model and service version you would like to use. Enter a title and description for your file and then 
+  submit your job. Once the job is finished, the results can be found and downloaded further below on the page, under 
+  the section labeled "Inputs."
+
+</p>
 
 <h4>Handwritten Text Recognition (HTR)</h4>
-<p>Coming soon...</p>
+<p>The Transkribus HTR Pipeline is currently 
+deactivated. We are working on an alternative solution. In the meantime, you can 
+try using Tesseract OCR, though the results will likely be poor.</p>
 
 <h4>Natural Language Processing (NLP)</h4>
-<p>Coming soon...</p>
+<p>The <a href="{{ url_for('services.spacy_nlp_pipeline') }}">SpaCy NLP Pipeline</a> extracts 
+information from plain text files (.txt format) via computational linguistic data processing 
+(tokenization, lemmatization, part-of-speech tagging and named-entity recognition). 
+To use this service, select the .txt file that you want to extract this information from. 
+Then select the language model and the version you want to use. Once the job is finished, you can find and download the files in 
+<b>.json</b> and <b>.vrt</b> format under the section labeled “Results.”</p>
 
 <h4>Corpus Analysis</h4>
 <p>
-  With the corpus analysis service, it is possible to create a text corpus
-  and then explore it in an analysis session. The analysis session is realized
+  With the <a href="{{ url_for('services.corpus_analysis') }}">Corpus Analysis</a> 
+  service, it is possible to create a text corpus
+  and then explore through it with analytical tools. The analysis session is realized
   on the server side by the Open Corpus Workbench software, which enables
-  efficient and complex searches with the help of the CQP Query Language.
+  efficient and complex searches with the help of the CQP Query Language.</p>
+  <p>
+  To use this service, navigate to the corpus you would like to analyze and click on the Analyze button. 
+  This will take you to an analysis overview page for your corpus. Here, you can find 
+  a visualization of general linguistic information of your corpus, including tokens, 
+  sentences, unique words, unique lemmas, unique parts of speech and unique simple 
+  parts of speech. You will also find a pie chart of the proportional textual makeup 
+  of your corpus and can view the linguistic information for each individual text file. 
+  A more detailed visualization of token frequencies with a search option is also on 
+  this page.
+  </p>
+  <p>
+  From the corpus analysis overview page, you can navigate to other analysis modules: 
+  the Query Builder (under Concordance) and the Reader. 
+  </p>
+  <p>
+  With the <b>Reader</b>, you can read your corpus texts tokenized with the associated linguistic information. The tokens 
+  can be shown as lemmas, parts of speech, words, and can be displayed in different 
+  ways: visually as plain text with the option of highlighted entities or as chips.
+  </p>
+  <p>
+  The Concordance module allows for more specific, query-oriented text analyses. 
+  Here, you can filter out text parameters and structural attributes in different 
+  combinations. This is explained in more detail in the <b>Query Builder</b> section of the 
+  manual.
+  </p>
 </p>

app/templates/_base/_modals/_manual/08_cqp_query_language.html.j2

@@ -1,5 +1,22 @@
 <h3 class="manual-chapter-title">CQP Query Language</h3>
-<p>Within the Corpus Query Language, a distinction is made between two types of annotations: positional attributes and structural attributes. Positional attributes refer to a token, e.g. the word "book" is assigned the part-of-speech tag "NN", the lemma "book" and the simplified part-of-speech tag "NOUN" within the token structure. Structural attributes refer to text structure-giving elements such as sentence and entity markup. For example, the markup of a sentence is represented in the background as follows:</p>
+<h4 id="cqp-query-language">CQP Query Language</h4>
+<p>In this section, we will provide some functional explanations of the properties of the Corpus Query Language. This includes 
+the types of linguistic attributes one can work with and how to use them in your query.</p>
+
+<div style="border: 1px solid; padding-left: 20px; margin-right: 400px; margin-bottom: 40px;">
+  <h5>Content</h5>
+  <ol style="list-style-type:disc">
+    <li><a href="#overview-annotations">Overview of annotation types</a></li>
+    <li><a href="#positional-attributes">Positional attributes</a></li>
+    <li><a href="#searching-positional-attributes">How to search for positional attributes</a></li>
+    <li><a href="#structural-attributes">Structural attributes</a></li>
+    <li><a href="#searching-structural-attributes">How to search for structural attributes</a></li>
+
+  </ol>
+</div>
+
+<h4 id="overview-annotations">Overview of annotation types</h4>
+<p>Within the Corpus Query Language, a distinction is made between two types of annotations: <b>positional attributes</b> and <b>structural attributes</b>. Positional attributes refer to a token, e.g. the word "book" is assigned the part-of-speech tag "NN", the lemma "book" and the simplified part-of-speech tag "NOUN" within the token structure. Structural attributes refer to text structure-giving elements such as sentence and entity markup. For example, the markup of a sentence is represented in the background as follows:</p>
 <pre>
   <code>
     <span class="green-text">&lt;s&gt;                                     structural attribute</span>
@@ -13,7 +30,7 @@
   </code>
 </pre>
 
-<h4>Positional attributes</h4>
+<h4 id="positional-attributes">Positional attributes</h4>
 <p>Before you can start searching for positional attributes (also called tokens), it is necessary to know what properties they contain.</p>
 <ol>
   <li><span class="blue-text"><b>word</b></span>: The string as it is also found in the original text</li>
@@ -33,7 +50,7 @@
   </li>
 </ol>
 
-<h5>Searching for positional attributes</h5>
+<h5 id="searching-positional-attributes">How to search for positional attributes</h5>
 <div>
   <p>
     <b>Token with no condition on any property (also called <span class="blue-text">wildcard token</span>)</b><br>
@@ -118,7 +135,7 @@
   <pre style="margin-top: 0;"   ><code>         ^             ^ the braces indicate the start and end of an option group</code></pre>
 </div>
 
-<h4>Structural attributes</h4>
+<h4 id="structural-attributes">Structural attributes</h4>
 <p>nopaque provides several structural attributes for query. A distinction is made between attributes with and without value.</p>
 <ol>
   <li><span class="green-text"><b>s</b></span>: Annotates a sentence</li>
@@ -153,7 +170,7 @@
   </li>
 </ol>
 
-<h5>Searching for structural attributes</h5>
+<h5 id="searching-structural-attributes">How to search for structural attributes</h5>
 <pre><code>&lt;ent&gt; [] &lt;/ent&gt;;                       A one token long entity of any type</code></pre>
 <pre><code>&lt;ent_type="PERSON"&gt; [] &lt;/ent_type&gt;;     A one token long entity of type PERSON</code></pre>
 <pre><code>&lt;ent_type="PERSON"&gt; []* &lt;/ent_type&gt;;    Entity of any length of type PERSON</code></pre>

app/templates/_base/_modals/_manual/09_query_builder.html.j2

@@ -1,27 +1,12 @@
 <h3 class="manual-chapter-title">Query Builder Tutorial</h3>
-<h4>Overview</h4>
-<p>The query builder can be accessed via "My Corpora" or "Corpus Analysis" in the sidebar options. 
-Select the desired corpus and click on the "Analyze" and then "Concordance"
-buttons to open the query builder.</p>
-<p>The query builder uses the Corpus Query Language (CQL) to help you make a query for analyzing your texts. 
-In this way, it is possible to filter out various types of text parameters, for 
-example, a specific word, a lemma, or you can set part-of-speech 
-tags (pos) that indicate the type of word you are looking for (a noun, an 
-adjective, etc.). In addition, you can also search for structural attributes, 
-or specify your query for a token (word, lemma, pos) via entity typing. And of 
-course, the different text parameters can be combined.</p>
-<p>Tokens and structural attributes can be added by clicking on the "+" button
-(the "input marker") in the input field or the labeled buttons below it. Elements 
-added are shown as chips. These can be reorganized using drag and drop. The input 
-marker can also be moved in this way. Its position shows where new elements will be added. <br>
-A "translation" of your query into Corpus Query Language (CQL) is shown below.</p>
-<p>Advanced users can make direct use of the Corpus Query Language (CQL) by switching to "expert mode" via the toggle button.</p>
-<p>The entire input field can be cleared using the red trash icon on the right.</p>
-<br>
+<h4>Query Builder</h4>
+<p>In this section, we will provide you with more detailed instructions on how to use the Query Builder - 
+nopaque's main user-friendly tool for finding and analyzing different linguistic elements of your texts.</p>
 
 <div style="border: 1px solid; padding-left: 20px; margin-right: 400px; margin-bottom: 40px;">
   <h5>Content</h5>
   <ol style="list-style-type:disc">
+    <li><a href="#general-overview">General Overview</a></li>
     <li><a href="#add-new-token-tutorial">Add a new token to your query</a></li>
     <li><a href="#edit-options-tutorial">Options for editing your query</a></li>
     <li><a href="#add-structural-attribute-tutorial">Add structural attributes to your query</a></li>
@@ -29,6 +14,33 @@ A "translation" of your query into Corpus Query Language (CQL) is shown below.</
   </ol>
 </div>
 
+<h4 id="general-overview">General Overview</h4>
+<p>The Query Builder can be accessed via <a href=" {{ url_for('main.dashboard') }}">My Corpora</a> or <a href=" {{ url_for('services.corpus_analysis') }}">Corpus Analysis</a> in the sidebar options. 
+Click on the corpus you wish to analyze. You will be sent to its corpus overview page.
+Here, click on <b>Analyze</b> to reach the analysis page.
+The analysis page features different options for analyzing your corpus, including 
+visualizations and a <b>Reader</b> module. In this case, we want to open the query builder. 
+To do so, click on the <b>Concordance</b> button on the top of the page.</p>
+<p>The query builder uses the <b>Corpus Query Language (CQL)</b> to help you make a query for analyzing your texts.
+In this way, it is possible to filter out various types of text parameters, for 
+example, a specific word, a lemma, or you can set part-of-speech 
+tags (pos) that indicate the type of word you are looking for (a noun, an 
+adjective, etc.). In addition, you can also search for structural attributes, 
+or specify your query for a token (word, lemma, pos) via entity typing. And of 
+course, the different text parameters can be combined.</p>
+<p>Tokens and structural attributes can be added by clicking on the <b>"+"</b> button
+(what we call the "input marker") in the input field or the labeled buttons below it. Elements 
+added are shown as chips. These can be reorganized using drag and drop. The input 
+marker can also be moved in this way. Its position shows where new elements will be added. <br>
+A "translation" of your query into Corpus Query Language (CQL) will be displayed underneath the query field.</p>
+<p>For more information, see our <b>manual section for the Corpus Query Language.</b>
+<br>
+Advanced users can make direct use of CQL by switching to <b>expert mode</b> via the toggle button.
+</p>
+<p>The entire input field can be cleared using the red trash icon on the right.</p>
+<br>
+
+
 {# Add Token Tutorial #}
 <div>
   <hr>
@@ -37,8 +49,8 @@ A "translation" of your query into Corpus Query Language (CQL) is shown below.</
   <h4 id="add-new-token-tutorial">Add new token to your Query</h4>
   <p>If you are only looking for a specific token, you can click on the left 
   button and select the type of token you are looking for from the drop-down menu. 
-  By default "Word" is selected. </p>
-  <br>
+  "Word" is selected by default. </p>
+  
   <h5>Word and Lemma</h5>
   <p>If you want to search for a specific word or lemma and the respective 
   category is selected in the drop-down menu, you can type in the word or lemma 

app/templates/_base/_modals/manual.html.j2

@@ -3,21 +3,22 @@
     <h2>Manual</h2>
     <ul class="tabs" id="manual-modal-toc">
       <li class="tab"><a href="#manual-modal-introduction">Introduction</a></li>
-      <li class="tab"><a href="#manual-modal-registration-and-log-in">Registration and Log in</a></li>
+      <li class="tab"><a href="#manual-modal-getting-started">Getting Started</a></li>
       <li class="tab"><a href="#manual-modal-dashboard">Dashboard</a></li>
       <li class="tab"><a href="#manual-modal-services">Services</a></li>
-      <li class="tab"><a href="#manual-modal-a-closer-look-at-the-corpus-analysis">A closer look at the Corpus Analysis</a></li>
-      <li class="tab"><a href="#manual-modal-cqp-query-language">CQP Query Language</a></li>
+      <!-- <li class="tab"><a href="#manual-modal-a-closer-look-at-the-corpus-analysis">A closer look at the Corpus Analysis</a></li> -->
       <li class="tab"><a href="#manual-modal-query-builder">Query Builder</a></li>
+      <li class="tab"><a href="#manual-modal-cqp-query-language">CQP Query Language</a></li>
+
       <li class="tab"><a href="#manual-modal-tagsets">Tagsets</a></li>
     </ul>
     <div id="manual-modal-introduction">
       <br>
       {% include "_base/_modals/_manual/01_introduction.html.j2" %}
     </div>
-    <div id="manual-modal-registration-and-log-in">
+    <div id="manual-modal-getting-started">
       <br>
-      {% include "_base/_modals/_manual/02_registration_and_log_in.html.j2" %}
+      {% include "_base/_modals/_manual/02_getting_started.html.j2" %}
     </div>
     <div id="manual-modal-dashboard">
       <br>
@@ -27,10 +28,10 @@
       <br>
       {% include "_base/_modals/_manual/06_services.html.j2" %}
     </div>
-    <div id="manual-modal-a-closer-look-at-the-corpus-analysis">
+    <!-- <div id="manual-modal-a-closer-look-at-the-corpus-analysis">
       <br>
       {% include "_base/_modals/_manual/07_a_closer_look_at_the_corpus_analysis.html.j2" %}
-    </div>
+    </div> -->
     <div id="manual-modal-cqp-query-language">
       <br>
       {% include "_base/_modals/_manual/08_cqp_query_language.html.j2" %}

app/templates/_base/_modals/terms_of_use.html.j2

@@ -5,28 +5,111 @@
         <div class="col s12">
           <h1 id="title">Terms of use</h1>
         </div>
+
         <div class="col s12">
-          <div class="switch">
-            <label>
-              DE
-              <input type="checkbox" id="terms-of-use-modal-switch">
-              <span class="lever"></span>
-              EN
-            </label>
+          <p>With the usage of the nopaque platform you declare your acceptance of the General Terms of Use and that you have taken note of the legal framework and the data protection declaration.</p>
         </div>
-          <br>
+
+        <div class="col s12">
+          <div class="card">
+            <div class="card-content">
+              <span class="card-title">§ 1 Scope</span>
+              <p>The General Terms of Use for the nopaque platform apply to everyone who uses the system as an authorised user in the sense of <b>§ 2</b> (1) of the General Terms of Use. By using the system and with your consent you accept these terms of use.</p>
             </div>
-        <div class="terms-of-use-modal-content hide">
-          {% include "main/terms_of_use_en.html.j2" %}
           </div>
-        <div class="terms-of-use-modal-content">
-          {% include "main/terms_of_use_de.html.j2" %}
         </div>
+
+        <div class="col s12">
+          <div class="card">
+            <div class="card-content">
+              <span class="card-title">§ 2 Right of use</span>
+              <p>(1) The nopaque platform is available to users exclusively for the purposes of teaching and research. Any other use, especially for business, commercial is not permitted. The following groups shall be entitled to use the nopaque platform:</p>
+              <ul class="browser-default">
+                <li>students, teaching staff and employees at Bielefeld University</li>
+                <li>external researchers from outside the University Bielefeld</li>
+              </ul>
+              <p>&nbsp;</p>
+              <p>(2) The use of the system is free of charge.</p>
+              <p>&nbsp;</p>
+              <p>(3) The duration of the right of use ends with the deletion of the user account by the user (see <b>§ 7</b>)</p>
+            </div>
+          </div>
+        </div>
+
+        <div class="col s12">
+          <div class="card">
+            <div class="card-content">
+              <span class="card-title">§ 3 Purpose of the Services</span>
+              <p>nopaque custom-built web application which serves as a platform for preprocessing and analysing digital copies of various text based research data (books, letters, etc.) in different files and formats. nopaque converts image data – like photos or scans – into text data through OCR making it machine readable. This step enables to proceed with further computational analysis of the documents. By means of computational linguistic data processing (tokenization, lemmatization, part-of-speech tagging and named-entity recognition) nopaque extracts additional information from texts.</p>
+              <p>&nbsp;</p>
+              <p>(1) Change of service</p>
+              <p>The provider of the nopaque platform is entitled to change and supplement the scope of functions of nopaque without prior notice. This could result from a thematic and scientific reorientation of the project.</p>
+              <p>&nbsp;</p>
+              <p>(2) Support</p>
+              <p>On nopaque, a contact form is available. As far as possible the SFB 1288 INF staff will try to provide user support.</p>
+            </div>
+          </div>
+        </div>
+
+        <div class="col s12">
+          <div class="card">
+            <div class="card-content">
+              <span class="card-title">§ 4 Obligations of the User</span>
+              <p>(1) The system is suitable for normal security requirements. Data with a high need for protection (e.g. health data) may not be stored or processed in the nopaque platform.</p>
+              <p>&nbsp;</p>
+              <p>(2) Users of nopaque are responsible for their own entered contents. The uploading of illegal content, especially content that violates criminal, personal, data protection or copyright regulations (including § 60a) is not permitted.</p>
+              <p>&nbsp;</p>
+              <p>(3) Users undertake to indemnify Bielefeld University from all claims by third parties based on the data they use and to reimburse Bielefeld University for any costs incurred by the latter due to possible infringements of rights. This also includes the costs incurred by Bielefeld University in defending itself against such claims in and out of court.</p>
+              <p>&nbsp;</p>
+              <p>(4) Exclusion from use</p>
+              <p>Bielefeld University is entitled to immediately block access to the service if there are reasonable grounds to suspect that the stored data is unlawful (e.g upload harmful files via file upload) and/or violates the rights of third parties. Other infringements of the provisions of these Terms of Use, in particular the obligations under §6 also entitle Bielefeld University to block the user. Bielefeld University shall immediately notify the user of the block and the reason for the block. The block must be lifted as soon as the suspicion is invalidated.</p>
+              <p>&nbsp;</p>
+              <p>(5) Usage of Data</p>
+              <p>The data stored by the user on the storage space intended for him may be legally protected, the responsibility for the processing of the data from these points of view lies solely with the user. By using nopaque, the user grants Bielefeld the right to process the data with the corresponding tools. At all times during processing in nopaque, data remains in the user's private storage location and will not passed on to third parties.</p>
+              <p>&nbsp;</p>
+              <p>(6) Release of Bielefeld University from Third-Party Claims</p>
+              <p>The user is responsible for the data stored by him/her in nopaque. Furthermore he/she is responsible for entering and maintaining the data and information required to use nopaque.</p>
+              <p>&nbsp;</p>
+              <p>The user is obliged to indemnify Bielefeld University against all claims by third parties based on the data stored by him/her and to reimburse Bielefeld University for any costs incurred as a result of possible legal infringements. This also includes the costs incurred by Bielefeld University for extrajudicial and judicial defense against these claims.</p>
+            </div>
+          </div>
+        </div>
+
+        <div class="col s12">
+          <div class="card">
+            <div class="card-content">
+              <span class="card-title">§ 5 Liability of Bielefeld University</span>
+              <p>Claims for damages against Bielefeld University are excluded irrespective of the legal grounds. Bielefeld University shall not be liable for loss of data and information or other „indirect“ damages, e.g. loss of profit, loss of production, or other indirect damages. Bielefeld University shall not be liable for the loss of data to the extent that the damage is due to the fact that the user has failed to back up the data and thereby ensure that lost data can be restored with justifiable effort.</p>
+              <p>&nbsp;</p>
+              <p>nopaque is available in accordance with normal operational care based on the "Best Effort" practice. No liability is assumed for the consequences of failures or errors of the nopaque platform. Bielefeld University does not guarantee that the systems will run error-free and without interruption at all times. Bielefeld University accepts no responsibility for technical quality. Nor is it liable for the content, in particular for the accuracy, completeness, and timeliness of information to which it merely provides access for use.</p>
+            </div>
+          </div>
+        </div>
+
+        <div class="col s12">
+          <div class="card">
+            <div class="card-content">
+              <span class="card-title">§ 6 Data Protection</span>
+              <p>Information on the handling of personal data during the operation of the service can be found in the separate data protection policy.</p>
+            </div>
+          </div>
+        </div>
+
+        <div class="col s12">
+          <div class="card">
+            <div class="card-content">
+              <span class="card-title">§ 7 Duration and Termination</span>
+              <p>The user may terminate the use nopaque by deleting his/her account at any time without giving reasons. After deletion of the account, all users‘ data will be automatically deleted and access to the service blocked. This does not affect the user's right to delete data under data protection law.</p>
+              <p>&nbsp;</p>
+              <p>Bielefeld University may exclude the user from using the service without notice for an important reason. Important reasons include, in particular, repeated violations of the provisions of these Terms of Use or of applicable laws.</p>
+            </div>
+          </div>
+        </div>
+
       </div>
     </div>
   </div>
   <div class="modal-footer">
-    <span style="margin-right:20px;">I have taken note of the new GTC and agree to their validity in the context of my further use.</span>
-    <a href="#!" class="modal-close waves-effect waves-green btn">Yes</a>
+    <a href="#!" class="modal-close waves-effect waves-green btn-flat">Accept</a>
   </div>
 </div>

app/templates/_base/scripts.html.j2

@@ -131,15 +131,3 @@
     app.flash(message, message);
   }
 </script>
-
-<script>
-  let languageModalSwitch = document.querySelector('#terms-of-use-modal-switch');
-  let termsOfUseModalContent = document.querySelectorAll('.terms-of-use-modal-content');
-  if (languageModalSwitch) {
-    languageModalSwitch.addEventListener('change', function() {
-      termsOfUseModalContent.forEach(content => {
-        content.classList.toggle('hide');
-      });
-    });
-  }
-</script>

app/templates/corpora/public_corpus.html.j2

@@ -273,7 +273,7 @@ publicCorpusFollowerList.add(
 {% if cfr.has_permission('MANAGE_FILES') %}
 let followerBuildRequest = document.querySelector('#follower-build-request');
 followerBuildRequest.addEventListener('click', () => {
-  nopaque.requests.corpora.entity.build({{ corpus.hashid|tojson }})
+  requests.corpora.entity.build({{ corpus.hashid|tojson }})
     .then((response) => {
       window.location.reload();
     });
@@ -285,7 +285,7 @@ followerBuildRequest.addEventListener('click', () => {
 {% if current_user.is_following_corpus(corpus) %}
   let unfollowRequestElement = document.querySelector('.action-button[data-action="unfollow-request"]');
   unfollowRequestElement.addEventListener('click', () => {
-    nopaque.requests.corpora.entity.followers.entity.delete({{ corpus.hashid|tojson }}, {{ current_user.hashid|tojson }})
+    requests.corpora.entity.followers.entity.delete({{ corpus.hashid|tojson }}, {{ current_user.hashid|tojson }})
       .then((response) => {
         window.location.reload();
       });
@@ -335,7 +335,7 @@ M.Modal.init(
 
 inviteUserModalInviteButtonElement.addEventListener('click', (event) => {
   let usernames = inviteUserModalSearch.chipsData.map((chipData) => chipData.tag);
-  nopaque.requests.corpora.entity.followers.add({{ corpus.hashid|tojson }}, usernames)
+  requests.corpora.entity.followers.add({{ corpus.hashid|tojson }}, usernames)
     .then((response) => {
       window.location.reload();
     });
@@ -383,7 +383,7 @@ M.Modal.init(
 shareLinkModalCreateButtonElement.addEventListener('click', (event) => {
   let role = shareLinkModalCorpusFollowerRoleSelectElement.value;
   let expiration = shareLinkModalExpirationDateDatepickerElement.value
-  nopaque.requests.corpora.entity.generateShareLink({{ corpus.hashid|tojson }}, role, expiration)
+  requests.corpora.entity.generateShareLink({{ corpus.hashid|tojson }}, role, expiration)
     .then((response) => {
       response.json()
         .then((json) => {

app/templates/main/privacy_policy.html.j2

@@ -8,14 +8,14 @@
     </div>
 
     <div class="col s12">
-      <p>With these data protection notices, Bielefeld University fulfils its obligation to provide information in accordance with Articles 13 & 14 of the <b>EU General Data Protection Regulation (GDPR)</b> on the above-mentioned processing of personal data. Terms such as "personal data", "processing", "data controller", "third party", etc. are used as defined in <b>Article 4 GDPR</b>.</p>
+      <p>With these data protection notices, Bielefeld University fulfils its obligation to provide information in accordance with Articles 13 & 14 of the EU General Data Protection Regulation (GDPR) on the above-mentioned processing of personal data. Terms such as "personal data", "processing", "data controller", "third party", etc. are used as defined in Article 4 GDPR.</p>
     </div>
 
     <div class="col s12">
       <div class="card">
         <div class="card-content">
           <span class="card-title">§ 1 Contact Details</span>
-          <p>Bielefeld University, a legal entity under public law established by the state of North Rhine-Westphalia (NRW), is responsible for processing the data. It is represented by its rector, Prof. Dr. Angelika Epple.</p>
+          <p>Bielefeld University, a legal entity under public law established by the state of North Rhine-Westphalia (NRW), is responsible for processing the data. It is represented by its rector, Prof. Dr. Ing. Gerhard Sagerer.</p>
           <h6>§ 1.1. Contact details of the data controller</h6>
           <ul class="browser-default">
             <li>Data protection officer of the Faculty of History</li>
@@ -34,10 +34,10 @@
           <ul class="browser-default">
             <li>Dr. Johanna Vompras</li>
             <li>Email:
-              <a href="mailto:nopaque@uni-bielefeld.de">nopaque@uni-bielefeld.de</a>
+              <a href="mailto:johanna.vompras@uni-bielefeld.de">johanna.vompras@uni-bielefeld.de</a>
             </li>
             <li>Web.:
-              <a href="https://www.uni-bielefeld.de/sfb/sfb1288/projektbereiche/inf/">https://www.uni-bielefeld.de/sfb/sfb1288/projektbereiche/inf/</a>
+              <a href="https://www.uni-bielefeld.de/(en)/sfb1288/projekte/inf.html">https://www.uni-bielefeld.de/(en)/sfb1288/projekte/inf.html</a>
             </li>
           </ul>
           <h6>§ 1.2. Contact details of the data protection officer</h6>
@@ -56,55 +56,40 @@
       <div class="card">
         <div class="card-content">
           <span class="card-title">§ 2 General information on data processing and its purpose</span>
-          <p>We process the personal data of our users only to the extent necessary to provide a functioning website and its functionalities. Collecting this information enables us to better diagnose problems with the application, provide support more effectively as well as ensure the continuous functionality of the service.</p>
-          <p> The following (personal) data is collected and stored within the system:</p>
-          
+          <p>We process the personal data of our users only to the extent necessary to provide a functioning website and its functionalities.</p>
+          <p>The following personal data is collected and stored within the system:</p>
           <h6>Master Data</h6>
-          <p>Within the scope of user authentication, the following personal data is collected and processed: </p>
+          <p>Within the scope of user authentication the following personal data is collected and processed:</p>
           <ul class="browser-default">
             <li>User name</li>
             <li>E-Mail</li>
           </ul>
-          <p>The registration of users is required for the provision of access to services within NOPAQUE. The freely selectable username and the corresponding email address is used to persistently identify you in NOPAQUE. The provided email address might be used to contact you in case we noticed some malfunction, to announce maintenance, or to spread important information regarding Nopaque. If you reset your password, Nopaque will use your email address to send you reset instructions via email. Nopaque does not show your email address and the username to other Nopaque users per default – except, if user gave the permission to do so, according to <b>§ 7 paragraph 1</b> of the General Terms of Use for the use of NOPAQUE.</p>
-          
-          <h6>Protocol and administrative data</h6>
+          <p>Registration of the user is required for the provision of certain content and services within nopaque.</p>
+          <h6>Protocol Data</h6>
           <p>In general, when a website is visited, for technical reasons information is automatically sent from the browser to the server and stored there in access protocols. When using a web application, additional protocol data is also generated, which is necessary for tracking technical errors. This information includes:</p>
           <ul class="browser-default">
             <li>IP address</li>
+            <li>User account</li>
             <li>Complete HTTP request URL</li>
             <li>HTTP action (e.g. GET: call up a page, POST: send form data)</li>
             <li>Access status (HTTP status code)</li>
+            <li>data volume retrieved</li>
             <li>Date and time of the action</li>
+            <li>User-Agent string</li>
           </ul>
-          <br>
-          <p>Protocol data will be used by the development team in order to debug and improve the included tools. This data can only be viewed by the technical administration and by the employees responsible for the NOPAQUE platform. Protocol data is not directly associated with a user account. NOPAQUE deletes all this information when it gets more than six months old.</p>
-          <br>
-          <p>Further administrative data, which is essentially needed – to enable a proper user registration and user management functionalities:</p>
-          <ul class="browser-default">
-            <li>Attributes <b>member_since</b> and <b>last_seen</b>: for system cleaning purposes and detection of fake accounts</li>
-            <li>Attribute <b>confirmed</b>: This attribute indicates whether the account has been activated via e-mail. This type of activation ensures that the stored e-mail address actually exists.</li>
-            <li>Attribute <b>terms_of_use_accepted</b>: To verify that the terms of use have been accepted by the user. This attribute is set to false when the terms of use has changed. After the user has logged in again, the user is asked to accept the new terms of use.</li>
-          </ul>
-
+          <p>Locally logged data will be used by the development team in order to debug and improve tools. This data can only be viewed by the technical administration and by the employees responsible for the nopaque platform. Data is stored for seven days to ensure proper technical operation and to find the cause of errors and is deleted <u>afterwards</u>.</p>
+          <p>Logged data may be used to understand how researchers are using the nopaque platform. To be able to use the data for research purposes, we reserve the right to store it in an anonymous and aggregated form for a longer period of time (up to two years after completion of the SFB 1288 INF project).</p>
           <h6>Cookies</h6>
-          <p>Cookies: Browsers store so-called cookies. Cookies are files that can be stored by the provider of a website in the directory of the browser program on the user's computer. These files contain text information and can be read again by the provider when the page is called up again. The provider can use these cookies, for example, to always deliver pages in the theme selected by the user.</p>
+          <p>Browsers store so-called cookies. Cookies are files that can be stored by the provider of a website in the directory of the browser program on the user's computer. These files contain text information and can be read again by the provider when the page is called up again. The provider can use these cookies, for example, to always deliver pages in the theme selected by the user.</p>
           <p>The storage of cookies can be switched off in the browser settings or provided with an expiry time. By deactivating cookies, however, some functions that are controlled by cookies can then only be used to a limited extent or not at all.</p>
-          <br>
-          <p>NOPAQUE uses <b>functionality cookies</b> which deliver certain functions and allow to remember important information and user’s preferences:</p>
+          <p>NOPAQUE uses cookies for the following purposes:</p>
           <ul class="browser-default">
-            <li><b>session</b>: Recognition of a user during a session in order to assign personal content and other user-defined settings. The session cookie is deleted after closing the browser session.</li>
-            <li><b>remember_token</b>: Login script with ‘remember me’ feature allowing the user to preserve their logged in status. When the user checks the Remember Me option, then the logged in status is serialized in the session and stored in cookies in an encrypted way.</li>
+            <li>Recognition of a user during a session in order to assign personal content and other user-defined settings.</li>
+            <li>Login Script with ‘Remember Me’ feature allows the user to preserve their logged in status. When the user checks the Remember Me option, then the logged in status is serialized in the session and stored in cookies in an encrypted way.</li>
           </ul>
-          <p>Cookies collected by NOPAQUE do not collect personal information of the users.</p>
-          
           <h6>Content Data</h6>
-          <p>The content data includes all data that is entered or created by users themselves in the system. This data is listed here because it is assigned to individual authors and may contain personal data. This may include: <b>uploaded files, images, text documents, other media files</b> and <b>(interim) results</b> after data processing and computations. Please note that files and scans submitted to NOPAQUE are safely stored on the NOPAQUE server in order to allow persistent access during a work session and between work sessions.</p>
-          <br>
-          <p>According to <b>§ 4 paragraph 1 - 3</b> of the General Terms of Use for the use of NOPAQUE at Bielefeld University, the users themselves are responsible for the content they upload and must comply with the legal provisions of data protection and copyright law. This includes in particular the deletion of personal data that may no longer be processed.</p>
-          
-          <h6>User-added Information (optional)</h6>
-          <p>NOPAQUE also stores optionally user-added personal information, like user’s profile information (full name, affiliation) and user’s added profile photo (avatar).</p>
-        
+          <p>The content data includes all data that is entered or created by users themselves in the system. This data is listed here because it is assigned to individual authors and may contain personal data. This may include: uploaded files, images, texts or other media files. Please note that files and scans submitted to NOPAQUE are stored in order to allow persistent access during a work session and between work sessions.</p>
+          <p>According to § 4 paragraph 2 of the General Terms of Use for the use of NOPAQUE at Bielefeld University, the users themselves are responsible for the content they post and must comply with the legal provisions of data protection. This includes in particular the deletion of personal data that may no longer be processed.</p>
         </div>
       </div>
     </div>
@@ -122,14 +107,9 @@
     <div class="col s12">
       <div class="card">
         <div class="card-content">
-          <span class="card-title">§ 4 Data transmissions and sharing of your data</span>
-          <p>Your personal data, which are processed by Bielefeld University for the purposes mentioned under <b>2 A - D</b> will not be transferred to third parties.</p>
-          <br>
+          <span class="card-title">§ 4 Data transmissions</span>
+          <p>Your personal data, which are processed by Bielefeld University for the purposes mentioned under 2. will not be transferred to third parties.</p>
           <p>In individual cases, data may also be legally transmitted to third parties, for example, to law enforcement authorities for the investigation of criminal offences within the framework of the <b>Code of Criminal Procedure (StPO)</b>. If technical service providers are given access to personal data, this is done on the basis of a contract in accordance with <b>Article 28 GDPR</b>.</p>
-          <br>
-          <p>NOPAQUE centrally bundles sophisticated data processing functionalities related to Digital Humanities (for example: pattern recognition or text mining) on its platform which are offered by third parties on external platforms. No personal data is passed on to third parties - only content data which is sent anonymously to the APIs of the third-party tools. The results of the calculations are then sent back to NOPAQUE and saved as results in user’s account.</p>
-          <br>
-          <p>For personal data mentioned under <b>2 E</b> the following applies: we do not share your personal data with third parties unless you have given your consent. This consent is given if the user actively makes his profile public in NOPAQUE. As consequence, user-added information (as listed under point 2E of this declaration) and, if applicable, a listing of public corpora with metadata is then made visible to other NOPAQUE users.</p>
         </div>
       </div>
     </div>
@@ -137,8 +117,8 @@
     <div class="col s12">
       <div class="card">
         <div class="card-content">
-          <span class="card-title">§ 5 Duration of processing of your data and data retention</span>
-          <p>Data processed for user authentication, all personal data and contents uploaded by the user (listed in <b>2</b>) are deleted immediately after account deletion.</p>
+          <span class="card-title">§ 5 Duration of processing / data deletion</span>
+          <p>Data processed for user authentication are deleted immediately after account deletion.</p>
         </div>
       </div>
     </div>
@@ -146,7 +126,7 @@
     <div class="col s12">
       <div class="card">
         <div class="card-content">
-          <span class="card-title">§ 6 Your data protection rights and choices as NOPAQUE user</span>
+          <span class="card-title">§ 6 Your rights as a data subject</span>
           <p>As a data subject, you have certain rights under <b>GDPR</b> that you may assert at any time:</p>
           <ul class="browser-default">
             <li>the right to access information about whether or not personal data concerning you is processed, and if so, what categories of data are being processed (<b>Article 15 GDPR</b>),</li>

app/templates/main/terms_of_use.html.j2

@@ -6,36 +6,106 @@
     <div class="col s12">
       <h1 id="title">{{ title }}</h1>
     </div>
+
     <div class="col s12">
-      <div class="switch">
-        <label>
-          DE
-          <input type="checkbox" id="terms-of-use-page-switch">
-          <span class="lever"></span>
-          EN
-        </label>
+      <p>With the usage of the nopaque platform you declare your acceptance of the General Terms of Use and that you have taken note of the legal framework and the data protection declaration.</p>
     </div>
-      <br>
+
+    <div class="col s12">
+      <div class="card">
+        <div class="card-content">
+          <span class="card-title">§ 1 Scope</span>
+          <p>The General Terms of Use for the nopaque platform apply to everyone who uses the system as an authorised user in the sense of <b>§ 2</b> (1) of the General Terms of Use. By using the system and with your consent you accept these terms of use.</p>
+        </div>
+      </div>
+    </div>
+
+    <div class="col s12">
+      <div class="card">
+        <div class="card-content">
+          <span class="card-title">§ 2 Right of use</span>
+          <p>(1) The nopaque platform is available to users exclusively for the purposes of teaching and research. Any other use, especially for business, commercial is not permitted. The following groups shall be entitled to use the nopaque platform:</p>
+          <ul class="browser-default">
+            <li>students, teaching staff and employees at Bielefeld University</li>
+            <li>external researchers from outside the University Bielefeld</li>
+          </ul>
+          <p>&nbsp;</p>
+          <p>(2) The use of the system is free of charge.</p>
+          <p>&nbsp;</p>
+          <p>(3) The duration of the right of use ends with the deletion of the user account by the user (see <b>§ 7</b>)</p>
+        </div>
+      </div>
+    </div>
+
+    <div class="col s12">
+      <div class="card">
+        <div class="card-content">
+          <span class="card-title">§ 3 Purpose of the Services</span>
+          <p>nopaque custom-built web application which serves as a platform for preprocessing and analysing digital copies of various text based research data (books, letters, etc.) in different files and formats. nopaque converts image data – like photos or scans – into text data through OCR making it machine readable. This step enables to proceed with further computational analysis of the documents. By means of computational linguistic data processing (tokenization, lemmatization, part-of-speech tagging and named-entity recognition) nopaque extracts additional information from texts.</p>
+          <p>&nbsp;</p>
+          <p>(1) Change of service</p>
+          <p>The provider of the nopaque platform is entitled to change and supplement the scope of functions of nopaque without prior notice. This could result from a thematic and scientific reorientation of the project.</p>
+          <p>&nbsp;</p>
+          <p>(2) Support</p>
+          <p>On nopaque, a contact form is available. As far as possible the SFB 1288 INF staff will try to provide user support.</p>
+        </div>
+      </div>
+    </div>
+
+    <div class="col s12">
+      <div class="card">
+        <div class="card-content">
+          <span class="card-title">§ 4 Obligations of the User</span>
+          <p>(1) The system is suitable for normal security requirements. Data with a high need for protection (e.g. health data) may not be stored or processed in the nopaque platform.</p>
+          <p>&nbsp;</p>
+          <p>(2) Users of nopaque are responsible for their own entered contents. The uploading of illegal content, especially content that violates criminal, personal, data protection or copyright regulations (including § 60a) is not permitted.</p>
+          <p>&nbsp;</p>
+          <p>(3) Users undertake to indemnify Bielefeld University from all claims by third parties based on the data they use and to reimburse Bielefeld University for any costs incurred by the latter due to possible infringements of rights. This also includes the costs incurred by Bielefeld University in defending itself against such claims in and out of court.</p>
+          <p>&nbsp;</p>
+          <p>(4) Exclusion from use</p>
+          <p>Bielefeld University is entitled to immediately block access to the service if there are reasonable grounds to suspect that the stored data is unlawful (e.g upload harmful files via file upload) and/or violates the rights of third parties. Other infringements of the provisions of these Terms of Use, in particular the obligations under §6 also entitle Bielefeld University to block the user. Bielefeld University shall immediately notify the user of the block and the reason for the block. The block must be lifted as soon as the suspicion is invalidated.</p>
+          <p>&nbsp;</p>
+          <p>(5) Usage of Data</p>
+          <p>The data stored by the user on the storage space intended for him may be legally protected, the responsibility for the processing of the data from these points of view lies solely with the user. By using nopaque, the user grants Bielefeld the right to process the data with the corresponding tools. At all times during processing in nopaque, data remains in the user's private storage location and will not passed on to third parties.</p>
+          <p>&nbsp;</p>
+          <p>(6) Release of Bielefeld University from Third-Party Claims</p>
+          <p>The user is responsible for the data stored by him/her in nopaque. Furthermore he/she is responsible for entering and maintaining the data and information required to use nopaque.</p>
+          <p>&nbsp;</p>
+          <p>The user is obliged to indemnify Bielefeld University against all claims by third parties based on the data stored by him/her and to reimburse Bielefeld University for any costs incurred as a result of possible legal infringements. This also includes the costs incurred by Bielefeld University for extrajudicial and judicial defense against these claims.</p>
+        </div>
+      </div>
+    </div>
+
+    <div class="col s12">
+      <div class="card">
+        <div class="card-content">
+          <span class="card-title">§ 5 Liability of Bielefeld University</span>
+          <p>Claims for damages against Bielefeld University are excluded irrespective of the legal grounds. Bielefeld University shall not be liable for loss of data and information or other „indirect“ damages, e.g. loss of profit, loss of production, or other indirect damages. Bielefeld University shall not be liable for the loss of data to the extent that the damage is due to the fact that the user has failed to back up the data and thereby ensure that lost data can be restored with justifiable effort.</p>
+          <p>&nbsp;</p>
+          <p>nopaque is available in accordance with normal operational care based on the "Best Effort" practice. No liability is assumed for the consequences of failures or errors of the nopaque platform. Bielefeld University does not guarantee that the systems will run error-free and without interruption at all times. Bielefeld University accepts no responsibility for technical quality. Nor is it liable for the content, in particular for the accuracy, completeness, and timeliness of information to which it merely provides access for use.</p>
+        </div>
+      </div>
+    </div>
+
+    <div class="col s12">
+      <div class="card">
+        <div class="card-content">
+          <span class="card-title">§ 6 Data Protection</span>
+          <p>Information on the handling of personal data during the operation of the service can be found in the separate data protection policy.</p>
+        </div>
+      </div>
+    </div>
+
+    <div class="col s12">
+      <div class="card">
+        <div class="card-content">
+          <span class="card-title">§ 7 Duration and Termination</span>
+          <p>The user may terminate the use nopaque by deleting his/her account at any time without giving reasons. After deletion of the account, all users‘ data will be automatically deleted and access to the service blocked. This does not affect the user's right to delete data under data protection law.</p>
+          <p>&nbsp;</p>
+          <p>Bielefeld University may exclude the user from using the service without notice for an important reason. Important reasons include, in particular, repeated violations of the provisions of these Terms of Use or of applicable laws.</p>
         </div>
-    <div class="terms-of-use-page-content hide">
-      {% include "main/terms_of_use_en.html.j2" %}
       </div>
-    <div class="terms-of-use-page-content">
-      {% include "main/terms_of_use_de.html.j2" %}
     </div>
   </div>
 </div>
 {% endblock page_content %}
-
-{% block scripts %}
-{{ super() }}
-<script>
-  let languagePageSwitch = document.querySelector('#terms-of-use-page-switch');
-  let termsOfUsePageContent = document.querySelectorAll('.terms-of-use-page-content');
-  languagePageSwitch.addEventListener('change', function() {
-    termsOfUsePageContent.forEach(content => {
-      content.classList.toggle('hide');
-    });
-  });
-</script>
-{% endblock scripts %}

app/templates/main/terms_of_use_de.html.j2

@@ -1,141 +0,0 @@
-<div class="col s12">
-  <p>Mit Nutzung der Plattform nopaque stimmen Sie den Allgemeinen Geschäftsbedingungen sowie der Zurkenntnisnahme des rechtlichen Rahmens und der Datenschutzerklärung.</p>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 1 Inhalt und Umfang des Serviceangebots</span>
-      <p>(1)	Diese Allgemeinen Geschäftsbedingungen gelten für die Nutzung der Angebote des browserbasierten Datenverarbeitungs- und Textanalysetools „nopaque“ (nachfolgend „Serviceangebot“), der Universität Bielefeld (nachfolgend Universität), das von berechtigten Nutzern kostenlos über die Internetseite www.nopaque.uni-bielefeld.de verwendet werden kann.</p>
-      <p>(2)	berechtigt zur Nutzung des Serviceangebotes sind lediglich</p>
-      <ol type="a">
-        <li>Studierende, Lehrende und Beschäftigte der Universität Bielefeld</li>
-        <li>Externe Wissenschaftler*innen  im Rahmen nichtkommerzieller Forschung</li>
-      </ol>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 2 Serviceangebot</span>
-      <p>(1)	Im Rahmen des Serviceangebots können von den Nutzern hochzuladende Daten automatisiert verarbeitet und analysiert werden.  Dies ist in Form von folgenden, einzeln ansteuerbaren, Services umgesetzt:</p>
-      <ol type="a">
-        <li><b>File Setup</b>: Digitale Kopien von textbasierten Forschungsdaten (Bücher, Briefe usw.) bestehen oft aus verschiedenen Dateien und Formaten. Nopaque konvertiert und führt diese Dateien zusammen, um die Weiterverarbeitung und die Anwendung anderer Dienste zu erleichtern.</li>
-        <li><b>Optical Character Recognition</b> (OCR): nopaque wandelt Ihre Bilddaten - wie Fotos oder Scans - durch OCR in Textdaten um und macht sie maschinenlesbar. Dieser Schritt ermöglicht es Ihnen, mit der weiteren rechnerischen Analyse Ihrer Dokumente fortzufahren.</li>
-        <li><b>Handwritten Text Recognition</b> (HTR): nopaque wandelt Ihre Bilddaten von handschriftlichen Texten - wie Fotos oder Scans - mittels HTR in Textdaten um und macht sie maschinenlesbar. Dieser Schritt ermöglicht es Ihnen, mit der weiteren rechnerischen Analyse Ihrer Dokumente fortzufahren.</li>
-        <li><b>Natural Language Processing</b> (NLP): Mittels computergestützter linguistischer Datenverarbeitung (Tokenisierung, Lemmatisierung, Part-of-Speech-Tagging und Named-Entity-Erkennung) extrahiert nopaque zusätzliche Informationen aus Ihrem Text.</li>
-        <li><b>Corpus analysis</b>: Mit nopaque können Sie so viele Textkorpora erstellen und hochladen, wie Sie möchten. Es nutzt die CQP Query Language, die komplexe Suchanfragen mit Hilfe von Metadaten und NLP-Tags ermöglicht.</li>
-      </ol>
-      <p>(2)	Der Nutzer ist auch berechtigt, im Rahmen des Serviceangebots erstellte Textaufbereitungen (Corpora) innerhalb der Nutzerplattform des Serviceangebots durch die „Teilen“-Funktionen mit anderen registrierten Nutzern zu teilen. Ein Zugang zu fremden Corpora kann jeweils mit Leserechten (Viewer), mit Lese-und Bearbeitungsrechten (Contributor) oder Co-Administratorrechten (Administrator) eingeräumt werden.</p>
-      <p>(3)	Die Nutzer können im Rahmen Ihres Nutzerkontos eigene Sprachmodelle hochladen und diese zur Analyse hochgeladener Dateien verwenden. Nach Freischaltung durch einen Administrator können Nutzer ihre hochgeladenen Sprachmodelle auch öffentlich im Rahmen der Plattform zur Verfügung stellen.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 3 Zugang zum Serviceangebot</span>
-      <p>(1) Die Nutzer registrieren sich über die Eingabe der abgefragten Daten in der Anmeldemaske. Danach muss der Nutzer einen von ihm gewählten Benutzernamen und ein Passwort bestimmen und eingeben.</p>
-      <p>(2) Der Nutzer ist für die Geheimhaltung des Benutzernamens sowie des Passwortes selbst verantwortlich.</p>
-      <p>(3) Nach Freischaltung durch einen Administrator können Nutzer durch eine API-Schnittstelle auch persönliche Zugangstoken erstellen und auf alle Daten zugreifen kann, auf die der Nutzer selbst zugreifen kann.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 4 Allgemeine Pflichten der Nutzer</span>
-      <p>(1)	Mit der Registrierung erklären die Nutzer Ihre Zustimmung zu den Nutzungsbedingungen. Das rechtswidrige Hochladen, Verarbeiten und Teilen von Inhalten insbesondere entgegen strafrechtlicher, persönlichkeitsrechtlicher, datenschutzrechtlicher oder urheberrechtlicher Regelungen ist nicht gestattet. Durch das Hochladen, bearbeiten und/oder Teilen entsprechender Texte, Corpora und/oder Analyseergebnisse erklärt der jeweilige Nutzer, Inhaber aller dazu jeweils erforderlichen Rechte zu sein.</p>
-      <p>(2)	Die Nutzer verpflichten sich, auch im Rahmen der Gestaltung des persönlichen Nutzerprofils und der Nutzung von Foren der Plattform, Medien und Texte nur auf gesetzlich erlaubte Art und Weise zu verwenden und illegale Äußerungen zu unterlassen.</p>
-      <p>(3)	Das Serviceangebot ist lediglich zur Verarbeitung von Daten ohne erhöhte Schutzbedürfnisse geeignet. Daten, welche besonderen datenschutzrechtlichen Anforderungen unterliegen (bspw. Gesundheitsdaten, siehe Art. 9 DSGVO) dürfen nicht gespeichert oder verarbeitet werden.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 5 Haftung der Nutzer</span>
-      <p>(1)	Sofern aufgrund der Nutzung eines nicht berechtigten Nutzers (siehe hierzu § 1 Abs. 2) oder aufgrund einer unerlaubten Nutzung (siehe hierzu § 4 Abs. 1, 2) von Texten, Analyseergebnissen oder sonstigen Medien (bspw. einem hochgeladenen Profilbild) im Rahmen des Serviceangebots Ansprüche Dritter gegen die Universität Bielefeld geltend gemacht werden, stellt der für die Rechtsverletzung verantwortliche Nutzer die Universität von diesen Ansprüchen frei.</p>
-      <p>(2)	Die Nutzer haften bezgl. der Geheimhaltung und Weitergabe von Zugangsdaten für jegliche Schäden, die Ihnen entstehen.  Sofern aufgrund einer unerlaubten Verwendung von Zugangsdaten/Token Ansprüche Dritter gegen die Universität Bielefeld geltend gemacht werden, stellt der für die Rechtsverletzung verantwortliche Nutzer die Universität von diesen Ansprüchen frei.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 6 Nutzungsrechte des Nutzers bzgl. erstellter Corpora und Analyseberichte</span>
-      <p>(1)	Der Nutzer ist in den Grenzen des § 4 berechtigt, Texte mit der Webanwendung aufzubereiten, im Rahmen der Webanwendung einzusehen und herunterzuladen. Regelungen zum Teilen der so erstellten Corpora ergeben sich nach § 7 dieser AGB.</p>
-      <p>(2)	Der Nutzer ist auch berechtigt, den jeweils auf Grundlage der aufbereiteten Texte zur Verfügung gestellten Analysebericht zu Zwecken von Forschung und Lehre in den Grenzen des § 4 im Rahmen der Online-Anwendung zu lesen, herunterzuladen, zu vervielfältigen und zu veröffentlichen. Die Berechtigung steht nur denjenigen Nutzern zu, welche die entsprechenden Analyseberichte generieren. Die Berechtigung steht unter der auflösenden Bedingung, dass im Rahmen entsprechender Vervielfältigungen/Veröffentlichungen von Analyseberichten oder deren Ausschnitten als Quellenangabe vermerkt wird: nopaque [Software]. (2020). SFB 1288 – Teilprojekt INF, Universität Bielefeld. https://nopaque.uni-bielefeld.de/</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 7 Teilen von zuvor erstellten Corpora</span>
-      <p>(1)	Das Teilen von Corpora wird auf folgende Art und Weise ermöglicht:</p>
-      <ol type="a"> 
-        <li>Es kann ein Link generiert werden, welcher anderen angemeldeten Nutzern Zugang zu den auf den Servern des Serviceangebots gespeicherten Corpora eines Nutzers ermöglicht.</li>
-        <li>Corpora können in eine durch alle Nutzer einsehbare Liste eingefügt werden, in deren Rahmen sich andere Nutzer über den vorhandene Bestand informieren und durch Kontaktierung des jeweiligen Erstellers einen Zugang erbitten können. Der Ersteller entscheidet dann in eigener Verantwortung über die Zulässigkeit des erbetenen Zugangs und ermöglicht bis zum Widerruf den Zugriff auf die Corpora durch die jeweiligen anderen Nutzer durch das Teilen eines Links im obigen Sinne.</li>
-      </ol>
-      <p>(2)	In Bezug auf das Teilen von Corpora, welche urheberrechtlich geschützte Medien enthalten, ist insb. § 60d UrhG einzuhalten. Es sind durch den hochladenden Nutzer insb. die dort genannten Löschfristen einzuhalten. Es wird ausdrücklich darauf hingewiesen, dass das regelwidrige Verbreiten von Corpora oder Ausgangstexten zu Pflichtverletzungen nach § 4 führen kann, deren finanzieller Schaden von den jeweiligen Nutzern zu tragen ist.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 8 Verfügbarkeit und Support</span>
-      <p>(1)	Die Universität ist berechtigt, soweit es im Interesse des Nutzers erforderlich ist, Wartungsarbeiten  auch während der Betriebszeit vorzunehmen. Hierbei kann es zu Störungen des Datenabrufs kommen, die die Universität möglichst geringhalten wird.</p>
-      <p>(2)	Die Universität ist berechtigt, den Funktionsumfang des Serviceangebots zu ändern und/oder zu modifizieren ohne die Nutzer zuvor zu benachrichtigen. Die Universität kann, ohne hierzu verpflichtet zu sein, die Software jederzeit aktualisieren oder weiterentwickeln und insbesondere aufgrund geänderter Rechtslage, technischer Entwicklungen, aufgrund einer wissenschaftlichen oder thematischen Umstrukturierung des Projekts oder zur Verbesserung der IT-Sicherheit anpassen.</p>
-      <p>(3)  Nutzern wird im Rahmen des Webauftritts ein Supportformular zur Verfügung gestellt.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 9 Mängelrechte, Haftung der Universität</span>
-      <p>(1)  Die Universität übernimmt keine Gewähr dafür, dass die durch das Serviceangebot zur Verfügung gestellten Informationen inhaltlich richtig, aktuell oder brauchbar sind oder zu einem gewünschten Erfolg führen. Insoweit ist jegliche Haftung der Universität ausgeschlossen.</p>
-      <p>(2)  Das Serviceangebot wird auf Basis der Praxis „Best Effort“ nach betriebsüblicher Sorgfalt zur Verfügung gestellt. Die Universität Bielefeld übernimmt keine Garantie dafür, dass die Systeme fehlerfrei und ohne Unterbrechung laufen. Eventuelle Datenverluste infolge technischer Störungen können nicht ausgeschlossen werden. Für den Verlust von Daten haftet die Universität Bielefeld insoweit nicht, als der Schaden darauf beruht, dass es die Nutzer*innen unterlassen haben, Datensicherungen durchzuführen und dadurch sicherzustellen, dass verloren gegangene Daten mit vertretbarem Aufwand wiederhergestellt werden können.</p>
-      <p>(3)  Im Übrigen haftet die Universität nur bei Vorsatz oder grober Fahrlässigkeit ihrer Mitarbeiter*innen, es sei denn, dass eine schuldhafte Verletzung wesentlicher Pflichten im Sinne dieser Nutzungsbedingungen vorliegt.  In diesem Fall ist die Haftung auf typische, bei Begründung des Nutzungsverhältnisses vorhersehbare Schäden begrenzt; die Universität haftet nicht für andere Schäden, z.B. für entgangenen Gewinn, für Produktionsausfall, für sonstige mittelbare Schäden oder für Verlust von Daten und Informationen. Die Haftung für Schäden aus der Verletzung des Lebens, des Körpers oder der Gesundheit bleibt unberührt.</p>
-      <p>(4)  Mögliche Amtshaftungsansprüche gegen die Hochschule bleiben von den vorstehenden Regelungen unberührt.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 10 Missbräuchliche Nutzung</span>
-      <p>Die Universität behält sich vor, bei Verdacht einer missbräuchlichen Nutzung oder wesentlicher Verletzungen dieser Nutzungsbedingungen diesen Vorgängen nachzugehen, entsprechende Vorkehrungen zu treffen und bei einem begründeten Verdacht gegebenenfalls den Zugang des Nutzers zum Serviceangebot – mindestens bis zu einer Verdachtsausräumung seitens des Nutzers – zu sperren und/oder gegebenenfalls bei besonders schwerwiegenden Verstößen auch das Nutzerkonto zu löschen. Soweit der Nutzer den Verdacht ausräumt, wird die Sperrung aufgehoben. Hinweise auf eine missbräuchliche Nutzung des Serviceangebotes hat jeder Nutzer der Universität unverzüglich mitzuteilen.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 11 Anwendbares Recht</span>
-      <p>Es gilt ausschließlich das Recht der Bundesrepublik Deutschland. Unberührt davon bleiben die zwingenden Bestimmungen des Staates, in dem Sie Ihren gewöhnlichen Aufenthalt haben.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 12 Gerichtsstand</span>
-      <p>Sofern Sie keinen Wohnsitz in der Bundesrepublik Deutschland haben oder nach Anmeldung Ihren Wohnsitz ins Ausland verlegen oder Ihr Wohnsitz zum Zeitpunkt der Klageerhebung nicht bekannt ist, ist Gerichtsstand für alle Streitigkeiten aus und im Zusammenhang mit dem Nutzungsverhältnis das Amts- oder Landgericht Bielefeld.</p>
-    </div>
-  </div>
-</div>

app/templates/main/terms_of_use_en.html.j2

@@ -1,150 +0,0 @@
-<div class="col s12">
-  <div class="card red darken-2">
-    <div class="card-content white-text">
-      <span class="card-title">Notice</span>
-      <p>This page is translated for the understanding of English-speaking users. However, only the version of the German Terms of Use in accordance with German law applies. </p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <p>With the usage of the nopaque platform you declare your acceptance of the General Terms of Use and that you have taken note of the legal framework and the data protection declaration.</p>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 1 Content and scope of the Services offered</span>
-      <p>(1)	These General Terms and Conditions apply to the use of the Services offered in the browser-based data processing and text analysis tool "nopaque" (hereinafter "Services") by Bielefeld University (hereinafter "University"), which can be used free of charge by authorized Users via the website www.nopaque.uni-bielefeld.de.</p>
-      <p>(2)	The authorized use of these services is exclusively granted to:</p>
-      <ol type="a">
-        <li>Students, teaching staff, and employees of Bielefeld University</li>
-        <li>External researchers for use in non-commercial research</li>
-      </ol>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 2 Services</span>
-      <p>(1)	As part of the Services offered, user-uploaded data can be processed and analyzed automatically. This is implemented in the form of the following Services, each of which can be executed individually:</p>
-      <ol type="a">
-        <li><b>File Setup</b>: Digital copies of text-based research data (books, letters, etc.) often consist of different files and formats. nopaque converts and merges these files to facilitate further processing and the use of other services.</li>
-        <li><b>Optical Character Recognition</b> (OCR): nopaque converts image data - such as photos or scans - into text data using OCR and makes it machine-readable. This step enables the further computational analysis of documents.</li>
-        <li><b>Handwritten Text Recognition</b> (HTR): nopaque converts image data from handwritten text - such as photos or scans - into text data using HTR and makes it machine-readable. This step enables further computational analysis of documents.</li>
-        <li><b>Natural Language Processing</b> (NLP): Using computer-aided linguistic data processing (tokenization, lemmatization, part-of-speech tagging and named entity recognition), nopaque extracts additional information from text.</li>
-        <li><b>Corpus analysis</b>: With nopaque, one can create and upload as many text corpora as desired. It uses the CQP Query Language, which enables complex search queries using metadata and NLP tags.</li>
-      </ol>
-      <p>(2)	The User is also entitled to share text edits (corpora) created as part of the Services offered with other registered Users within the Service’s user platform using the "Share" functions. Access to third-party corpora can be granted with reading rights (viewer), reading and editing rights (contributor) or co-administrator rights (administrator).</p>
-      <p>(3)	Users can upload their own language models as part of their user account and use them to analyze uploaded files. After activation by an administrator, Users can also make their uploaded language models publicly available on the platform.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 3 Access to the Services</span>
-      <p>(1)  Users register by entering the requested data in the login screen. The User must then select and enter a username and password of their choice.</p>
-      <p>(2) Users are responsible for keeping their username and password confidential.</p>
-      <p>(3) After activation by an administrator, Users can create personal access tokens via an application programming interface (API) and access all user-accessible data. </p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 4 General User Obligations</span>
-      <p>(1)	By registering, Users declare their consent to the terms of use. The unlawful uploading, processing, and sharing of content, in particular contrary to criminal law, personal rights regulations, data protection law or copyright regulations, is not permitted. By uploading, editing and/or sharing corresponding texts, corpora and/or analysis results, the respective User declares to be the owner of all rights required in each case.</p>
-      <p>(2)	Users are required to use media and texts only in a legally permitted manner and refrain from making illegal statements. This includes the design of their personal user profile and when using the forums on the nopaque platform.</p>
-      <p>(3)	The Services offered are only suitable for the processing of data without heightened security requirements. Data that is subject to special data protection requirements (e.g. health data, see Art. 9 GDPR) may not be stored or processed.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 5 User liability</span>
-      <p>(1)	If claims are asserted against Bielefeld University by third parties due to the use of an unauthorized User (see § 1 para. 2) or due to unauthorized use (see § 4 para. 1, 2) of texts, analysis results or other media (e.g. an uploaded profile picture) within the scope of the services offered, the User responsible for the infringement shall indemnify Bielefeld University against these claims.</p>
-      <p>(2)	Users are liable for any damage they incur regarding the confidentiality and disclosure of access data. If claims are asserted against Bielefeld University by third parties due to unauthorized use of access data/tokens, the User responsible for the infringement shall indemnify Bielefeld University against these claims.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 6 User rights of use regarding generated corpora and analysis reports</span>
-      <p>(1)	Within the limits of § 4, the User is entitled to prepare texts with the web application, to view them within the web application and to download them. Regulations on sharing the corpora created in this way are set out in § 7 of these GTC</p>
-      <p>(2)	The User is also entitled to display, download, reproduce, and publish analysis reports generated based on the prepared texts for the purposes of teaching and research within the limits of § 4. These rights are only granted to the Users that generate the corresponding analysis reports. The authorization is subject to the resolutive condition that in the context of corresponding reproductions/publications of analysis reports or their excerpts, the following is noted as the source: nopaque [Software]. (2020). SFB 1288 - Subproject INF, Bielefeld University. https://nopaque.uni-bielefeld.de/.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 7 Sharing previously created corpora</span>
-      <p>(1)	Sharing of corpora is possible in the following ways:</p>
-      <ol type="a"> 
-        <li>A link can be generated allowing other registered Users to access another User’s corpora stored on the servers of the Service.</li>
-        <li>Corpora can be added to a list visible to all other Users. In the context of this list, other Users can find information about the available content and request access by contacting the relevant creator. The creator can then decide, on their own responsibility, whether the requested access is permissible and can allow the requesting User to access the corpora – until this access is revoked – by sharing a link as described above.</li>
-      </ol>
-      <p>(2)	With regard to the sharing of corpora containing copyright-protected media, § 60d UrhG must be observed most particularly. The User is required to comply with the deletion periods stated therein. It is expressly pointed out that the improper distribution of corpora or source texts can lead to breaches of duty in accordance with § 4, the financial loss of which is to be borne by the respective users.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 8 Availability and support</span>
-      <p>(1)	The University has the right to conduct maintenance during operating times as far as it is in user interest. Disruption of data access may occur during maintenance, which the University will minimize as much as possible. </p>
-      <p>(2)	The University has the right to change and/or modify the range of functions of the Services without prior notification of its Users. The University can, without being required to do so, update or develop the software at any time, especially due to changed laws and regulations, technical developments, scientific or thematic restructuring of the project or for IT security improvements.</p>
-      <p>(3)  Users are provided with a support contact form on the website.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 9 Defect rights and liability of the University</span>
-      <p>(1)  The University does not guarantee that the information provided by the service is correct, up-to-date or usable or that it will lead to the desired results. In this respect, the University accepts no liability whatsoever.</p>
-      <p>(2)  The Services are provided based on “best effort” practices according to customary operational diligence. The University does not guarantee uninterrupted, error-free system operation. Possible data loss due to technical disruptions cannot be ruled out. The University is not liable for data loss based on user neglect to create data backups and to ensure that lost data can be restored with reasonable expense and effort.</p>
-      <p>(3)  Otherwise, the University shall only be liable in the event of wrongful intent or gross negligence on the part of its employees, unless there is a culpable breach of material obligations within the scope of these Terms and Conditions of use.  In this case, liability is limited to typical damages foreseeable at the time the user relationship was established; the University is not liable for other damages, e.g. for loss of profit, for loss of production, for other indirect damages or for loss of data and information. Liability for damage resulting from injury to life, body or health remains unaffected.</p>
-      <p>(4)  Possible official liability claims against the university remain unaffected by the above provisions.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 10 Wrongful use</span>
-      <p>The University reserves the right to investigate suspected misuse or significant violations of these Terms and Conditions, to take appropriate precautions and, in the event of reasonable suspicion, to block the User's access to the Services – at least until the user has cleared up the suspicion – and/or, if necessary, to delete the user account in the event of particularly serious violations. If the User clears up the suspicion, the block will be lifted. Every User must notify the University immediately of any indications of misuse of the service.</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 11 Applicable law</span>
-      <p>The law of the Federal Republic of Germany shall apply exclusively. The mandatory provisions of the country in which you have your habitual residence remain unaffected</p>
-    </div>
-  </div>
-</div>
-
-<div class="col s12">
-  <div class="card">
-    <div class="card-content">
-      <span class="card-title">§ 12 Place of jurisdiction</span>
-      <p>If you do not have a place of residence in the Federal Republic of Germany, if you move your place of residence abroad after registration, or if your place of residence is not known at the time the action is filed, the place of jurisdiction for all disputes arising from and in connection with the user relationship shall be the local ("Amtsgericht") or regional ("Landgericht") court of Bielefeld.</p>
-    </div>
-  </div>
-</div>

app/users/__init__.py

@@ -15,4 +15,4 @@ def before_request():
     pass
 
 
-from . import cli, events, json_routes, routes, settings
+from . import events, json_routes, routes, settings

app/users/cli.py

@@ -1,14 +0,0 @@
-from app.models import User
-import os
-import shutil
-from app import db
-from . import bp
-
-
-@bp.cli.command('reset')
-def reset():
-    ''' Reset terms of use accept '''
-    for user in [x for x in User.query.all() if x.terms_of_use_accepted]:
-        print(f'Resetting user {user.username}')
-        user.terms_of_use_accepted = False
-    db.session.commit()