path: root/2020/subtitles/emacsconf-2020--17-org-mode-and-org-roam-for-scholars-and-researchers--noorah-alhasan.vtt

WEBVTT

00:00:00.320 --> 00:00:02.639
Good afternoon or good evening, everyone.

00:00:03.040 --> 00:00:05.440
Today, my talk is going to be on Org Mode

00:00:05.440 --> 00:00:07.759
and org-roam for scholars and researchers.

00:00:07.759 --> 00:00:10.559
Leo has talked about the overall

00:00:10.559 --> 00:00:12.639
picture of org-roam and

00:00:12.639 --> 00:00:15.120
org-roam-bibtex. I will be

00:00:15.120 --> 00:00:16.240
talking more about

00:00:16.240 --> 00:00:20.320
the research process itself using these
tools.

00:00:20.320 --> 00:00:22.400
All right. So, just to introduce that the

00:00:22.400 --> 00:00:25.039
research process is really messy.

00:00:25.039 --> 00:00:28.080
You're always working in

00:00:28.080 --> 00:00:31.039
piecemeal tasks and things move around

00:00:31.039 --> 00:00:32.960
all the time.

00:00:32.960 --> 00:00:35.280
There needs to be a system where you can

00:00:35.280 --> 00:00:36.880
organize all these tasks,

00:00:36.880 --> 00:00:39.360
all these ideas in a way that is

00:00:39.360 --> 00:00:41.760
flexible and effective.

00:00:41.760 --> 00:00:44.767
So my motivation is that research is
hard

00:00:44.767 --> 00:00:47.120
and writing about it is even
more difficult.

00:00:47.120 --> 00:00:49.600
My goal is to add some structure to

00:00:49.600 --> 00:00:51.120
this whole madness.

00:00:51.120 --> 00:00:52.800
Here's a list of some of the stuff

00:00:52.800 --> 00:00:54.480
that I've been using since I first

00:00:54.480 --> 00:00:57.199
learned about Emacs in 2019

00:00:57.199 --> 00:01:00.160
and what I've found useful

00:01:02.000 --> 00:01:05.199
within my research process.

00:01:05.199 --> 00:01:07.920
I've organized Org Mode for Researchers

00:01:07.920 --> 00:01:10.400
and Scholars Within the Writing Process

00:01:10.400 --> 00:01:12.400
into three modules. First, there's

00:01:12.400 --> 00:01:14.320
the planning aspect of it,

00:01:14.320 --> 00:01:15.759
then you've got the writing and the

00:01:15.759 --> 00:01:18.320
reference management, which I will join
together

00:01:18.320 --> 00:01:20.560
by looking at the example of doing your

00:01:20.560 --> 00:01:21.920
literature review.

00:01:21.920 --> 00:01:25.467
When we're talking about planning,

00:01:25.467 --> 00:01:27.360
we're talking about either task
management or

00:01:27.360 --> 00:01:30.880
time management with task management.

00:01:30.880 --> 00:01:31.600
You've got

00:01:31.600 --> 00:01:33.840
Org Mode's TODOs, tags, and

00:01:33.840 --> 00:01:36.159
categories. These are really powerful

00:01:36.159 --> 00:01:38.479
tools that you could use

00:01:38.479 --> 00:01:41.600
in your Org files to

00:01:41.600 --> 00:01:44.799
organize your tasks and

00:01:44.799 --> 00:01:47.040
your appointments. There are different

00:01:47.040 --> 00:01:49.040
types of TODOs that you can either set

00:01:49.040 --> 00:01:50.960
globally in your init file or they can

00:01:50.960 --> 00:01:52.799
be file-/buffer-specific.

00:01:52.799 --> 00:01:54.867
That means, based on context,

00:01:54.867 --> 00:01:57.759
based on the type of manuscript you're
working on, whether

00:01:57.759 --> 00:02:00.033
it's a literate programming report

00:02:00.033 --> 00:02:03.759
or your actual thesis/dissertation.

00:02:03.759 --> 00:02:05.840
Also, these TODOs are either created

00:02:05.840 --> 00:02:07.759
as a subtree, like think of them as

00:02:07.759 --> 00:02:11.440
headings and sections if you use LaTeX,

00:02:11.440 --> 00:02:15.233
or inline tasks, which are like Org
inline tasks.

00:02:19.120 --> 00:02:17.760
I like Org inline tasks
because I can add

00:02:19.120 --> 00:02:21.520
TODOs between two paragraphs. That

00:02:21.520 --> 00:02:22.879
way, it doesn't show up

00:02:22.879 --> 00:02:25.360
in the table of contents when I export

00:02:25.360 --> 00:02:27.280
into PDF, HTML, or

00:02:27.280 --> 00:02:30.879
anything else. So this is an

00:02:30.879 --> 00:02:34.319
example of buffer-specific TODOs,

00:02:34.319 --> 00:02:37.360
and this is an example of a little

00:02:37.360 --> 00:02:39.120
programming report that I was working on

00:02:39.120 --> 00:02:40.800
where I was dealing with

