On Sunday, June 7, 2020 at 8:51:11 AM UTC-7, Jon wrote:
>
> I plan to use TW5-JsonMangler 
> <https://joshuafontany.github.io/TW5-JsonMangler/> to import a diary as a 
> .csv file into my wiki so that each row is a new tiddler with the date as 
> the name.
> The dates are in the format 20/06/07 rather than 2020/06/07.
> Will my wiki recognise the dates correctly or do I need to somehow convert 
> them first?
>

It all depends on what you mean by "recognize the dates correctly".

Tiddlers have standard fields "created" and "modified", which get date 
values using "YYYY0MM0DD0hh0mm0ss0XXX" formatting (see 
https://tiddlywiki.com/#DateFormat and https://tiddlywiki.com/#Date%20Fields
)

You can use these values in filters to identify and sort tiddlers (see 
https://tiddlywiki.com/#Filter%20Operators for "days", "eachday", 
"sameday", and "sort")

However, for your stated purpose, the imported date values will be used as 
the *titles* of the tiddlers.  Fortunately, this dates-as-titles usage will 
still sort nicely using simple alpha-numeric sorting, because your chosen 
format, "YY/0MM/0DD", puts the most-significant value first and uses 
zero-padded numbers.  If your dates were in a different format (e.g., 
MM/DD/YY), then this wouldn't work since a value like "6/7/20" would 
alpha-numerically come *after* something like "12/25/20".

I concur with TonyM's suggestion: use the YY/0MM/0DD date *as-is* for the 
title, but also create a fully-formatted custom field such as 
"published-date", using the same "YYYY0MM0DD0hh0mm0ss0XXX" format as the 
standard "created" and "modified" fields.  This will then allow you to use 
the above mentioned date-related filter operators with the custom field.

enjoy,
-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/336a4837-c070-4d83-8cd1-9b5d97cdac9bo%40googlegroups.com.

Reply via email to