It is incredibly difficult to plan in advance what to collect for any zettelkasten, even when its scope is tightly defined, like it would have been for the Oxford English Dictionary.

https://www.academia.edu/community/VDDN6V

Evina Stein has a nice list of digital manuscript databases

Alternative approach to consider: don't rebuild older posts. Transform them from Markdown into HTML in situ and then never worry about recompiling that post again. You could do this by either keeping both the Markdown source and the output document around, or by crafting the output in such a way that the compilation process is reversible—so you could delete the Markdown source after it's compiled and derive it from the output in the event that you ever wanted to recover it.

But it will always be well to cultivate the mechanical habits of which pro- fessional compilers have learnt the value by experi- ence: to write at the head of evey slip its date,

Here again we see some broad common advice for zettels and note taking methods: - every slip or note should have a date - every slip should have a (topical) heading - indices - cross-references - lists of sources (bibliography)

traditional compilation foils "symmetric authoring"

Readable how? I think the better approach over what we do now, where we run source code through what are essentially compilers for making websites and then treat the output similar to object files—i.e. opaque blobs that are unsuitable for anything other than either (a) executing/experiencing, or (b) publishing to others—would be to pursue non-destructive compilation. So after the Markdown is compiled (if there is any compilation step at all), you don't have to keep the original sources around. The tooling should be sufficiently advanced to work with the publishable form as input, too, and not demand only Markdown. In instances where the Markdown files are kept around because the spartan experience of opening a plain text file where the content is almost entirely unadorned by formatting concerns is the preferred way to get things done, the tooling should be able to derive the original Markdown (or a good enough rendition) from the output itself. HTML is rich enough to be able to encode the necessary structure for this on the first Markdown-to-HTML pass. Systems that implement this kind of thing could be said to support a sort of "reversible Markdown", making the publishable form a suitable source of truth—a treatment that is right now reserved only for the originals that are collected and kept off-site.

Make the writing and editing experience more like Word or Google Docs and less like LaTeX.

(NB: the compilation "object" format here would, much like triple scripts, be another form of human readable source.)

Guarino da Verona when making the unlikely claim that note taking begin in earnest with Francesco Sacchini in the seventeenth century rather than a hundred years earlier with Erasmus and Vives.

I almost feel like I've arrived as I noticed this error in the text myself.

Interesting that he calls her out for making a compilation error, something which is very meta with respect to this particular text.

There is a parallel between these practices and the same sort of practices seen in social media posting, annotating, and bookmarking, however in the digital realm the user interface is so simple that one needn't put very much thought into the process and the results become almost instantaneously meaningless. Was this the case in the medieval context as well, or did the readers/compilers get more out of their practices?

In addition to florilegium, the descriptors liber scintillarum (book of sparks) and pharetra (quiver) in addition to other flower metaphors were also used in the medieval period to describe the genre of books in which the best passages from authoritative sources were compiled.

While there are ancient compilations by writers including Pliny, Diogenes Laertius, and Stobaeus, many authors in the Renaissance credited Aulus Gellius as the founder of the genre.

As it should be. (This should be the default. The NodeJS/NPM's Webpack addiction needs to be curbed—or confronted with a reality check.)

Python-igraph 0.8.3. (2020, October 8). Igraph Support Forum. https://igraph.discourse.group/t/python-igraph-0-8-3/473

Panda, A., Gonawela, A., Acharyya, S., Mishra, D., Mohapatra, M., Chandrasekaran, R., & Pal, J. (2020). NivaDuck—A Scalable Pipeline to Build a Database of Political Twitter Handles for India and the United States. International Conference on Social Media and Society, 200–209. https://doi.org/10.1145/3400806.3400830

Uribe-Tirado, A., del Rio, G., Raiher, S., & Ochoa Gutiérrez, J. (2020). Open Science since Covid-19: Open Access + Open Data [Preprint]. SocArXiv. https://doi.org/10.31235/osf.io/a5nqw

VA: Sing meinen Song – Das Tauschkonzert Vol. 4

VÖ: 9.6.2017

Charts seit 16.6.2017