From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id pPytDRHe1V/jQAAA0tVLHw (envelope-from ) for ; Sun, 13 Dec 2020 09:25:37 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id kMj4CBHe1V+zcAAAB5/wlQ (envelope-from ) for ; Sun, 13 Dec 2020 09:25:37 +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 51BE0940148 for ; Sun, 13 Dec 2020 09:25:36 +0000 (UTC) Received: from localhost ([::1]:52824 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1koNdF-0005l5-Mk for larch@yhetil.org; Sun, 13 Dec 2020 04:25:33 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:43652) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1koNcg-0005kl-Uh for emacs-orgmode@gnu.org; Sun, 13 Dec 2020 04:24:58 -0500 Received: from mout.gmx.net ([212.227.17.22]:43077) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1koNce-0004Uh-MY for emacs-orgmode@gnu.org; Sun, 13 Dec 2020 04:24:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1607851447; bh=+2FcPsCDazKyH0fJnnOkzqtPG6NOaSt/ByBl1Hs4Up0=; h=X-UI-Sender-Class:From:To:Cc:Subject:Date:In-Reply-To:References; b=hm6BFdkGx5QPizw/V1fWuMrogVMBfjThE9KUx4TVNb43E/JMtBHO/WkMkFGTiByCQ o59+ZunUE64lV2Xxy7qbaONuohCOIJrnuXkfKo+ui0JIfMLtvJYj+WlapOTNH+qjkq /BR5qA4J5/JF8bT/xVUhOulx2FnR4GU09Qif6OCY= 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); Sun, 13 Dec 2020 10:24:07 +0100 MIME-Version: 1.0 Message-ID: From: Christopher Dimech To: pietru@caramail.com Subject: Re: Org Capture Menu cannot be fully viewed Content-Type: text/plain; charset=UTF-8 Date: Sun, 13 Dec 2020 10:24:07 +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:l33lcgUb8B8N2gO4CsGZNOwYUsgIeoN5n2bb8Ji5qO9e2Eho2VzGGZCl3qOQ2DrYvDCCK YtU+16tkKR+ucj4kCSWPSVyCbyt+HJnO/165Zkm6YCIOcfdVNwRP/OzPCD0r6UjHilhqti6M9NaK mDLFhJRulxqanrHwtfB9hFER2EqblFzc6bDvQouH5gUGgbViApWSOyn942XZ7ZLsxDLfLnvwwcH9 PS7wMv7rI0SwYuUl2CRnJfAzJANDhlrrrZ7YWV3IbwjyM1JTxBQ3NI48vJoq4HWC4PhdUuA03qVf uw= X-UI-Out-Filterresults: notjunk:1;V03:K0:CZVuj6SZU8Q=:PtrKT0LySkGYWaTIpZB3Zy TzCc5Fjy79el1fDTbHlDE4QEmO2Y7dzW5bQbZQGxcf8HkPR9Ga3EL1OvtJB7aKFB+n8w9MJtC HTUI+Pv1DyJqvE2k5BKiKwLMNldHZKyy0Pk52FQPcSOgvM1yA5iqkyI4H6QENObbIyDHYR+54 YFh1Te8h1A08voThuSkLQEE2P5b+wjjB3oeD9vxq2VoQg8uwaWl0lXVkW3cZSPCKZLjmoL/kO zAoFz7TkEg/F9dh36u5Iamxlmh3f+iEc12+lLrgNH3dDBF9vFNJedP/fmGSms0NO/5avGVKc6 wDxSohkp6gx3sDNXw+q1r9SzRbsGEuPjBbFtR/cS8k0CxZCaSXZi/ODa2YIZMMoNgKyUvvKe8 hy92Jip+rnKV9WtTTOK6+zEBwTG1zECszt+GxdvmS6EchhYSACtUXUj5xZXzAckLMmJEMq3Vx j8iGRMpce2JStfJkhA6MUOwBjz9zAAGI9NxrDL4o70q1LztvtRtwrgqtM7sms7bsQpskp0q5W wd6Q+RCThYTVETD7IBQVZedaf0hATOKALaM35zKpHMAwFj6raA0EnRVxojIzv14g26DMuEYSY p+Pp5L2tLGmzM= Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=212.227.17.22; envelope-from=dimech@gmx.com; helo=mout.gmx.net X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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: -0.70 Authentication-Results: aspmx1.migadu.com; dkim=fail (headers rsa verify failed) header.d=gmx.net header.s=badeba3b8450 header.b=hm6BFdkG; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmx.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: 51BE0940148 X-Spam-Score: -0.70 X-Migadu-Scanner: scn1.migadu.com X-TUID: zLHjbo2+emfi Org Capture has the ability to get specific information using "%:keyword" (e.g., for rmail one can use %:subject to get the specific email subject). An extension to "%:keyword", would be to allow the extraction of keywords taken from recfiles, which are also text based. You could then have %:Investigation_Type in Org-Capture entry. There needs to be some way to specify the recfile. The specification of recfiles is described by Gnu Recutils. https://www.gnu.org/software/recutils/ =2D---- file.rec ----- Investigation_Type: Historic Background Research Site Evaluation/Testing =2D---- file.rec ----- This could make easier capture because instead of %^{prompt|default|completion2|completion3...} you could have %:Site_Type The scheme would work very well if you have hierarchical lists that you can use for specificity. Domestic Structure > Settlement > Hamlet or Village %:Domestic_Structure: %:Settlement\n =2D---- file.rec ----- Domestic_Structure: Settlement Settlement: Hamlet or Village =2D---- file.rec ----- rather than using "Site_Type: %^{Site_Type: |default| + Domestic Structure or Architectural Complex| + Resource Extraction or Production| + Transportation Structure or Features| + Funerary and Burial Structures or Features| + Non-Domestic Structures| + Archaeological Feature| + Rock Art| + Water-Related}\n%?" > Sent: Sunday, December 13, 2020 at 5:57 AM > From: pietru@caramail.com > To: "TRS-80" > Cc: emacs-orgmode@gnu.org > Subject: Re: Org Capture Menu cannot be fully viewed > > > If you care to share a slightly bigger picture view, particularly abou= t > > 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. > > Most agencies, universities, museums and archaeological organizations us= e > standard forms for recording sites. Generally speaking these are used bu= t > with a couple of caveats. First, there are occasions when a standard fo= rm > may not call for recording enough data or the right kinds of data to sat= isfy > particular needs. Then there are Exclusive Surveys (Incomplete coverage= , > portions of the project are excluded) and Unsystematic Surveys (done wit= hout > a specific plan, methods at varied level of intensity; coverage random, > opportunistic, or intuitive). In many instances, previous work would hav= e > been done, so people would want to quickly skip entries. > > The plan for Org-Mode Capture is primarily for such Exclusive and Unsyst= ematic Surveys > where we do not necessarily use standard forms. I'm not sure if you cap= ture the drift > concerning unsystematic surveys. Most times I cannot tell you exactly w= hat 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, an= d which could > change each day. maintain and review notebooks and records and overseei= ng quality > control is done daily. It is customary to split the day. One of the be= st ways we > improve survey efficiency is to anticipate bottlenecks and invent creati= ve logistical > solutions right in the field. > > The long template situation then occurs. You can access better than mys= elf as you > know what org and org-capture can do and what not. I briefly reported o= n what we > found problematic in practice. But we're at the beginning of this, and = would > likely report on other things as we progress. Still, most things are l= ikely > to be done by the "Institute for Technologies applied to Cultural Herita= ge (itabc)". > > Nevertheless, we see some aspects where your scheme can be improved to c= ater for more > serious work. Emacs is quite good software. > > Hope my comments helped somewhat. > > Pietru > > > > > > > Sent: Sunday, December 13, 2020 at 4:16 AM > > From: "TRS-80" > > To: emacs-orgmode@gnu.org > > Subject: Re: Org Capture Menu cannot be fully viewed > > > > On 2020-12-12 21:08, pietru@caramail.com wrote: > > > Here is one version of a template > > > > > > (setq capture-template-investigation-type '( > > > > > > ("a" "Historic Background Research Site Evaluation/Testing" entry > > > (file "~/histr/archaeol.org") > > > "* Site_Type: %?\n %T\n") > > > > > > [...] > > > > > > ("u" "Remote Sensing" entry > > > (file "~/histr/archaeol.org") > > > "* Site_Type: %?\n %T\n") )) > > > > > > > Are there any more to these templates you did not show? > > > > Because, (and unless I am missing something) what I see are essentiall= y > > all the same (and quite simple). You would end up with something like > > the following in your target file (with the cursor ending up at the x)= : > > > #+begin_example > > > > * Site_Type: x > > [2020-12-12 Sat 21:58] > > > > #+end_example > > > > In fact I don't even see where the type name ends up in the result? > > > > If all my assumptions above are true, I think you would probably be > > better served with a simple completing-read (or similar) function to > > select the "Investigation Type" from a list and then simply insert tha= t > > along with a timestamp. Which it will take you longer to reply to thi= s > > email and confirm than it would take me to write such a function. :) > > > > Benefit of that way also removes possibility of typos in the type name= . > > > > In fact, the above could even be done with something as simple as > > Yankpad[0]. > > > > I have no idea what your workflow looks like, or where this data ends > > up. However, thinking further, I would imagine it might even be helpf= ul > > to set one or more Org properties[1] for things like "Investigation > > Type" (along with some other things I could speculate like "Location" > > etc.). But all of that depends on even more things I don't know about= . > > > > If you care to share a slightly bigger picture view, particularly abou= t > > 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. > > > > Cheers, > > TRS-80 > > > > [0] https://github.com/Kungsgeten/yankpad > > [1] https://orgmode.org/manual/Properties-and-Columns.html > > > > > > =2D-------------------- Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy