add material initially for workshop

README.md

-# Collaborative Coding with Emacs
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://git.rwth-aachen.de/dl/workshops/collaborative-coding-with-emacs.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://git.rwth-aachen.de/dl/workshops/collaborative-coding-with-emacs/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

README.org

+* Collaborative Coding with Emacs
+
+[[file:img/nfdi-in-emacs-best-practice-overview.png]]
+
+* Abstract
+In our best-practice presentation we will show an efficient way of combining
+information and enriching it by retrieving data, processing it, and finally
+exporting it, all with one tool: Emacs and its "org-mode". Org-mode is a simple
+yet flexible markdown language that enables the user to write everything from
+quick personal notes to long form professional documents. In this presentation,
+we will demonstrate not only org-mode, but also a few companion libraries that
+add functionality such as knowledge graph visualizations, literate programming,
+and collaborative editing to quickly create a deeply informative reference page.
+
+The starting point of our best practice is the NFDI about which we intend to
+retrieve and process certain information data gathered from wikidata. For this,
+we are additionally leveraging the "org-roam" emacs package, which provides
+functionality for quickly and simply linking together notes and ideas into a
+custom knowledge graph. Initially, we will write a short abstract about the NFDI
+and embed it into our existing knowledge graph by linking it to other existing
+nodes. In the visualized graph (using the “org-roam-ui” package), links and
+secondary connections to other existing nodes can now be revealed.
+
+Next, we would like to enrich the text about the NFDI by with data retrieved
+from the Wikidata API. A convenient way of creating self-documenting code is the
+approach called “literate programming”, which presents program logic embedded
+within human language text. In Emacs we achieve this by using the “org-babel”
+package. Perhaps now we find it is helpful to collaborate with a colleague in
+the document: while one is writing the code, the other can explain its use and
+interpret the results. We will do this simultaneously in the same document using
+a method called “crdt” (conflict-free replicated data type) and – of course –
+there is also an implementation of this in Emacs. The results of the code blocks
+can be used for further analysis and shared throughout the same document.
+
+Finally, for the sake of proper and barrier free documentation, we show how to
+export the document to various formats like pdf, html, txt etc. using either the
+built-in feature of org-mode or the implementation of pandoc.
+
+* How to use the files
+
+The main file is [[file:nfdi-in-emacs-with-orgmode.org]] in which you find an
+enhanced and documented flow of the data.
+
+The file [[file:nfdi-in-emacs-with-orgmode-live-coding.org]] can be used as a blue
+print for a live coding session.

custom-export.setup

+# -*- mode: org; -*-
+
+#+LATEX_COMPILER: lualatex
+#+LATEX_CLASS: article
+#+LATEX_CLASS_OPTIONS: [11pt]
+#+LATEX_HEADER: \usepackage[french,english]{babel}
+#+LATEX_HEADER: \usepackage[a4paper,top=3cm,bottom=3cm]{geometry}
+#+LATEX_HEADER: \usepackage{minimalist}
+#+LATEX_HEADER: \usepackage{fontspec}
+#+LATEX_HEADER: \usepackage{caption} \captionsetup{labelfont=bf,font={sf,small}}
+#+LATEX_HEADER: \setmainfont{TeX Gyre Pagella}
+#+LATEX_HEADER: \usepackage{enumitem} \setlist{nosep}
+#+LATEX_HEADER: \usepackage{longtable}
+#+LATEX_HEADER: \usepackage{microtype}
+#+LATEX_HEADER: \AtBeginEnvironment{longtable}{\footnotesize}
+#+LATEX_HEADER: \setminted{fontsize=\small,baselinestretch=.75}
+#+LATEX_HEADER: \usepackage[backend=biber, style=ext-verbose]{biblatex}
+#+LATEX_HEADER: \usepackage[norule,marginal,hang]{footmisc}
+
+
+#+OPTIONS: toc:2
+
+
+#+OPTIONS: html-style:nil
+#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="https://fniessen.github.io/org-html-themes/src/readtheorg_theme/css/htmlize.css"/>
+#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="https://fniessen.github.io/org-html-themes/src/readtheorg_theme/css/readtheorg.css"/>
+
+#+HTML_HEAD: <script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
+#+HTML_HEAD: <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js"></script>
+#+HTML_HEAD: <script type="text/javascript" src="https://fniessen.github.io/org-html-themes/src/lib/js/jquery.stickytableheaders.min.js"></script>
+#+HTML_HEAD: <script type="text/javascript" src="https://fniessen.github.io/org-html-themes/src/readtheorg_theme/js/readtheorg.js"></script>
+#+HTML_HEAD: <style> #content{max-width:1800px;}</style>

