Skip to content

GitLab

Commit da79de1e authored by Gradl, Tobias's avatar Gradl, Tobias
Browse files

Add 'doku/' from commit 'b424b44a' 

git-subtree-dir: doku
git-subtree-mainline: c068b330
git-subtree-split: b424b44a
parents c068b330 b424b44a
Expand all Hide whitespace changes
Inline Side-by-side
doku/.gitignore 0 → 100644
View file @ da79de1e
# Build paths
/target/
/docs/_build/
# ---> Java
*.class
# Mobile Tools for Java (J2ME)
.mtj.tmp/
# Package Files #
*.jar
*.war
*.ear
# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
hs_err_pid*
# ---> Eclipse
*.pydevproject
.metadata
.gradle
bin/
tmp/
*.tmp
*.bak
*.swp
*~.nib
local.properties
.settings/
.loadpath
# Eclipse Core
.project
# External tool builders
.externalToolBuilders/
# Locally stored "Eclipse launch configurations"
*.launch
# CDT-specific
.cproject
# JDT-specific (Eclipse Java Development Tools)
.classpath
# Java annotation processor (APT)
.factorypath
# PDT-specific
.buildpath
# sbteclipse plugin
.target
# TeXlipse plugin
.texlipse
.springBeans
doku/Jenkinsfile 0 → 100644
View file @ da79de1e
#!/usr/bin/env groovy
node {
def mvnHome
stage('Preparation') {
git 'https://github.com/tgradl/cosmotool.git'
mvnHome = tool 'Maven 3.5.0'
}
stage('Build') {
sh '''
#echo "-- Updating submodules"
#git submodule init &&
#git submodule update --force --remote &&
umask 0022
cd docs
echo "-- Setting up Virtualenv"
virtualenv venv
pwd
. venv/bin/activate
echo "-- Installing requirements"
pip install -r requirements.txt
echo "-- Building HTML version within $(pwd)"
make clean html
echo "-- Creating package"
VERSION=$(grep ^version conf.py | sed \'s/version = \'\\\'\'\\(.*\\)\'\\\'\'/\\1/g\')
fpm -t deb -a noarch -s dir --name dariah-de-cosmotool-doc \
--description='DARIAH-DE Cosmotool Documentation' \
--maintainer='DARIAH-DE <info@de.dariah.eu>' \
--vendor='DARIAH-DE' \
--url='https://cosmotool.de.dariah.eu' \
--iteration $(expr $BUILD_NUMBER + 299) \
--version $VERSION \
-x ".git**" \
-x "**/.git**" \
-x "**/.hg**" \
-x "**/.svn**" \
-x ".buildinfo" \
-x "**/*.deb" \
--prefix /var/www/doc/cosmotool \
-C _build/html .
'''
}
stage('Publish') {
def dVersion = sh(returnStdout: true, script: 'grep ^version ./docs/conf.py | sed \'s/version = \'\\\'\'\\(.*\\)\'\\\'\'/\\1/g\'').trim()
def snapshot = dVersion.contains("SNAPSHOT")
if (snapshot) {
doDebSnapshot('dariah-de-cosmotool-doc', dVersion)
}
else {
doDebRelease('dariah-de-cosmotool-doc', dVersion)
}
}
}
def doDebRelease(pname, pversion) {
echo "Publishing Debian package ${pname} for RELEASE version ${pversion}"
sh "PLOC=\$(ls ./docs/*.deb); curl -X POST -F file=@\${PLOC} http://localhost:8008/api/files/${pname}-${pversion}"
sh "curl -X POST http://localhost:8008/api/repos/releases/file/${pname}-${pversion}"
sh "curl -X PUT -H 'Content-Type: application/json' --data '{}' http://localhost:8008/api/publish/:./trusty"
sh "rm ./docs/*.deb"
}
def doDebSnapshot(pname, pversion) {
echo "Publishing Debian package ${pname} for SNAPSHOT version ${pversion}"
sh "PLOC=\$(ls ./docs/*.deb); curl -X POST -F file=@\${PLOC} http://localhost:8008/api/files/${pname}-${pversion}"
sh "curl -X POST http://localhost:8008/api/repos/snapshots/file/${pname}-${pversion}"
sh "curl -X PUT -H 'Content-Type: application/json' --data '{}' http://localhost:8008/api/publish/:./trusty"
sh "rm ./docs/*.deb"
}
doku/LICENSE 0 → 100644
View file @ da79de1e
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
doku/README.md 0 → 100644
View file @ da79de1e
# cosmotool
doku/docs/Makefile 0 → 100644
View file @ da79de1e
# Makefile for Sphinx documentation
#
# You can set these variables from the command line.
SPHINXOPTS =
SPHINXBUILD = sphinx-build
PAPER =
BUILDDIR = _build
# User-friendly check for sphinx-build
ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
endif
# Internal variables.
PAPEROPT_a4 = -D latex_paper_size=a4
PAPEROPT_letter = -D latex_paper_size=letter
ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
# the i18n builder cannot share the environment and doctrees with the others
I18NSPHINXOPTS = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest coverage gettext
help:
@echo "Please use \`make <target>' where <target> is one of"
@echo " html to make standalone HTML files"
@echo " dirhtml to make HTML files named index.html in directories"
@echo " singlehtml to make a single large HTML file"
@echo " pickle to make pickle files"
@echo " json to make JSON files"
@echo " htmlhelp to make HTML files and a HTML help project"
@echo " qthelp to make HTML files and a qthelp project"
@echo " applehelp to make an Apple Help Book"
@echo " devhelp to make HTML files and a Devhelp project"
@echo " epub to make an epub"
@echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
@echo " latexpdf to make LaTeX files and run them through pdflatex"
@echo " latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
@echo " text to make text files"
@echo " man to make manual pages"
@echo " texinfo to make Texinfo files"
@echo " info to make Texinfo files and run them through makeinfo"
@echo " gettext to make PO message catalogs"
@echo " changes to make an overview of all changed/added/deprecated items"
@echo " xml to make Docutils-native XML files"
@echo " pseudoxml to make pseudoxml-XML files for display purposes"
@echo " linkcheck to check all external links for integrity"
@echo " doctest to run all doctests embedded in the documentation (if enabled)"
@echo " coverage to run coverage check of the documentation (if enabled)"
clean:
rm -rf $(BUILDDIR)/*
html:
$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
dirhtml:
$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
singlehtml:
$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
@echo
@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
pickle:
$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
@echo
@echo "Build finished; now you can process the pickle files."
json:
$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
@echo
@echo "Build finished; now you can process the JSON files."
htmlhelp:
$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
@echo
@echo "Build finished; now you can run HTML Help Workshop with the" \
".hhp project file in $(BUILDDIR)/htmlhelp."
qthelp:
$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
@echo
@echo "Build finished; now you can run "qcollectiongenerator" with the" \
".qhcp project file in $(BUILDDIR)/qthelp, like this:"
@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/tgimport.qhcp"
@echo "To view the help file:"
@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/tgimport.qhc"
applehelp:
$(SPHINXBUILD) -b applehelp $(ALLSPHINXOPTS) $(BUILDDIR)/applehelp
@echo
@echo "Build finished. The help book is in $(BUILDDIR)/applehelp."
@echo "N.B. You won't be able to view it unless you put it in" \
"~/Library/Documentation/Help or install it in your application" \
"bundle."
devhelp:
$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
@echo
@echo "Build finished."
@echo "To view the help file:"
@echo "# mkdir -p $$HOME/.local/share/devhelp/tgimport"
@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/tgimport"
@echo "# devhelp"
epub:
$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
@echo
@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
latex:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo
@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
@echo "Run \`make' in that directory to run these through (pdf)latex" \
"(use \`make latexpdf' here to do that automatically)."
latexpdf:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through pdflatex..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
latexpdfja:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through platex and dvipdfmx..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
text:
$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
@echo
@echo "Build finished. The text files are in $(BUILDDIR)/text."
man:
$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
@echo
@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
texinfo:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo
@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
@echo "Run \`make' in that directory to run these through makeinfo" \
"(use \`make info' here to do that automatically)."
info:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo "Running Texinfo files through makeinfo..."
make -C $(BUILDDIR)/texinfo info
@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
gettext:
$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
@echo
@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
changes:
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
@echo
@echo "The overview file is in $(BUILDDIR)/changes."
linkcheck:
$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
@echo
@echo "Link check complete; look for any errors in the above output " \
"or in $(BUILDDIR)/linkcheck/output.txt."
doctest:
$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
@echo "Testing of doctests in the sources finished, look at the " \
"results in $(BUILDDIR)/doctest/output.txt."
coverage:
$(SPHINXBUILD) -b coverage $(ALLSPHINXOPTS) $(BUILDDIR)/coverage
@echo "Testing of coverage in the sources finished, look at the " \
"results in $(BUILDDIR)/coverage/python.txt."
xml:
$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
@echo
@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
pseudoxml:
$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
@echo
@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."
doku/docs/_static/dariah_logo.svg 0 → 100644
View file @ da79de1e
This diff is collapsed.
doku/docs/_static/textgrid.css 0 → 100644
View file @ da79de1e
@import url("./css/theme.css");
.wy-side-nav-search {
background-color:#CCCCCC;
}
.wy-dropdown > a {
color:#222222;
}
.wy-side-nav-search > a,
.wy-side-nav-search .wy-dropdown > a,
.wy-side-nav-search > div.version {
color:#222222;
}
doku/docs/background.rst 0 → 100644
View file @ da79de1e
===========
Hintergrund
===========
Die Arbeiten am Cosmotool wurden im Rahmen der vergangenen Projektphase von DARIAH-DE begonnen – primär um die prinzipielle Eignung eines solchen Werkzeugs für die Unterstützung der geisteswissenschaftlichen Forschung zu erheben und Anforderungen an die Umsetzung einer produktiven Version des Cosmotools im Rahmen der aktuellen Förderphase zu sammeln. Der Fokus der Konzeption und prototypischen Implementierung des Cosmotools lag und liegt dabei primär auf Anforderungen, die aus der qualitativen, historischen Forschung am Leibniz Institut für Europäische Geschichte (IEG) Mainz abgeleitet werden können.
Mit Hilfe automatischer Methoden zur Analyse und Visualisierung von Daten soll die qualitative Forschung insbesondere wie folgt unterstützt werden:
- Biographische Informationen aus unterschiedlichen Quellen sollen zu (potenziell) transnationalen Lebens- und Bewegungsprofilen historischer Personen zusammengeführt werden.
- Die interaktive Erschließung dieser Profile aus unterschiedlichen Dimensionen (Personen, Orte, Zeitpunkte/-räume, Ideen/Ereignisse) soll Kriterien für Zusammenhänge zwischen Entitäten, die Gruppierung von Personen und die Visualisierung dieser Personengruppen ermöglichen.
Anwendungsfälle für die Analyse und Verarbeitung biographischer Daten mit Hilfe informatischer Methoden waren hierbei zunächst auf das Cosmobilities Projekt [#cosmobilities]_ des IEG fokussiert. Durch die Erweiterung der Betrachtung auf einen weiteren, primären Anwendungsfall der historischen Forschung am IEG, sowie den Rückmeldungen von Nutzern und Interessenten des Cosmotools konnten Anforderungen so generalisiert werden, dass einmal implementierte, technisch generische Konzepte zu einer Unterstützung einer Vielzahl spezifischer, fachlicher Anwendungsfälle führen.
Motivation
----------
Internationale Perspektive auf Biographien stärken
++++++++++++++++++++++++++++++++++++++++++++++++++
In biographischen Beschreibungen werden historische Akteure oft im Rahmen einer Nation portraitiert [Pa15]_. Das Cosmotool kann durch Erfassen der Daten aus mehreren Quellen ein breiteres Bild zeichnen und potenziell die internationale Karrieren der historischen Persönlichkeiten erfassen. Auch wenn Versuche eine inter-/transnationale Geschichte zu schreiben nicht neu sind, bietet das Cosmotool einen Vorteil in dem es einen schnelleren Überblick über die schematischen biographischen Profile erlaubt.
Erkennen der Muster in Biographien
++++++++++++++++++++++++++++++++++
Methode und Forschungsstand
---------------------------
Die Fragen um Schulbildung in Russland, Einfluss der deutschsprachigen Bevölkerung darauf und der pietistischen Mission wurden bis dato hermeneutisch bearbeitet. Im Zentrum des Interesses stand in diesen frühen Arbeiten die Petrischule, deren Stellung gegenüber der Regierung bzw. die Frage, inwieweit die Einflussnahme der russischen Obrigkeit die Schulorganisation veränderte oder sogar zur Schließung von Schulen führte. Deutlich wird in diesen Studien, dass Russland seit Peter dem Großen das Bildungswesen von oben nach unten aufbaute und spätestens seit 1762 auch deutsche Fremdenschulen darin integrierte. Der Aufsatz von Ralf Tuchtenhagen [Tu94]_ beschäftigt sich ebenfalls mit der Entwicklung der Kirchenschulen in St. Petersburg. Eingerichtet für Kinder der deutschen Handwerker und „Kleinunternehmer“, boten zuerst nur Elementarschulen, dann im Laufe des 18. Jahrhunderts auch Lateinschulen einen sich stetig erweiternden Fächerkanon an. Zu den Interessen der pietistischen Mission in Russland liegen Arbeiten von Eduard Winter [Wi53]_ vor, der schon in den 1950er Jahren darauf hinwies, dass die Franckeschen Anstalten Verbindungen nach Russland hatten. Durch die Analyse der pietistischen Netzwerke stellte er fest, dass viele Pastoren, Lehrer oder Gönner der Petri- und Annenkirche zu diesem Netzwerk gehörten. Günter Mühlpfort [Mü00]_ und Galina Smagina [Sm00]_ betonen die Verbindung von Pietisten mit der Aufklärung in Russland und mit deutschsprachigen Wissenschaftlern [#methode1]_. Im Mittelpunkt dieser Arbeiten stehen die Akademie der Wissenschaften und das Gymnasium bei der Akademie. Swetlana Mengel zeigte konkrete Beispiele des kulturellen Austausches zwischen Russland und Halle in Form von Übersetzungen der pietistischen Erbauungsliteratur. [Me09]_
Quantitative Unterstützung
--------------------------
Fragen der Bildung und des Ideentransfers lassen sich nicht leicht quantifizieren. Dennoch können quantitative Methoden unterstützend sein, um die sozialgeschichtliche Dimension der Frage zu erforschen. Kollektivbiographien können quantitativ auf ihre (soziale) Struktur und Wandel dieser Struktur untersucht werden.
So könnten beispielsweise Eigenschaften für die Gruppe der Missionare identifiziert werden, die diese von anderen Personengruppen abgrenzen. Durch die eine iterative Verfeinerung der Beschreibung zur Bildung von Personengruppen ist es ein Ziel der Entwicklung des Cosmotools, durch die Anwendung quantitativer Verfahren bedeutungsähnliche Personen zu identifizieren, d. h. Personen, deren Eigenschaften sich mit denen bereits definierter Gruppen passen.
.. [#methode1] Dazu zählen auch Arbeiten von [Be02]_
.. [#cosmobilities] http://www.ieg-mainz.de/Forschungsprojekte------_site.site..ls_dir._nav.17_f.69_likecms.html
doku/docs/bibliography.rst 0 → 100644
View file @ da79de1e
=============
Bibliographie
=============
.. _eigene_veröffentlichungen:
Eigene Veröffentlichungen
-------------------------
.. [Gr16a] Gradl, Tobias; Henrich, Andreas (2016): Die DARIAH-DE-Föderationsarchitektur – Datenintegration im Spannungsfeld forschungsspezifischer und domänenübergreifender Anforderungen. In: Bibliothek Forschung und Praxis 40 (2). DOI: 10.1515/bfp-2016-0027.
.. [Gr16b] Gradl, Tobias; Henrich, Andreas (2016): Nutzung und Kombination von Daten aus strukturierten und unstrukturierten Quellen zur Identifikation transnationaler Lebensläufe. In: Elisabeth Burr (Hg.): DHd 2016. Book of abstracts. DHd 2016 - Modellierung - Vernetzung - Visualisierung, 7. bis 12. März 2016. Universität Leipzig: nisaba Verlag, S. 135–138.
.. [Gr16c] Gradl, Tobias; Henrich, Andreas (2016): Extending Data Models by Declaratively Specifying Contextual Knowledge. In: Robert Sablatnig und Tamir Hassan (Hg.): DocEng '16 Proceedings of the 2016 ACM Symposium on Document Engineering. DocEng'16. Vienna, Austria, September 13-16, 2016. New York, NY, USA: ACM, S. 123–126.
.. [Gr17] Gradl, Tobias; Aschauer, Anna; Dogunke, Swantje; Klaffki, Lisa; Schmunk, Stefan; Steyer, Timo (2017): Daten sammeln, modellieren und durchsuchen mit DARIAH-DE. Workshop im Rahmen der DHd 2017. In: Michael Stolz (Hg.): Konferenzabstracts. 4. Tagung des Verbands Digital Humanities im deutschsprachigen Raum e. V. Bern, 13. bis 18. Februar 2017. Universität Bern. Bern: Universität Bern, S. 22–27.
.. [He15] Henrich, Andreas; Gradl, Tobias (2015): Erforschung der Weltenwanderer : Über die Nutzung der Wikipedia zur Identifikation grenzüberschreitender Lebensläufe. In: Uni.vers Forschung : das Magazin der Otto-Friedrich-Universität Bamberg. ISSN 1618-9019, S. 46-49.
Quellen
-------
.. [Be02] Hermann Beyer-Thoma, Bayern und Osteuropa im 18. Jahrhundert: Gelehrtenmigration und Region, in: Hermann Beyer-Thoma, Olivia Griese, Zsolt K. Lengyel (Hrsg), Münchener Forschungen zur Geschichte Ost- und Südosteuropas. Werkstattberichte, Bd. 5, Ars Una 2002,S. 99–134.
.. [Go84] Goeke, Dieter; Kornelius, Joachim (1984): Wortfelder aus bemessenen Ordnungen. Ein empirischer Beitrag zur Wortfeldforschung. c 1984. Trier: WVT-Wissenschaftlicher Verlag.
.. [Me09] Swetlana Mengel,. „Russische Drucke aus Halle - "ein vergessenes Kapitel der slavischen Philologie".“ In Dmitrij I. Tschižewskij: Impulse eines Philologen und Philosophen für eine komparative Geistesgeschichte. Hrsg. von Angela Richter und Brigitte Klosterberg, 21–30. Berlin, Münster: Lit, 2009
.. [Mü00] Günter Mühlpfordt, "Hallesche Bildung in Russland 1696-1831: Berufungen, Lehrtätigkeiten, Schulgründungen, Schulreformen, Bücher, Didaktik." In Nemcy v Rossii: Russko-nemeckie naučnye i kul'turnye svjazi. Hrsg. von Galina I. Smagina, 159–169. St. Peterburg: Bulanin, 2000.
.. [Pa15] Sarah Panter, Johannes Paulmann und Margit Szöllösi-Janze: Mobility and Biography. Methodological Challenges and Perspectives, in: Mobility and Biography, hrsg. von Sarah Panter (=Jahrbuch für Europäische Geschichte / European History Yearbook 16 (2015)), Berlin:De Gruyter Oldenbourg, S. 1-14
.. [Sm00] Galina I. Smagina, "Russisch- deutsche Beziehungen in der Wissenschaft im 18. und 19. Jahrhundert." In Nemcy v Rossii: Russko-nemeckie naučnye i kul'turnye svjazi. Hrsg. von Galina I. Smagina, S. 208–224. St. Peterburg: Bulanin, 2000.
.. [Tu94] Ralph Tuchtenhagen, "Bildung als Auftrag und Aufgabe. Deutsche Schulen in St. Petersburg 1703-1934." In Deutsche in St. Petersburg und Moskau vom 18. Jahrhundert bis zum Ausbruch des Ersten Weltkrieges. Hrsg. von Dittmar Dahlmann. Lüneburg: Verl. Nordostdt. Kulturwerk, 1994. Siehe auch Jan Kusber, Eliten- und Volksbildung im Zarenreich während des 18. und in der ersten Hälfte des 19. Jahrhunderts: Studien zu Diskurs, Gesetzgebung und Umsetzung. Quellen und Studien zur Geschichte des östlichen Europa. Bd. 65. Stuttgart: Steiner, 2004.
.. [Wi53] Eduard Winter, Halle als Ausgangspunkt der deutschen Russlandkunde im 18. Jahrhundert. Berlin: Akad.-Verl., 1953.
Organisierte Workshops
----------------------
**15. Mai 2018**
DARIAH-DE Methodenworkshop „Computergestütze Analyse biographischer Texte”. Gemeinsamer DARIAH-DE Cluster 5 Methodenworkshop. Universität Würzburg
**27. Februar 2018**
DHd-Workshop „Reisewege in Raum und Zeit” im Rahmen der DHd 2018 in Köln. Universität zu Köln. https://dhd-blog.org/?p=9834
**16.-17. März 2017**
DARIAH-DE Expertenseminar „Biographische Daten und Ihre Analyse in der historischen Forschung“. IEG, Mainz. Bericht: https://dhd-blog.org/?p=8000
**13. Februar 2017**
DHd-Workshop „Daten sammeln, modellieren und durchsuchen mit DARIAH-DE” im Rahmen der DHd 2017 in Bern. Universität Bern. https://doi.org/10.5281/zenodo.582316
**19.-20. November 2015**
DARIAH-DE Methodenworkshop „Quantitative Vorauswahl und Validierung für ein qualitatives Arbeiten in den Geisteswissenschaften: Ein iterativer Prozess?”. Universität Bamberg. https://www.uni-bamberg.de/minf/forschung/dariah-de/workshop2015/
**23.-24. Januar 2015**
»Cosmobilities« – Perspektiven, Herausforderungen, Synergien. IEG, Mainz. `http://www.ieg-mainz.de/media/public/PDF/Cosmobilities_website_23_24_1_15_.pdf <http://www.ieg-mainz.de/media/public/PDF/Cosmobilities_website_23_24_1_15_.pdf>`_
.. _abschlussarbeiten:
Abschlussarbeiten
-----------------
werden in Kürze an dieser Stelle ergänzt
\ No newline at end of file
doku/docs/conf.py 0 → 100644
View file @ da79de1e
# -*- coding: utf-8 -*-
#
# tgimport documentation build configuration file, created by
# sphinx-quickstart on Thu May 21 16:32:23 2015.
#
# This file is execfile()d with the current directory set to its
# containing dir.
#
# Note that not all possible configuration values are present in this
# autogenerated file.
#
# All configuration values have a default; values that are commented out
# serve to show the default.
import sys
import os
import shlex
#import numfig
# If extensions (or modules to document with autodoc) are in another directory,
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
#sys.path.insert(0, os.path.abspath('.'))
# -- General configuration ------------------------------------------------
# If your documentation needs a minimal Sphinx version, state it here.
#needs_sphinx = '1.0'
# Add any Sphinx extension module names here, as strings. They can be
# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
# ones.
extensions = [
'sphinx.ext.autodoc',
'sphinx.ext.intersphinx',
'sphinx.ext.todo',
'sphinxcontrib.httpdomain',
]
# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
# The suffix(es) of source filenames.
# You can specify multiple suffix as a list of string:
# source_suffix = ['.rst', '.md']
source_suffix = '.rst'
# The encoding of source files.
#source_encoding = 'utf-8-sig'
# The master toctree document.
master_doc = 'index'
# General information about the project.
project = u'DARIAH-DE Cosmotool'
copyright = u'2018, DARIAH-DE'
author = u'DARIAH-DE'
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
# built documents.
#
# The short X.Y version.
#version = '2.0-SNAPSHOT'
version = '2.0-RELEASE'
# The full version, including alpha/beta/rc tags.
release = '2.0'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
#
# This is also used if you do content translation via gettext catalogs.
# Usually you set "language" from the command line for these cases.
language = None
# There are two options for replacing |today|: either, you set today to some
# non-false value, then it is used:
#today = ''
# Else, today_fmt is used as the format for a strftime call.
#today_fmt = '%B %d, %Y'
# List of patterns, relative to source directory, that match files and
# directories to ignore when looking for source files.
exclude_patterns = ['_build']
# The reST default role (used for this markup: `text`) to use for all
# documents.
#default_role = None
# If true, '()' will be appended to :func: etc. cross-reference text.
#add_function_parentheses = True
# If true, the current module name will be prepended to all description
# unit titles (such as .. function::).
#add_module_names = True