00:02:40.800 --> 00:02:44.080
data and analysis and all of that
stuff.

00:02:44.080 --> 00:02:47.519
I needed context-specific TODOs to

00:02:47.519 --> 00:02:49.440
use them within this buffer.

00:02:49.440 --> 00:02:52.080
That's how I would organize it.

00:02:52.080 --> 00:02:54.319
There's also another example

00:02:54.319 --> 00:02:57.200
of an Org inline task where you could

00:02:57.200 --> 00:03:01.360
see it in the middle between the
two headings.

00:03:01.360 --> 00:03:03.040
That way, it wouldn't show up in the

00:03:03.040 --> 00:03:04.959
table of contents, and it would look

00:03:04.959 --> 00:03:06.480
neater within the

00:03:06.480 --> 00:03:09.519
text when you export it.

00:03:09.519 --> 00:03:11.920
I also added a tag of :noexport:

00:03:11.920 --> 00:03:13.280
so it won't show up at all

00:03:13.280 --> 00:03:16.400
when I export it into either PDF,

00:03:16.400 --> 00:03:19.360
which I use all the time.

00:03:19.360 --> 00:03:21.599
Another useful tool

00:03:21.599 --> 00:03:24.159
for the research and just

00:03:24.159 --> 00:03:25.200
general planning

00:03:25.200 --> 00:03:27.920
is the org-capture. When I first

00:03:27.920 --> 00:03:29.120
started with Emacs,

00:03:29.120 --> 00:03:32.080
actually, it was for org-agenda.

00:03:32.080 --> 00:03:34.239
I went crazy with my capture template.

00:03:34.239 --> 00:03:35.360
I created a template for

00:03:35.360 --> 00:03:38.640
everything because I was just so
excited.

00:03:38.640 --> 00:03:40.720
But with time, I was using less and less

00:03:40.720 --> 00:03:42.400
of them, so I kept taking them out.

00:03:42.400 --> 00:03:46.319
Now this is my simplified

00:03:46.319 --> 00:03:48.239
capture templates that I use, either for

00:03:48.239 --> 00:03:49.599
a general TODO,

00:03:49.599 --> 00:03:52.159
for a regular appointment, a fleeting

00:03:52.159 --> 00:03:54.159
note, research tasks (because those

00:03:54.159 --> 00:03:55.200
are what I focus on,

00:03:55.200 --> 00:03:56.959
like my bread and butter), and then

00:03:56.959 --> 00:03:58.720
finally with meetings, which I find

00:03:58.720 --> 00:04:00.879
sometimes I don't use it as much because

00:04:00.879 --> 00:04:03.519
I would just have the Org file ready
instead of

00:04:03.519 --> 00:04:04.879
needing to capture,

00:04:04.879 --> 00:04:07.920
you know, open a capture template.

00:04:07.920 --> 00:04:12.400
Right. Org Agenda. That's how I got into
Emacs.

00:04:12.400 --> 00:04:15.439
I needed to organize my life.

00:04:15.439 --> 00:04:19.199
I found Emacs and it's been great
ever since.

00:04:19.199 --> 00:04:20.479
It populates all your TODOs and

00:04:20.479 --> 00:04:22.720
appointments into a singular view. So the

00:04:22.720 --> 00:04:25.280
default view, I think, is a week view.

00:04:25.280 --> 00:04:29.120
However, I use org-super-agenda. Love this

00:04:29.120 --> 00:04:31.919
package. I set up my agenda as a

00:04:31.919 --> 00:04:34.160
daily view with appointments,

00:04:34.160 --> 00:04:37.360
deadlines, and a habit tracker.

00:04:37.360 --> 00:04:38.720
A side note, you guys: I'm still

00:04:38.720 --> 00:04:40.639
struggling with organizing the perfect

00:04:40.639 --> 00:04:42.320
agenda, so it's a process.

00:04:42.320 --> 00:04:45.360
Take it easy, all right?

00:04:45.360 --> 00:04:47.919
So this is just an overview of my daily

00:04:47.919 --> 00:04:50.320
agenda. As you can see they're just

00:04:50.320 --> 00:04:55.520
appointments that I import from Gmail
using org-gcal;

00:04:55.520 --> 00:04:57.919
a simple habit tracker of daily

00:04:57.919 --> 00:04:58.880
free writing--

00:04:58.880 --> 00:05:00.960
as you can see, there are a lot of times

00:05:00.960 --> 00:05:02.800
where I'm skipping, and the asterisk is

00:05:02.800 --> 00:05:05.199
the one where I've completed that day,

00:05:05.199 --> 00:05:08.479
so, you know, it's a process--and then

00:05:08.479 --> 00:05:10.080
regular deadlines.

00:05:10.080 --> 00:05:12.639
So what happens is that I have other

00:05:12.639 --> 00:05:17.120
TODOs that I have not scheduled or not
added a deadline

00:05:17.120 --> 00:05:19.933
but they're just tasks that keep piling
up.

00:05:19.933 --> 00:05:22.320
When I first started with Emacs
and org-agenda,