emacs-references.bib

+@article{Bossert2023Wikidata,
+  author          = {Bossert, Lukas C. and Cyra, Magdalene and Demandt, Évariste
+                  and Fingerhuth, Matthias and Yildiz, Ceren},
+  title           = {Das muss noch in Wikidata rein},
+  date            = {2023-09-11},
+  journaltitle    = {Bausteine FDM},
+  pages           = {2-18},
+  doi             = {10.17192/bfdm.2023.5.8580}
+}
+
+@incollection{Strobel1996Linux,
+  doi             = {10.1007/978-1-4684-0247-6_13},
+  year            = 1996,
+  publisher       = {Springer {US}},
+  pages           = {287--324},
+  author          = {Stefan Strobel and Thomas Uhl},
+  title           = {{GNU} Emacs},
+  booktitle       = {Linux Unleashing the Workstation in Your {PC}}
+}
+
+
+@article{Kitchin2016DataSharing,
+  doi             = {10.1007/s00799-016-0173-7},
+  year            = 2016,
+  month           = jun,
+  publisher       = {Springer Science and Business Media {LLC}},
+  volume          = 18,
+  number          = 2,
+  pages           = {93--98},
+  author          = {John R. Kitchin and Ana E. Van Gulick and Lisa D. Zilinski},
+  title           = {Automating data sharing through authoring tools},
+  journal         = {International Journal on Digital Libraries}
+}
+
+@book{Hahn2016Emacs,
+  doi             = {10.1007/978-1-4842-1703-0},
+  year            = 2016,
+  publisher       = {Apress},
+  author          = {Harley Hahn},
+  title           = {Harley Hahn’s Emacs Field Guide}
+}
+
+@inproceedings{Stanisic2014,
+  title           = {Effective Reproducible Research with Org-Mode and Git},
+  booktitle       = {Euro-Par 2014: {{Parallel}} Processing Workshops},
+  author          = {Stanisic, Luka and Legrand, Arnaud},
+  editor          = {Lopes, Luís and Žilinskas, Julius and Costan, Alexandru and
+                  Cascella, Roberto G. and Kecskemeti, Gabor and Jeannot,
+                  Emmanuel and Cannataro, Mario and Ricci, Laura and Benkner,
+                  Siegfried and Petit, Salvador and Scarano, Vittorio and
+                  Gracia, José and Hunold, Sascha and Scott, Stephen L. and
+                  Lankes, Stefan and Lengauer, Christian and Carretero, Jesus
+                  and Breitbart, Jens and Alexander, Michael},
+  date            = 2014,
+  pages           = {475--486},
+  publisher       = {{Springer International Publishing}},
+  location        = {{Cham}},
+  abstract        = {In this article we address the question of developing a
+                  lightweight and effective workflow for conducting experimental
+                  research on modern parallel computer systems in a reproducible
+                  way. Our workflow simply builds on two well-known tools
+                  (Org-mode and Git) and enables to address issues such as
+                  provenance tracking, experimental setup reconstruction,
+                  replicable analysis. Although this workflow is perfectible and
+                  cannot be seen as a final solution, we have been using it for
+                  two years now and we have recently published a fully
+                  reproducible article [3], which demonstrates the effectiveness
+                  of our proposal.},
+  isbn            = {978-3-319-14325-5}
+}

nfdi-in-emacs-with-orgmode-live-coding.org

