Several datetrees in one file

Several datetrees in one file

[Alexander Baier]

Hello,

I would like to have several datetrees in one org file. I want to have
different datetrees under different headlines. The setup I have in mind
is an address book with chronologically ordered notes for each person.

This is an example entry for one person. Each following person in that
file will have their own datetree and corresponding notes.

* John Doe
  :PROPERTIES:
  :MAIL:     john.doe@example.com
  :END:
- nice guy
** 2014
*** 2014-10 October
**** 2014-10-27 Monday
***** meeting 1
Entered on <2014-10-27 Mon 00:00>
- notes
**** 2014-10-28 Tuesday
***** meeting 2
Entered on <2014-10-28 Tue 00:00>
- more notes

Currently, there is no way to capture a new entry in a datetree for a
specific person. The current capture templates only allow for one
datetree per file.

Is it possible to extend this datetree functionality and let the user
specify the file and the headline under which the datetree resides?
Adapting the example from the manual, I would like to have something
along the lines of:

(file+headline+datetree "path/to/file" "headline")

or

(file+olp+datetree "path/to/file" "level 1 headline" "level2" ...)


Is this possible?

Regards,
-- 
Alexander Baier

Re: Several datetrees in one file

[Nick Dokos]

Alexander Baier <alexander.baier@mailbox.org> writes:

> Hello,
>
> I would like to have several datetrees in one org file. I want to have
> different datetrees under different headlines. The setup I have in mind
> is an address book with chronologically ordered notes for each person.
>
> ...
>
> Is this possible?
>

I don't think so (but I don't know for sure).

-- 
Nick

Re: Several datetrees in one file

[Alexander Baier]

On 2014-10-29 04:01 Nick Dokos wrote:
> Alexander Baier <alexander.baier@mailbox.org> writes:
>> I would like to have several datetrees in one org file. I want to have
>> different datetrees under different headlines. The setup I have in mind
>> is an address book with chronologically ordered notes for each person.
>>
>> ...
>>
>> Is this possible?
>>
>
> I don't think so (but I don't know for sure).

I dug around the source code for org-capture and org-datetree and seems
that there is only lacking support in the capture process. IIUC the
datetree functionality is affected by narrowing, which could be used to
force it to use the datetree under a certain header.

As I am not quite convinced of my approach jet, I would like to hear
what others would use in my situation described in the first post. To
rehash: An address book with one level 1 heading per person and notes
corresponding to said person in a datetree starting at level 2.

Regards,
-- 
Alexander Baier