00:05:22.320 --> 00:05:24.880
I had everything in there, and it got

00:05:24.880 --> 00:05:26.880
overwhelming. Then I decided, no,

00:05:26.880 --> 00:05:29.680
I'm not gonna even let them show up.

00:05:29.680 --> 00:05:30.800
So what I would do

00:05:30.800 --> 00:05:33.120
at the beginning of each week or the

00:05:33.120 --> 00:05:34.479
night before,

00:05:34.479 --> 00:05:36.800
I would sit down, look at all my

00:05:36.800 --> 00:05:40.720
TODOs that I have not assigned yet to a
deadline or a

00:05:40.720 --> 00:05:42.639
schedule or just a simple

00:05:42.639 --> 00:05:45.360
timestamp, and I would organize them

00:05:45.360 --> 00:05:46.320
throughout the week.

00:05:46.320 --> 00:05:49.520
So, here's an example of what I did.

00:05:49.520 --> 00:05:51.680
On that Wednesday, from my Gmail, I had

00:05:51.680 --> 00:05:53.039
all these appointments, but

00:05:53.039 --> 00:05:56.560
one of them is I have a writing group
session.

00:05:56.560 --> 00:05:58.400
So I looked at my tasks and I

00:05:58.400 --> 00:05:59.759
thought, okay, then I will just

00:05:59.759 --> 00:06:03.520
assign, for example, my Emacs
slides

00:06:03.520 --> 00:06:06.319
or the framework diagram into that

00:06:06.319 --> 00:06:07.280
writing session.

00:06:07.280 --> 00:06:10.800
All I did was just add an active
timestamp.

00:06:10.800 --> 00:06:12.960
That is all I needed to do, and it went

00:06:12.960 --> 00:06:14.000
straight into my

00:06:14.000 --> 00:06:17.120
appointment. Now, if I miss that,

00:06:17.120 --> 00:06:20.080
it won't show up on the next day. So if

00:06:20.080 --> 00:06:21.520
you put in a deadline,

00:06:21.520 --> 00:06:24.639
it will show up as an overdue, but if you

00:06:24.639 --> 00:06:26.560
have no deadline or schedule, it will not

00:06:26.560 --> 00:06:29.280
show up in your daily org agenda.

00:06:29.280 --> 00:06:32.960
So, just a star.

00:06:32.960 --> 00:06:35.680
All right. Another way of accessing your

00:06:35.680 --> 00:06:37.520
TODOs is that if it's

00:06:37.520 --> 00:06:40.880
Org file-specific,

00:06:40.880 --> 00:06:42.160
buffer-specific,

00:06:42.160 --> 00:06:44.160
and so... Like when we talked about like

00:06:44.160 --> 00:06:46.400
whether to have a big-ass Org file or

00:06:46.400 --> 00:06:47.680
like tiny files,

00:06:47.680 --> 00:06:50.720
it all depends. This isn't the...

00:06:50.720 --> 00:06:54.560
you know, the way this depends,

00:06:54.560 --> 00:06:55.759
because if you're working on a

00:06:55.759 --> 00:06:58.400
dissertation, it's a huge manuscript.

00:06:58.400 --> 00:06:59.680
You need to work

00:06:59.680 --> 00:07:02.880
on that Org file all the time.

00:07:02.880 --> 00:07:05.759
Then yes, my TODOs should be in that

00:07:05.759 --> 00:07:07.680
file specifically, because every time,

00:07:08.000 --> 00:07:09.680
if I'm visiting this Org file all the

00:07:09.680 --> 00:07:12.479
time, I should be able to just look at my

00:07:12.479 --> 00:07:15.520
tasks from within that buffer.

00:07:15.520 --> 00:07:18.639
And so I use org-sidebar to

00:07:18.639 --> 00:07:21.599
keep all these specific TODOs

00:07:21.599 --> 00:07:22.960
within that Org file.

00:07:22.960 --> 00:07:26.560
I find it helpful. Okay.

00:07:26.560 --> 00:07:28.400
Now that we're going into the writing

00:07:28.400 --> 00:07:29.759
and reference management...

00:07:29.759 --> 00:07:33.039
We'll call it a literature review.

00:07:33.039 --> 00:07:36.639
This is something I've built as a
schema.

00:07:36.639 --> 00:07:40.240
I think that it works for now.

00:07:40.240 --> 00:07:45.919
It requires one outside software, which
is Zotero, what

00:07:45.919 --> 00:07:47.680
I use. It's an open source reference

00:07:47.680 --> 00:07:51.759
management software. It's great.

00:07:51.759 --> 00:07:53.599
But the thing to keep in mind is that I

00:07:53.599 --> 00:07:58.319
use two plugins that are really needed
for when

00:07:58.319 --> 00:08:01.039
we work with org-roam-bibtex, org-roam,

00:08:01.039 --> 00:08:03.840
Org Mode, and the ZotFile.

00:08:03.840 --> 00:08:07.039
Better BibTeX organizes your
reference keys

00:08:07.039 --> 00:08:10.560
in a way, in a fashion that

