wish : filenames in the Calendar contain a full/ISO date, eg YYYYMMDD

[damien.courousse]

Hello!

I would like to suggest the following improvement:
filenames in the Calendar tree of files should be named following the ISO convention.
This means that filenames would be:
YYYYMMDD for days.txt
YYYYMM for months
YYYY for years.

Why?
for example, when a tag is regularly used in calendar files, for example for daily notes (eg @weekly, or @projectA),

moving to the Tags panel, if you select one of those tags, you currently see only a list of day numbers ("3, "4', "18", "25", ).
The displayed list of numbers is meaningless this way. Furthermore, if the tag '@weekly' was used for example in files 2011/11/06.txt and 2011/12/06.txt, you have access only to one of those files this way.

Changing the filenames following my proposal should solve this problem.

BTW, I know a bit about Python; if one of you provide me some guidelines (for an eventual patch to be accepted), I am willing to offer my help on this wish.

I would like also to thank all of the contributors to this tool! It is great!!!

cheers,
Damien

[Jaap Karssenberg (jaap.karssenberg)]

I agree with your problem statement, but not with the proposed solution.

Changing the file name for calendar pages mean you need to drop the
hierarchy in the index for calendar pages. So unfolding the "calendar"
namespace shows many years worth of pages, and you can't find the one you
are looking for. (If you keep the hierarchy, you get full page names like
"2012:01:20120101", which is event worse.)

An alternative solution is to make the tag view show a longer name as a
special case for for calendar names. Would need some modifications in the
index though, so not trivial.

-- Jaap

On Sun, Dec 18, 2011 at 6:06 PM, damien.courousse <<email address hidden>
> wrote:

> Public bug reported:
>
> Hello!
>
> I would like to suggest the following improvement:
> filenames in the Calendar tree of files should be named following the ISO
> convention.
> This means that filenames would be:
> YYYYMMDD for days.txt
> YYYYMM for months
> YYYY for years.
>
> Why?
> for example, when a tag is regularly used in calendar files, for example
> for daily notes (eg @weekly, or @projectA),
>
> moving to the Tags panel, if you select one of those tags, you currently
> see only a list of day numbers ("3, "4', "18", "25", ).
> The displayed list of numbers is meaningless this way. Furthermore, if the
> tag '@weekly' was used for example in files 2011/11/06.txt and
> 2011/12/06.txt, you have access only to one of those files this way.
>
> Changing the filenames following my proposal should solve this problem.
>
> BTW, I know a bit about Python; if one of you provide me some guidelines
> (for an eventual patch to be accepted), I am willing to offer my help on
> this wish.
>
> I would like also to thank all of the contributors to this tool! It is
> great!!!
>
> cheers,
> Damien
>
> ** Affects: zim
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to Zim.
> https://bugs.launchpad.net/bugs/905988
>
> Title:
> wish : filenames in the Calendar contain a full/ISO date, eg YYYYMMDD
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/zim/+bug/905988/+subscriptions
>

[damien.courousse (damien-courousse)]

Hello Jaap,

In this case, I would vote for
(1) keeping the file hierarchy with ISO filenames, so that
browsing/searching into the Calendar file hierarchy is easier from
external tools (eg sed/grep/awk...). This is another "feature" I like a lot.
(2) modifying the index view for calendar files, in order to display a
shorter name for the ease of reading.
In this case, we wouldn't need any modification in the tag view, which
would display the long ISO names.

best regards,
Damien

On 19/12/2011 09:30, Jaap Karssenberg wrote:
> I agree with your problem statement, but not with the proposed solution.
>
> Changing the file name for calendar pages mean you need to drop the
> hierarchy in the index for calendar pages. So unfolding the "calendar"
> namespace shows many years worth of pages, and you can't find the one you
> are looking for. (If you keep the hierarchy, you get full page names like
> "2012:01:20120101", which is event worse.)
>
> An alternative solution is to make the tag view show a longer name as a
> special case for for calendar names. Would need some modifications in the
> index though, so not trivial.
>
> -- Jaap
>