From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id v+h1HW2s1l/kbQAA0tVLHw (envelope-from ) for ; Mon, 14 Dec 2020 00:06:05 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id qMfWGG2s1l8oFgAAbx9fmQ (envelope-from ) for ; Mon, 14 Dec 2020 00:06:05 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id B3AB29403A7 for ; Mon, 14 Dec 2020 00:06:04 +0000 (UTC) Received: from localhost ([::1]:58036 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kobNL-00026a-8d for larch@yhetil.org; Sun, 13 Dec 2020 19:06:03 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:58416) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kobMu-00026H-0u for emacs-orgmode@gnu.org; Sun, 13 Dec 2020 19:05:36 -0500 Received: from mout.gmx.net ([212.227.17.20]:35125) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kobMr-0002r6-PS for emacs-orgmode@gnu.org; Sun, 13 Dec 2020 19:05:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1607904284; bh=JmIlzEVtIf1b5RyjE40VfRGRdO7bjX58IH3EvaUBwac=; h=X-UI-Sender-Class:From:To:Cc:Subject:Date:In-Reply-To:References; b=Fmzz45t4Pw4+LkwBZ2C8Ov0TnjQAfilR2MNiewMGDss8pP84kqhvgROKe3VItas2E P0jQL1EpxMXVg9zvVMWI2zodfd1wActCYwBdwmbGFzTDfFlheLmmbMZG5yf09ifSEb 3cMcQm2Rqp9Dbivfa6tG2BFfv4o7OtO/5Kjh4kVk= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [213.165.168.94] ([213.165.168.94]) by web-mail.gmx.net (3c-app-mailcom-bs09.server.lan [172.19.170.177]) (via HTTP); Mon, 14 Dec 2020 01:04:44 +0100 MIME-Version: 1.0 Message-ID: From: pietru@caramail.com To: TRS-80 Subject: Re: Org Capture Menu cannot be fully viewed Content-Type: text/plain; charset=UTF-8 Date: Mon, 14 Dec 2020 01:04:44 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: <87y2i2ttl7.fsf@gmail.com> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:41muXKgJzrAa+vtTpR2ybsmplqxGlRvBu3GBi1eTc6x9iueEP/Q2nYYB8s5E4PlpJaR9h jG9FnLK1Tf7FE74INMJrJcbgm80rWnToGwc7RwFx5OwiyhIBqYa525e4ZmUMLXAMFZI4loDACELv /pjkOlsVCB6s4JLzJT7TW8S9EhMRMcZawliDaTsd7m9fgVMqhiPjNbeqV1Bc6loZBcliAVWBOy+I qkOe2aWSD5fbl/WdPzMDlAk1uVaNUKbyga1k5wFhZ3mRBzhXLnJYGltrLhWVGNHjNLVnHEK0035A Ss= X-UI-Out-Filterresults: notjunk:1;V03:K0:drJ1YX1gq3g=:uSvv0l2SgDo1r2WL0Diwpm 0ZESYh7FuJK8G7N7u7B1COd7VZHTA63vzf4dDdinPB7/QBcDavx5JsAwSnFsm221Qwefl3bW3 2QoF57Ja04o5przyNtaTwH6iUwf2zBXWvvN5t58z5GSM78XnqeE5oqBqKX8FIIhlIsvty/1+0 SDydpErws7M9TuTJZyL4ZBKxHSjl/iHjT7kft4Oxqsh8JLBcUYz0qy1jeyNorWy/t9HlYMPGi iNp2JHG1SxTyaW5+fGZqFI3BLy0Jy0opObSs/QFLi0zril7gpmQ3jUZTapJzabqDww0mICbt4 P4ra7Og+qTVuLtPt3nVC0qb4ELPPYf/quza4l3s64au5Kv8chqwqw7MoBmBvrjw/9AEe8lxfA vFBrEObqISvdFxmSrd4M46g9Qjftb4yJ3lf19OFVmniXDKjLK0cPAZiy7QAMAGlbglnbFAZwJ RRSM/VMNg1MAkyyZnG0LGQ7SttXTGJYxYXnleYoYIPW96XAdeWoJoeecnnQhxVqb+n2/xvbPX PXVEqLe+v1Sq9NjP1aSyAiz2LZftr1LCIxlwMjHGMIljXfY6pcmBi2uuH883XIIwig4SHpPD1 NRDhJ3TEiiZos= Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=212.227.17.20; envelope-from=pietru@caramail.com; helo=mout.gmx.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -1.90 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmx.net header.s=badeba3b8450 header.b=Fmzz45t4; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=caramail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: B3AB29403A7 X-Spam-Score: -1.90 X-Migadu-Scanner: scn1.migadu.com X-TUID: 8A7ZA219dudy > Sent: Monday, December 14, 2020 at 12:08 AM > From: "TRS-80" > To: emacs-orgmode@gnu.org > Subject: Re: Org Capture Menu cannot be fully viewed > > On 2020-12-12 23:57, pietru@caramail.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 > structure. Yes, the prose seems a challenging to capture, except for extracting from emails perhaps. > 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 t= o 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. Absolutely correct. > 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 impl= ement. > > 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 capt= ure template suitable for archaeological work. Completion (including regexp) would really help them. We can have a number of master files (with defini= tions, 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 woul= d 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-mo= de. Thank you so very much Pietro > Cheers, > TRS-80 > >