00:08:10.560 --> 00:08:13.360
works for you. For me, all my reference

00:08:13.360 --> 00:08:17.280
keys are last author and year.
With ZotFile,

00:08:17.280 --> 00:08:21.120
I let it rename all the

00:08:21.120 --> 00:08:22.319
PDF files

00:08:22.319 --> 00:08:24.400
the same way that I have for

00:08:24.400 --> 00:08:26.000
my Bib keys, which is

00:08:26.000 --> 00:08:29.360
last name of author and year. All right.

00:08:29.360 --> 00:08:33.440
Once you export your entire

00:08:33.440 --> 00:08:37.120
library as a Bib file, then you can work

00:08:37.120 --> 00:08:39.440
on it within Org Mode and Emacs

00:08:39.440 --> 00:08:42.880
using the following packages.

00:08:42.880 --> 00:08:45.040
So with org-roam-bibtex, it

00:08:45.040 --> 00:08:47.839
creates an Org file for each Bib entry.

00:08:47.839 --> 00:08:49.519
You have the option of

00:08:49.519 --> 00:08:52.240
templating and doing other stuff with it.

00:08:52.240 --> 00:08:54.880
Then finally, there's this

00:08:54.880 --> 00:08:56.240
orb-pdf-scrapper.

00:08:56.240 --> 00:09:00.240
I've used it briefly but I think the
potential

00:09:00.240 --> 00:09:02.880
with orb-pdf-scrapper is if you're going to

00:09:02.880 --> 00:09:05.920
do a bibliometric study or

00:09:05.920 --> 00:09:08.320
a systematic literature review, there's

00:09:08.320 --> 00:09:10.000
something there, but I have to look

00:09:10.000 --> 00:09:10.959
through it.

00:09:10.959 --> 00:09:14.399
Anyway, so once you create

00:09:14.399 --> 00:09:16.880
your reference file of reference X and

00:09:16.880 --> 00:09:18.160
you're writing your notes,

00:09:18.160 --> 00:09:20.240
you can either go... Like, with going

00:09:20.240 --> 00:09:22.399
through Org Mode, you're writing

00:09:22.399 --> 00:09:24.080
your ideas, you're writing your notes,

00:09:24.080 --> 00:09:26.080
you're assigning tasks,

00:09:26.080 --> 00:09:27.839
and then there's org-transclusion, which

00:09:27.839 --> 00:09:30.480
I will mention briefly at the end,

00:09:30.480 --> 00:09:32.240
and ways to extract. If you're going to

00:09:32.240 --> 00:09:35.360
go through the org-roam...

00:09:35.360 --> 00:09:36.640
Things that you're going to use within

00:09:36.640 --> 00:09:38.720
org-roam... It's a great way to build your

00:09:38.720 --> 00:09:40.000
database. You start making the

00:09:40.000 --> 00:09:42.880
connections. You can visualize your

00:09:42.880 --> 00:09:44.959
notes and how these references are

00:09:44.959 --> 00:09:46.240
linked to each other

00:09:46.240 --> 00:09:48.839
through the org-roam server or

00:09:48.839 --> 00:09:50.240
org-roam graph.

00:09:50.240 --> 00:09:53.120
All right. This is just notes for later.

00:09:53.680 --> 00:09:56.240
So this is an example of an org-roam

00:09:56.240 --> 00:09:57.360
file that I have.

00:09:57.360 --> 00:09:59.279
For example, if I'm working on adaptation

00:09:59.279 --> 00:10:01.760
policy, I have these hyperlinks that are

00:10:01.760 --> 00:10:04.959
linked to other concepts and ideas such
as either

00:10:04.959 --> 00:10:06.640
climate security,

00:10:06.640 --> 00:10:08.720
changing global environment, so on and

00:10:08.720 --> 00:10:10.560
so forth. The backlinks

00:10:10.560 --> 00:10:13.920
are other references that talk about

00:10:13.920 --> 00:10:15.839
this specific concept.

00:10:15.839 --> 00:10:17.680
This is really helpful. Then, when

00:10:17.680 --> 00:10:19.920
you visualize it, the picture on the left