+#+begin_comment
+SETUP:
+- DOOM big font (SPC t b)
+
+#+end_comment
+
+* Overview
+Welcome to our best practice example!
+#+caption: Workflow of the document. Source [[https://excalidraw.com/#room=8617c3374a9c2c2c895b,a_SoKClI-tyAxWfSgzThWQ][Excalidraw]].
+#+attr_org: :width 1700
+[[file:nfdi-in-emacs-best-practice-overview.png]]
+
+* Introduce
+What is Emacs and *org-mode*?
+#+begin_quote
+Back to the future for plain text\\
+(Carsten Dominik)
+#+end_quote
+
+Let’s make an executive summary of org-mode:
+- Module for [[https://emacs.org][Emacs]]
+- Plain text based
+- Around since 2003
+- Meant for (scientific) text production and organisation
+  + project management
+  + agenda, diary, journaling
+  + personal knowledge management
+  + presentation
+  + single-source-publishing
+  + literate programming
+- Extensible and fully customizable
+
+
+
+
+
+* Prepare
+
+@@comment: showing crdt function@@
+
+
+
+
+** Data retrieval using SPARQL
+Retrieve the data from Wikidata via SPARQL query.
+For more, have a look at [cite:@Bossert2023Wikidata]
+@@comment:add bibliography in header: #+bibliography: emacs-references.bib@@
+
+
+#+name: raw-dataset
+#+caption: Retrieving the dataset from wikidata
+#+BEGIN_SRC sparql -n  :url https://query.wikidata.org/sparql :cache yes :exports both
+SELECT ?wLabel ?pLabel
+WHERE
+{
+  ?p wdt:P31 wd:Q98270496 .
+  ?p wdt:P1416 ?w .
+  SERVICE wikibase:label { bd:serviceParam wikibase:language "en" . }
+}
+ORDER BY ASC(?wLabel) ASC(?pLabel)
+LIMIT 50
+#+END_SRC
+
+#+RESULTS[49333e23a608795eee0a37982e900a3c0fbecf84]: raw-dataset
+| wLabel                                                       | pLabel            |
+|--------------------------------------------------------------+-------------------|
+| Q105775472                                                   | NFDI4Health       |
+| Q1117007                                                     | NFDI4Health       |
+| Q115254989                                                   | NFDI4Objects      |
+| Q1205424                                                     | NFDI4Objects      |
+| Q17575706                                                    | NFDI4Objects      |
+| Academy of Sciences and Humanities in Hamburg                | Text+             |
+| Academy of Sciences and Literature Mainz                     | NFDI4Culture      |
+| Academy of Sciences and Literature Mainz                     | NFDI4Memory       |
+| Academy of Sciences and Literature Mainz                     | NFDI4Objects      |
+| Academy of Sciences and Literature Mainz                     | Text+             |
+| Alfred Wegener Institute for Polar and Marine Research       | NFDI4Biodiversity |
+| Alfred Wegener Institute for Polar and Marine Research       | NFDI4DataScience  |
+| Alfred Wegener Institute for Polar and Marine Research       | NFDI4Earth        |
+| Anthropological Society (Munich)                             | NFDI4Objects      |
+| Arachnologische Gesellschaft                                 | NFDI4Biodiversity |
+| Arbeitskreis Provenienzforschung e.V.                        | NFDI4Culture      |
+| Arbeitskreis Provenienzforschung e.V.                        | NFDI4Memory       |
+| Archivschule Marburg                                         | NFDI4Memory       |
+| Archäologische Kommission für Niedersachsen                  | NFDI4Objects      |
+| Archäologisches Museum Hamburg und Stadtmuseum Harburg       | NFDI4Objects      |
+| Arthistoricum                                                | NFDI4Culture      |
+| Association for Data-Intensive Radio Astronomy               | PUNCH4NFDI        |
+| Association for Technology and Construction in Agriculture   | FAIRAgro          |
+| Association of German Architects                             | NFDI4Culture      |
+| Association of Population Based Cancer Registries in Germany | NFDI4Health       |
+| Association of states archaeologists                         | NFDI4Objects      |
+| BERD@NFDI                                                    | Base4NFDI         |
+| Bach-Archiv Leipzig                                          | NFDI4Culture      |
+| Bauhaus-Universität Weimar                                   | NFDI4Ing          |
+| Bavarian Academy of Sciences and Humanities                  | BERD@NFDI         |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Culture      |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Earth        |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Memory       |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Objects      |
+| Bavarian Academy of Sciences and Humanities                  | NFDIxCS           |
+| Bavarian Academy of Sciences and Humanities                  | PUNCH4NFDI        |
+| Bavarian Academy of Sciences and Humanities                  | Text+             |
+| Bavarian Forest National Park                                | NFDI4Biodiversity |
+| Bavarian Natural History Collections                         | NFDI4Biodiversity |
+| Bavarian Natural History Collections                         | NFDI4Objects      |
+| Bavarian State Archaeological Collection                     | NFDI4Objects      |
+| Bavarian State Archives                                      | FAIRAgro          |
+| Bavarian State Archives                                      | NFDI4Biodiversity |
+| Bavarian State Archives                                      | NFDI4Earth        |
+| Bavarian State Archives                                      | NFDI4Objects      |
+| Bavarian State Library                                       | NFDI4Culture      |
+| Bavarian State Library                                       | NFDI4Memory       |
+| Bavarian State Painting Collections                          | NFDI4Culture      |
+| Bavarian State Research Center for Agriculture               | FAIRAgro          |
+| Beethoven House                                              | NFDI4Culture      |
+
+
+
+
+** Data cleaning using shell
+The data we got from listing [[raw-dataset]] is good but it needs further cleaning.
+
+#+caption: Cleaning the raw data.
+#+NAME: clean-dataset
+#+BEGIN_SRC sh -n :var input=raw-dataset :colnames yes :exports both
+echo "$input" | sed -E '/Q[0-9]+/d'
+#+END_SRC
+
+#+RESULTS: clean-dataset
+| wLabel                                                       | pLabel            |
+|--------------------------------------------------------------+-------------------|
+| Academy of Sciences and Humanities in Hamburg                | Text+             |
+| Academy of Sciences and Literature Mainz                     | NFDI4Culture      |
+| Academy of Sciences and Literature Mainz                     | NFDI4Memory       |
+| Academy of Sciences and Literature Mainz                     | NFDI4Objects      |
+| Academy of Sciences and Literature Mainz                     | Text+             |
+| Alfred Wegener Institute for Polar and Marine Research       | NFDI4Biodiversity |
+| Alfred Wegener Institute for Polar and Marine Research       | NFDI4DataScience  |
+| Alfred Wegener Institute for Polar and Marine Research       | NFDI4Earth        |
+| Anthropological Society (Munich)                             | NFDI4Objects      |
+| Arachnologische Gesellschaft                                 | NFDI4Biodiversity |
+| Arbeitskreis Provenienzforschung e.V.                        | NFDI4Culture      |
+| Arbeitskreis Provenienzforschung e.V.                        | NFDI4Memory       |
+| Archivschule Marburg                                         | NFDI4Memory       |
+| Archäologische Kommission für Niedersachsen                  | NFDI4Objects      |
+| Archäologisches Museum Hamburg und Stadtmuseum Harburg       | NFDI4Objects      |
+| Arthistoricum                                                | NFDI4Culture      |
+| Association for Data-Intensive Radio Astronomy               | PUNCH4NFDI        |
+| Association for Technology and Construction in Agriculture   | FAIRAgro          |
+| Association of German Architects                             | NFDI4Culture      |
+| Association of Population Based Cancer Registries in Germany | NFDI4Health       |
+| Association of states archaeologists                         | NFDI4Objects      |
+| BERD@NFDI                                                    | Base4NFDI         |
+| Bach-Archiv Leipzig                                          | NFDI4Culture      |
+| Bauhaus-Universität Weimar                                   | NFDI4Ing          |
+| Bavarian Academy of Sciences and Humanities                  | BERD@NFDI         |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Culture      |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Earth        |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Memory       |
+| Bavarian Academy of Sciences and Humanities                  | NFDI4Objects      |
+| Bavarian Academy of Sciences and Humanities                  | NFDIxCS           |
+| Bavarian Academy of Sciences and Humanities                  | PUNCH4NFDI        |
+| Bavarian Academy of Sciences and Humanities                  | Text+             |
+| Bavarian Forest National Park                                | NFDI4Biodiversity |
+| Bavarian Natural History Collections                         | NFDI4Biodiversity |
+| Bavarian Natural History Collections                         | NFDI4Objects      |
+| Bavarian State Archaeological Collection                     | NFDI4Objects      |
+| Bavarian State Archives                                      | FAIRAgro          |
+| Bavarian State Archives                                      | NFDI4Biodiversity |
+| Bavarian State Archives                                      | NFDI4Earth        |
+| Bavarian State Archives                                      | NFDI4Objects      |
+| Bavarian State Library                                       | NFDI4Culture      |
+| Bavarian State Library                                       | NFDI4Memory       |
+| Bavarian State Painting Collections                          | NFDI4Culture      |
+| Bavarian State Research Center for Agriculture               | FAIRAgro          |
+| Beethoven House                                              | NFDI4Culture      |
+
+
+* Process
+
+** Data Aggregation with Python
+
+#+BEGIN_SRC python -n :var clean_df=clean-dataset :colnames no :results replace table :exports both
+import pandas as pd
+df = pd.DataFrame(clean_df[1:], columns=clean_df[0])
+agg_df = (
+    df
+    .groupby("wLabel")
+    .size()
+    .sort_values(ascending=False)
+    .reset_index(name="Count"))
+return [list(agg_df.columns), None, *map(list, agg_df.values)]
+#+END_SRC
+
+#+RESULTS:
+| wLabel                                                       | Count |
+|--------------------------------------------------------------+-------|
+| Bavarian Academy of Sciences and Humanities                  |     8 |
+| Bavarian State Archives                                      |     4 |
+| Academy of Sciences and Literature Mainz                     |     4 |
+| Alfred Wegener Institute for Polar and Marine Research       |     3 |
+| Arbeitskreis Provenienzforschung e.V.                        |     2 |
+| Bavarian State Library                                       |     2 |
+| Bavarian Natural History Collections                         |     2 |
+| Academy of Sciences and Humanities in Hamburg                |     1 |
+| BERD@NFDI                                                    |     1 |
+| Bavarian State Research Center for Agriculture               |     1 |
+| Bavarian State Painting Collections                          |     1 |
+| Bavarian State Archaeological Collection                     |     1 |
+| Bavarian Forest National Park                                |     1 |
+| Bauhaus-Universität Weimar                                   |     1 |
+| Bach-Archiv Leipzig                                          |     1 |
+| Association of Population Based Cancer Registries in Germany |     1 |
+| Association of states archaeologists                         |     1 |
+| Association of German Architects                             |     1 |
+| Association for Technology and Construction in Agriculture   |     1 |
+| Association for Data-Intensive Radio Astronomy               |     1 |
+| Arthistoricum                                                |     1 |
+| Archäologisches Museum Hamburg und Stadtmuseum Harburg       |     1 |
+| Archäologische Kommission für Niedersachsen                  |     1 |
+| Archivschule Marburg                                         |     1 |
+| Arachnologische Gesellschaft                                 |     1 |
+| Anthropological Society (Munich)                             |     1 |
+| Beethoven House                                              |     1 |
+
+
+Now the other way round: get amount of institutions per consortium.
+
+#+name: inst-count
+#+begin_src awk -n :stdin clean-dataset :var consortium="NFDI4Memory" :results value drawer  :exports code
+BEGIN {
+  FS =  "\t"
+}
+  $2 == consortium { ++counts[$2] }
+END {
+  for (k in counts) print consortium " (" counts[k]  " institutions)"
+}
+#+end_src
+
+#+RESULTS: inst-count
+:results:
+NFDI4Memory (5 institutions)
+:end:
+
+#+RESULTS:
+:results:
+NFDI4Memory (5 institutions)
+:end:
+
+
+So, now we know of many institutions are involved in
+call_inst-count('NFDI4Objects') {{{results(NFDI4Objects (9 institutions))}}}
+or in
+call_inst-count("NFDI4Earth") {{{results(NFDI4Earth (3 institutions))}}}.
+
+
+
+** Network Display with R
+Visualize the connections in R
+
+#+begin_src R -n :var NFDI_edges=clean-dataset :results graphics file :exports both :file network-plot.png
+library("igraph")
+
+NFDI_network <- graph_from_data_frame(NFDI_edges,
+                                      directed = FALSE)
+plot(NFDI_network,
+    main  = "NFDI Network",
+    vertex.size        = 4,
+    vertex.label       = NA,
+    edge.curved        = 0.2,
+    )
+#+end_src
+
+#+RESULTS:
+[[file:network-plot.png]]
+
+
+
+* Preserve
+
+** Manual export
+
+export using =SPC m e l o= --> LaTeX (PDF).
+
+SWITCH to Jonathan.
+
+[[file:nfdi-in-emacs-with-orgmode.org]]
+
+SWITCH to complete version.
+
+QUESTION
+
+
+* Next Steps :noexport:
+
+#+begin_comment
+#+author: Jonathan A. Hartman | Lukas C. Bossert
+#+title: Data processing, Code documenting and Beyond
+#+date: <2023-09-12 Tue>
+#+end_comment
+
+Better LaTeX-Export
+#+begin_comment
+#+LATEX_COMPILER: lualatex
+#+LATEX_CLASS: article
+#+LATEX_HEADER: \usepackage{minimalist}
+#+LATEX_HEADER: \usepackage{fontspec}
+#+LATEX_HEADER: \usepackage{caption} \captionsetup{labelfont=bf,font={sf,small}}
+#+LATEX_HEADER: \setmainfont{TeX Gyre Pagella}
+#+LATEX_HEADER: \AtBeginEnvironment{longtable}{\small\sf}
+
+
+#+ATTR_LaTeX: :environment longtable
+
+#+attr_html: :width 70%
+#+attr_LaTeX: :width .5\linewidth
+#+end_comment
+
+Pandoc
+#+begin_comment
+#+PANDOC_VARIABLES: documentclass:scrartcl
+#+PANDOC_VARIABLES: classoption:10pt
+#+PANDOC_OPTIONS: highlight-style:zenburn
+#+end_comment
+
+
+Better HTML-Export
+#+begin_comment
+
+#+SETUPFILE: https://fniessen.github.io/org-html-themes/org/theme-readtheorg.setup
+#+end_comment
+
+
+Very optional
+#+begin_comment
+#+title:  Data Processing, Code Documentation and Beyond {{{NEWLINE}}} (Emacs and org-mode)
+#+MACRO: NEWLINE @@latex:\\@@ @@html:<br>@@
+#+end_comment
+
+#+print_bibliography: