[[!meta title="Managing a research workflow (bibliographies, note-taking, and arXiv)"]]
[[!meta copyright="Copyright © 2021 Ahmed Khaled"]]
[[!inline pages="internal(2021/info/research-nav)" raw="yes"]]
<!-- You can manually edit this file to update the abstract, add links, etc. --->
# Managing a research workflow (bibliographies, note-taking, and arXiv)
Ahmed Khaled
[[!inline pages="internal(2021/info/research-schedule)" raw="yes"]]
[Configuration I use in Doom Emacs as part of my academic reading/notetaking workflow](https://gist.github.com/rka97/57779810d3664f41b0ed68a855fcab54)
Researchers and knowledge workers have to read and discover new papers,
ask questions about what they read, write notes and scratchwork, and store
much of this information for use in writing papers and/or code. Emacs allows
us to do all of this (and more) using simple text interfaces that integrate
well together. In this talk I will talk about the following:
a. Using elfeed and elfeed-score to read new papers from arXiv.
b. Using org-ref to import arXiv papers of interest into a local
bibliography.
c. Using Emacs hooks with biber and rebiber in order to keep the local
bibliography clean and up-to-date with conference versions of papers.
d. Using org-roam and org-roam-bibtex to take linked, searchable notes in
org on research papers.
This text-based workflow allows for keeping everything accessible under
version
control and avoids the platform lock-in of binary formats (e.g. Mendeley). I
will share my Doom Emacs configuration for this workflow, but it is not
limited
to Doom.
# Discussion
- Are there any good packages for emacs/Lisp libraries that are similar to Matplotlib/Pyplot/Numpy?
- use numpy with org-mode and babel
- plotting is a bleak spot in the lisp space, racket has a built in plot library that is probably the best on that front
- are these helper functions public?
- this talk just gave me an idea, I organize repos inside ~/code/{github.com,gitlab.com,gnu.org,etc}/author@repository-name.git - and I can instead use a single directory and use this strategy for projectile-switch-project where author is one column, repository name is another, git remote is another, etc
# Outline
- 5-10 minutes: I will demo the packages I use in 5 minutes.
<!--
- 20 minutes: I will describe the packages I use in some detail and give a
demo of them.
- 40 minutes: I will describe the packages I use, give a demo of them, and
include a video segment on configuring the packages in Emacs.
-->
[[!inline pages="internal(2021/captions/research)" raw="yes"]]
[[!inline pages="internal(2021/info/research-nav)" raw="yes"]]
