To: TRS-80 <firstname.lastname@example.org>
Subject: Re: Org Capture Menu cannot be fully viewed
Date: Mon, 14 Dec 2020 01:04:44 +0100 [thread overview]
Message-ID: <trinity-4d444ac1-ed80-4727-8f04-386692b6cd0a-1607904284190@3c-app-mailcom-bs09> (raw)
> Sent: Monday, December 14, 2020 at 12:08 AM
> From: "TRS-80" <email@example.com>
> To: firstname.lastname@example.org
> Subject: Re: Org Capture Menu cannot be fully viewed
> On 2020-12-12 23:57, email@example.com wrote:
> > TRS-80 wrote:
> >> If you care to share a slightly bigger picture view, particularly
> >> about the structure of the data you are trying to capture (and/or,
> >> your workflow) we could likely come up with something that would work
> >> much better for you than a capture template, at least in this
> >> particular case.
> > In many instances, previous work would have been done, so people would
> > want to quickly skip entries.
> I think perhaps plain old Org headline folding might be great for
> quickly navigating to the incomplete portion of the document?
> Especially if the sections each might contain a lot of prose and/or
> notes, and/or the sections are logically organized in any sort of tree
Yes, the prose seems a challenging to capture, except for extracting from
> If it's more about key: value type data, I would (again) recommend Org
> Properties. I'm sure there might be a way (or we could whip one up) to
> help automate searching through the document looking for empty
> Properties if that's the sort of workflow you would like.
I got to discuss this key-value with some people. This is quite related to
link types using keywords. Will will find it useful if not restricted to email
etc. But we would like to specify the key ourselves.
But having completion would be really super , especially if people can use
regexp search on entries in a master file).
> > The plan for Org-Mode Capture is primarily for such Exclusive and
> > Unsystematic Surveys where we do not necessarily use standard forms.
> > I'm not sure if you capture the drift concerning unsystematic surveys.
> > Most times I cannot tell you exactly what people in the field came up
> > with. The pace can be rapid and some could be working in challenging
> > conditions. The plan is for the Crew Chief to make a quick template,
> > and which could change each day. maintain and review notebooks and
> > records and overseeing quality control is done daily. It is customary
> > to split the day. One of the best ways we improve survey efficiency
> > is to anticipate bottlenecks and invent creative logistical solutions
> > right in the field.
> > The long template situation then occurs. You can access better than
> > myself as you know what org and org-capture can do and what not.
> Overall, what I am imagining is some set of Orgmode files as templates.
> Each template containing all requirements of data collection for that
> type. So you would simply make new copy of empty template file for each
> new instance of that particular case / template. Inside would be
> headings organizing the different parts of the survey or whatever the
> work is. And then Org Properties as needed for key: value data, located
> within the tree structure on headings as appropriate (remembering that
> Property inheritance is possible).
> You could even use the TODO functionality to mark sections as being
> complete. It then becomes easy to find sections which have not been
> finished yet. With org-log-done and org-log-into-drawer (and other
> related) settings you could even have different teams make (timestamped)
> metadata notes about what they accomplished, making it easier to hand
> off partially completed work between teams and allow them to communicate
> between each other in a sort of side channel without that info being
> directly in the report.
> As you can see, there are often many options, so it's mostly about "what
> workflow do you want?" ;)
Let's concentrate on essential parts first and not too much hassle to implement.
> > I briefly reported on what we found problematic in practice. But
> > we're at the beginning of this, and would likely report on other
> > things as we progress.
> Yes, please let us know how you are getting on!
> > Nevertheless, we see some aspects where your scheme can be improved to
> > cater for more serious work. Emacs is quite good software.
> This is probably the strongest point. Emacs can be almost whatever you
> want it to be. Even non-programmers (with a little effort) can stitch
> together their own custom interfaces using some combination of
> package(s), built-in functionality, and perhaps a bit of Elisp. Which
> makes it a bit of a universal User Interface framework, in a way.
That's the kind of people we have. If they can conveniently set up a capture
template suitable for archaeological work. Completion (including regexp)
would really help them. We can have a number of master files (with definitions,
categories, etc). They can then concentrate on jotting useful comments
and progress, rather than playing with Academese. The latter part can be
searched and selected from the master files.
> > Hope my comments helped somewhat.
> Yes, I think so. Hopefully my replies will therefore heve been equally
> helpful to you.
Now that the topic is understood, what can we tackle? Don't think it would
be useful elaborating on extremely specific archaeo things. Just things
that would be useful to many people, although inspired by our discussion.
Bit more flexibility so we can continue doing some more things with org-mode.
Thank you so very much
next prev parent reply other threads:[~2020-12-14 0:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 18:02 Org Capture Menu cannot be fully viewed pietru
2020-12-12 22:09 ` TRS-80
2020-12-12 22:46 ` pietru
2020-12-12 23:13 ` TRS-80
2020-12-12 23:30 ` pietru
2020-12-13 0:00 ` TRS-80
2020-12-13 0:10 ` pietru
2020-12-13 11:06 ` Jean Louis
2020-12-13 18:28 ` pietru
2020-12-13 20:37 ` Jean Louis
2020-12-13 20:52 ` TRS-80
2020-12-13 21:02 ` pietru
2020-12-13 21:48 ` Jean Louis
2020-12-13 22:08 ` pietru
2020-12-13 22:20 ` pietru
2020-12-13 22:00 ` TRS-80
2020-12-13 22:36 ` pietru
2020-12-13 20:32 ` TEC
2020-12-13 21:43 ` Jean Louis
2020-12-13 0:46 ` Tim Cross
2020-12-13 1:32 ` pietru
2020-12-13 2:08 ` pietru
2020-12-13 3:16 ` TRS-80
2020-12-13 3:49 ` pietru
2020-12-13 4:30 ` TRS-80
2020-12-13 9:58 ` pietru
2020-12-13 16:52 ` Jean Louis
2020-12-13 10:24 ` Jean Louis
2020-12-13 18:41 ` pietru
2020-12-13 20:48 ` TRS-80
2020-12-13 4:57 ` pietru
2020-12-13 9:24 ` Christopher Dimech
2020-12-13 23:08 ` TRS-80
2020-12-14 0:04 ` pietru [this message]
2020-12-13 9:44 ` Jean Louis
2020-12-13 18:46 ` Christopher Dimech
2020-12-16 18:46 ` No Wayman
2020-12-16 16:58 ` No Wayman
2020-12-13 15:12 ` Jean Louis
2020-12-13 18:08 ` pietru
2020-12-13 20:06 ` Tim Cross
2020-12-13 21:37 ` pietru
2020-12-13 21:57 ` Bastien
2020-12-13 22:31 ` pietru
2020-12-13 23:30 ` Jean Louis
2020-12-13 23:52 ` Bastien
2020-12-13 22:34 ` Jean Louis
2020-12-14 12:41 ` Marco Wahl
2020-12-14 13:00 ` pietru
2020-12-14 13:18 ` Marco Wahl
2020-12-14 20:02 ` Org Capture Menu cannot be fully viewed - Results of testing C-n, C-p, C-v pietru
2020-12-16 21:46 ` Marco Wahl
2020-12-16 23:25 ` pietru
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).