00:10:19.920 --> 00:10:22.160
(which I'm sure looks really small),

00:10:22.160 --> 00:10:24.160
you can see the connections that it's

00:10:24.160 --> 00:10:25.680
making with other

00:10:25.680 --> 00:10:28.160
references. Of course, this is just

00:10:28.160 --> 00:10:32.720
like a buffer network. When you look at
the entire

00:10:32.720 --> 00:10:34.560
database network...

00:10:34.560 --> 00:10:38.000
It's growing. Okay.

00:10:38.000 --> 00:10:41.680
So going into org-roam-bibtex...

00:10:41.680 --> 00:10:44.079
It utilizes a combination of the

00:10:44.079 --> 00:10:46.000
org-ref package, helm-bibtex,

00:10:46.000 --> 00:10:46.880
bibtex-completion.

00:10:46.880 --> 00:10:50.079
It works with org-roam functionalities

00:10:50.079 --> 00:10:54.880
and other good stuff. This is an example

00:10:54.880 --> 00:10:57.440
of my org-roam-bibtex file. All right. So

00:10:57.440 --> 00:11:01.200
I've created the template which I
pretty much use,

00:11:01.200 --> 00:11:05.920
what Leo has produced in his

00:11:05.920 --> 00:11:08.640
tutorial. I think it's great. It

00:11:08.640 --> 00:11:10.160
works well for me.

00:11:10.160 --> 00:11:12.880
What it does is that it works

00:11:12.880 --> 00:11:14.480
with your bib file.

00:11:14.480 --> 00:11:17.519
So if you're in your bib file, you have a

00:11:17.519 --> 00:11:19.519
sub entry that's called keywords, and

00:11:19.519 --> 00:11:21.040
usually that's within

00:11:21.040 --> 00:11:23.120
a journal article. The author would

00:11:23.120 --> 00:11:27.519
specify these keywords. When it gets
imported into

00:11:27.519 --> 00:11:30.399
Zotero, it extracts those keywords and
then it

00:11:30.399 --> 00:11:32.399
gets populated as an Org file

00:11:32.399 --> 00:11:34.959
with org-roam-bibtex. I always start

00:11:34.959 --> 00:11:36.959
with the meta information first, and then

00:11:36.959 --> 00:11:38.560
I would write my notes

00:11:38.560 --> 00:11:42.480
after that. This is an example, though,

00:11:42.480 --> 00:11:45.760
for reference of a physical book, so

00:11:45.760 --> 00:11:49.120
I don't have a pdf file for it.

00:11:49.120 --> 00:11:51.519
So when I've figured out a new idea

00:11:51.519 --> 00:11:53.920
for it, if I'm writing notes on it,

00:11:53.920 --> 00:11:57.279
I would create a property that says
pages.

00:11:57.279 --> 00:11:58.959
That way, it's easier for you when you go

00:11:58.959 --> 00:12:00.639
back to citing

00:12:00.639 --> 00:12:02.720
certain ideas or something, that you

00:12:02.720 --> 00:12:04.720
have the pages prepared there.

00:12:04.720 --> 00:12:07.839
It's easier that way. Okay.

00:12:07.839 --> 00:12:11.279
org-noter which is something I

00:12:11.279 --> 00:12:13.040
use a lot, especially with journal

00:12:13.040 --> 00:12:15.600
articles that have PDFs and stuff like
that.

00:12:15.600 --> 00:12:19.120
They're really helpful if you are going to...

00:12:19.120 --> 00:12:22.720
If you've just started using Emacs

00:12:22.720 --> 00:12:23.760
and org-roam,

00:12:23.760 --> 00:12:26.959
and you have all these PDFs that have

00:12:26.959 --> 00:12:29.519
all the annotations and highlighting and

00:12:29.519 --> 00:12:32.639
all that stuff, with org-noter you can

00:12:32.639 --> 00:12:36.720
just use the org-noter-create-skeleton

00:12:36.720 --> 00:12:39.519
command and it will populate all your

00:12:39.519 --> 00:12:41.200
notes that have already been

00:12:41.200 --> 00:12:43.760
entered within the PDF file if you're

00:12:43.760 --> 00:12:48.160
using an outside software, and creates
them as a neat

00:12:48.160 --> 00:12:52.560
Org file. I highly recommend.

00:12:52.560 --> 00:12:55.920
Finally, org-transclusion.

00:12:55.920 --> 00:12:57.920
I think this is still in its beta phase,

00:12:57.920 --> 00:13:01.040
but I've been enjoying it so far.

00:13:01.040 --> 00:13:02.720
I'm guessing people know what

00:13:02.720 --> 00:13:04.800
transclusion means, which is like

00:13:04.800 --> 00:13:06.480
copy-pasting text from

00:13:06.480 --> 00:13:09.600
one Org file to another. This is helpful.

00:13:09.600 --> 00:13:11.839
I think I peeked at a question that

00:13:11.839 --> 00:13:12.959
was talking about

00:13:12.959 --> 00:13:16.320
linking to other Org files.

00:13:16.320 --> 00:13:20.320
I think org-transclusion could really
work. It's

00:13:20.320 --> 00:13:24.399
equivalent to the include

00:13:24.399 --> 00:13:27.760
function within Org Mode, but I think...

00:13:27.760 --> 00:13:29.519
So if you have other files

00:13:29.519 --> 00:13:32.560
that you know which region that you

00:13:32.560 --> 00:13:34.800
need in another file, you could use the

00:13:34.800 --> 00:13:36.079
#+INCLUDE, but with

00:13:36.079 --> 00:13:38.160
org-transclusion... It's great. I mean you

00:13:38.160 --> 00:13:39.440
just have...

00:13:39.440 --> 00:13:43.360
you're just linking one part to the
other.

00:13:43.360 --> 00:13:45.760
Sort of... Like, not refiling, but you know

00:13:45.760 --> 00:13:47.760
hyperlinking.

00:13:47.760 --> 00:13:49.680
So this is an example of what

00:13:49.680 --> 00:13:51.120
org-transclusion looks like.

00:13:51.120 --> 00:13:53.680
The highlighted problem statement

00:13:53.680 --> 00:13:54.720
is from another

00:13:54.720 --> 00:13:57.760
Org file. Then what I would do is

00:13:57.760 --> 00:13:59.760
just link it to there, and there was a

00:13:59.760 --> 00:14:01.440
transclusion command.

00:14:01.440 --> 00:14:05.440
I wish I made another screenshot of it.

00:14:05.440 --> 00:14:09.120
When you invoke org-transclusion-mode,

00:14:09.120 --> 00:14:12.079
it turns... It prints it out like that.

00:14:12.480 --> 00:14:15.120
It's in view mode. Then when you want

00:14:15.120 --> 00:14:16.560
to edit, it will take you back to that

00:14:16.560 --> 00:14:18.480
buffer and you can edit the text

00:14:18.480 --> 00:14:22.720
however you want. All right. So, thank
you so much.

00:14:22.720 --> 00:14:26.000
I wanted to leave room for questions,

00:14:26.000 --> 00:14:29.120
but special thanks to all the folks that

00:14:29.120 --> 00:14:33.440
work on org-roam, org-roam-bibtex,
org-roam-server,

00:14:33.440 --> 00:14:36.320
org-transclusion, and of course alphapapa on

00:14:36.320 --> 00:14:38.240
org-super-agenda and org-sidebar.

00:14:38.240 --> 00:14:43.440
That's how I got into Emacs. Thank you.

00:14:43.440 --> 00:14:45.600
(Leo: All right. Well, thank you. So yeah,

00:14:45.600 --> 00:14:47.120
this time I'll be the one asking the

00:14:47.120 --> 00:14:49.120
question and not Amin.

00:14:49.120 --> 00:14:51.360
I'm filling big shoes right now,

00:14:51.360 --> 00:14:53.120
so you'll have to bear with me folks.

00:14:53.120 --> 00:14:54.880
So thank you so much, Noorah, for your

00:14:54.880 --> 00:14:56.240
presentation that is incredibly

00:14:56.240 --> 00:14:57.279
interesting.

00:14:57.279 --> 00:14:58.959
Would you mind if I fed you questions

00:14:58.959 --> 00:15:00.800
from the charts?)

00:15:00.800 --> 00:15:04.000
Noorah: Go ahead. (Leo: Okay. so the first one I've

00:15:04.000 --> 00:15:06.160
picked on my end was "Did you try using

00:15:06.160 --> 00:15:07.920
ebib instead of Zotero,

00:15:07.920 --> 00:15:10.560
and if so, is it better than Zotero in

00:15:10.560 --> 00:15:12.079
some ways?)

00:15:12.079 --> 00:15:14.880
Noorah: No, I have not used Ebib. I've only used

00:15:14.880 --> 00:15:15.680
Mendeley

00:15:15.680 --> 00:15:18.560
and then they got bought by Elsevier,

00:15:18.560 --> 00:15:20.320
and so I was, like, okay I'm done,

00:15:20.320 --> 00:15:23.040
I'm going to Zotero. There are a lot

00:15:23.040 --> 00:15:25.120
of plugins with Zotero that you can play

00:15:25.120 --> 00:15:26.240
around with.

00:15:26.240 --> 00:15:28.320
I can't speak for Ebib, but definitely

00:15:28.320 --> 00:15:32.079
Zotero has been a good experience so
far.

00:15:32.079 --> 00:15:34.880
(Leo: Yes, same. I also do research on

00:15:34.880 --> 00:15:35.360
the side;

00:15:35.360 --> 00:15:38.079
as I told you, English major, and yeah I

00:15:38.079 --> 00:15:39.360
also do Zotero.

00:15:39.360 --> 00:15:41.839
Some people have been using uh a

00:15:41.839 --> 00:15:43.759
connector between Zotero and Emacs which

00:15:43.759 --> 00:15:46.000
has... they've had great success with
them but

00:15:46.000 --> 00:15:47.360
personally I haven't

00:15:47.360 --> 00:15:50.480
touched it already, so yeah.

00:15:50.480 --> 00:15:52.240
Oh, go ahead. Sorry.) Noorah: All right. So far, I

00:15:52.240 --> 00:15:53.920
don't have any problems with Zotero, but

00:15:53.920 --> 00:15:56.320
maybe if I run into something, I might
check out

00:15:56.320 --> 00:15:58.320
Ebib in the future.

00:15:58.320 --> 00:16:00.240
(Leo: yeah, definitely. I think zotero is a very

00:16:00.240 --> 00:16:01.680
solid project. You know, the fact that

00:16:01.680 --> 00:16:02.560
it's being used

00:16:02.560 --> 00:16:04.959
by people outside of Emacs also ensures

00:16:04.959 --> 00:16:06.560
that there's quite a lot of backing

00:16:06.560 --> 00:16:07.680
behind the software,

00:16:07.680 --> 00:16:09.759
which is reassuring when your livelihood

00:16:09.759 --> 00:16:11.759
depends on your research.)

00:16:11.759 --> 00:16:13.519
Noorah: Right. And then I think one more thing

00:16:13.519 --> 00:16:15.600
with Zotero is that you can create

00:16:15.600 --> 00:16:18.079
groups, so if you're in a collaborative
project,

00:16:18.079 --> 00:16:20.160
you can create a reference,

00:16:20.160 --> 00:16:22.320
a library just for your group, and I think

00:16:22.320 --> 00:16:23.759
that could help.

00:16:23.759 --> 00:16:25.279
I'm going to be in a project next

00:16:25.279 --> 00:16:27.600
semester that requires that.

00:16:27.600 --> 00:16:29.839
(Leo: Yeah, definitely. I believe the ability to

00:16:29.839 --> 00:16:31.600
have folders inside Zotero

00:16:31.600 --> 00:16:33.839
makes it incredibly useful to manage

00:16:33.839 --> 00:16:37.440
your different projects, concurrent
projects.

00:16:37.440 --> 00:16:39.279
So moving on to other questions, do you

00:16:39.279 --> 00:16:41.279
have any suggestion on what subjects or

00:16:41.279 --> 00:16:43.440
things should be tags or separate org-roam

00:16:43.440 --> 00:16:46.560
files for cross-linking?)

00:16:46.560 --> 00:16:50.320
Right. So far, now, I'm having

00:16:50.320 --> 00:16:52.720
trouble with "should I be combining

00:16:52.720 --> 00:16:55.360
certain concepts together as one?"

00:16:55.360 --> 00:16:59.360
This is where the thought process

00:16:59.360 --> 00:17:00.959
starts coming to fruit, is that when you

00:17:00.959 --> 00:17:04.880
start combining ideas together so you
won't need a

00:17:04.880 --> 00:17:06.480
specific tag

00:17:06.480 --> 00:17:09.199
and another one that are like similar in

00:17:09.199 --> 00:17:11.280
ideas...

00:17:11.280 --> 00:17:12.720
I'm not sure if that answers the

00:17:12.720 --> 00:17:14.799
question, but so far I've been using

00:17:14.799 --> 00:17:17.919
the org-roam the default way,
which is

00:17:17.919 --> 00:17:22.160
many small files and then just

00:17:22.160 --> 00:17:24.400
linking them to my... Like, either if I have

00:17:24.400 --> 00:17:26.319
a report to write, or if I have an

00:17:26.959 --> 00:17:32.240
essay to write...

00:17:32.240 --> 00:17:35.360
I think you're muted.

00:17:35.360 --> 00:17:38.400
(Leo: I did two stupid things. The
first one

00:17:38.400 --> 00:17:40.640
was spilling out my water. The second one

00:17:40.640 --> 00:17:42.320
was speaking without actually turning on

00:17:42.320 --> 00:17:43.760
my microphone.

00:17:43.760 --> 00:17:45.760
Let's just hope that nothing is going

00:17:45.760 --> 00:17:48.320
to fry in the near vicinity of me right
now.

00:17:48.320 --> 00:17:49.840
But yeah, I believe you've answered

00:17:49.840 --> 00:17:51.440
the question, so don't worry about it. I'm

00:17:51.440 --> 00:17:53.200
slightly wet right now, which is not a

00:17:53.200 --> 00:17:55.280
very agreeable feeling, but we'll have to

00:17:55.280 --> 00:17:57.280
carry on, I suppose.

00:17:57.280 --> 00:17:59.360
Another question: "is there a place where

00:17:59.360 --> 00:18:01.600
people are collaborating on research

00:18:01.600 --> 00:18:04.320
about Emacs?" So do you want to try to

00:18:04.320 --> 00:18:06.160
take this one?)

00:18:06.160 --> 00:18:08.559
Noorah: I don't know, but I'm definitely

00:18:08.559 --> 00:18:10.559
interested in the user experience of

00:18:10.559 --> 00:18:14.720
Emacs, so if anyone wants to work on
that,

00:18:14.720 --> 00:18:16.400
I'm happy.

00:18:16.400 --> 00:18:18.320
(Leo: Well you do have a a pretty good

00:18:18.320 --> 00:18:19.760
candidate in front of you, if I

00:18:19.760 --> 00:18:22.080
should say so myself. I'm incredibly

00:18:22.080 --> 00:18:22.960
interested about

00:18:22.960 --> 00:18:25.039
the ability to do research in Emacs

00:18:25.039 --> 00:18:26.960
and about the ability to

00:18:26.960 --> 00:18:30.480
preach the FLOSS way

00:18:30.480 --> 00:18:32.480
to academia and to the academe,

00:18:32.480 --> 00:18:34.080
especially because I believe there's

00:18:34.080 --> 00:18:35.280
really something

00:18:35.280 --> 00:18:38.240
great to be done. Sorry, I'm just looking

00:18:38.240 --> 00:18:39.919
at the puddle of water on the side which

00:18:39.919 --> 00:18:41.840
is slightly oozing my way,

00:18:41.840 --> 00:18:45.039
which is not a very good feeling, really.

00:18:45.039 --> 00:18:46.880
I believe some work

00:18:46.880 --> 00:18:48.320
could be done, and if people are

00:18:48.320 --> 00:18:50.000
interested in the chat right now,

00:18:50.000 --> 00:18:52.320
do get in touch with us. Both

00:18:52.320 --> 00:18:57.280
Noorah and I are on our Slack channel.
Yes, I know, Slack,

00:18:57.280 --> 00:19:00.080
the corporate hive mind that is Slack.

00:19:00.080 --> 00:19:02.720
But we've decided with org-roam to use
Slack.

00:19:02.720 --> 00:19:05.520
You can find us very easily.

00:19:05.520 --> 00:19:06.880
If you want to talk about these topics,

00:19:07.360 --> 00:19:08.720
by all means, do, and we'll be very

00:19:08.720 --> 00:19:10.720
interested to answer your questions.)

00:19:10.720 --> 00:19:12.640
Noorah: I have a question here that says, "How

00:19:12.640 --> 00:19:15.520
does the view for time blocking works?"

00:19:15.520 --> 00:19:18.640
I use org-super-agenda, so

00:19:18.640 --> 00:19:22.000
what happens is that my active

00:19:22.000 --> 00:19:26.960
timestamps are only in my Gmail
Org file.

00:19:26.960 --> 00:19:29.200
If you use org-gcal, you have to

00:19:29.200 --> 00:19:32.559
specify a certain Org file. When it

00:19:32.559 --> 00:19:34.320
imports them, it imports them as

00:19:34.320 --> 00:19:38.200
active timestamps. I make sure

00:19:38.200 --> 00:19:40.480
whenever I create a TODO or even a
research task

00:19:40.480 --> 00:19:42.480
that it doesn't have a timestamp on it,

00:19:42.480 --> 00:19:45.039
because what I want to do is go back

00:19:45.039 --> 00:19:48.480
and then move around these tasks

00:19:48.480 --> 00:19:50.160
according to my either weekly

00:19:50.160 --> 00:19:51.919
schedule, or monthly, or however long you

00:19:51.919 --> 00:19:52.960
want to do it.

00:19:52.960 --> 00:19:56.480
So yeah, only active timestamps or

00:19:56.480 --> 00:19:59.679
deadline um appear in your time grid.

00:19:59.679 --> 00:20:03.280
So that could work. (Leo: That's very good.

00:20:03.280 --> 00:20:05.440
Just to interject for a second

00:20:05.440 --> 00:20:06.320
about this,

00:20:06.320 --> 00:20:07.840
you know with org-roam right now, we're

00:20:07.840 --> 00:20:10.720
mostly focused on optimization,

00:20:10.720 --> 00:20:13.039
but we're hoping to move on to UX very

00:20:13.039 --> 00:20:14.720
soon. So all those matters about

00:20:14.720 --> 00:20:16.720
having TODOs in your files, it

00:20:16.720 --> 00:20:18.159
is something that we've been thinking

00:20:18.159 --> 00:20:20.000
about with Jethro Kuan, who is my main

00:20:20.000 --> 00:20:23.280
co-maintainer for org-roam. We'll be
working on this in

00:20:23.280 --> 00:20:24.480
the coming months, so don't worry too

00:20:24.480 --> 00:20:26.080
much about it and stay tuned.)

00:20:26.080 --> 00:20:29.760
Noorah: Yeah. So I've got the ebib

00:20:29.760 --> 00:20:33.200
and what else... What subjects... I think...

00:20:33.200 --> 00:20:34.080
Okay!

00:20:34.080 --> 00:20:35.919
What is this question? "Have you seen the

00:20:35.919 --> 00:20:37.120
project Papis?"

00:20:37.120 --> 00:20:40.400
I'm not sure what... oh it's a Zotero

00:20:40.400 --> 00:20:41.280
alternative. Okay.

00:20:41.280 --> 00:20:43.840
I'll look into it. Thank you.

00:20:43.840 --> 00:20:45.919
(Leo: I don't know about it either, so

00:20:45.919 --> 00:20:49.600
please look into it and let me know.)

00:20:49.600 --> 00:20:53.200
Have we covered all the questions?

00:20:53.200 --> 00:20:55.679
(Leo: I believe we have. We have about

00:20:55.679 --> 00:20:56.880
two-minute leeway

00:20:56.880 --> 00:20:58.880
for me to move into the next talk, so

00:20:58.880 --> 00:21:00.240
we're right on time.)

00:21:00.240 --> 00:21:01.760
All right. Thank you so much. Really

00:21:01.760 --> 00:21:04.159
appreciate it. Good luck everyone!

00:21:04.159 --> 00:21:05.440
(Leo: well thank you, and thank you so much for

00:21:05.440 --> 00:21:07.600
coming, and allowing me not to

00:21:07.600 --> 00:21:08.400
be the only one

00:21:08.400 --> 00:21:11.440
talking about org-roam today.) Noorah: Sounds good.

00:21:11.440 --> 00:21:14.559
All right. (Amin: Thank you both very much.)