positiv,

No withstanding Marks wise words, I have a separate wiki with the JSON 
mangler plugin for processing files such as csv or with other delimiters. 
You have full control and auto indexing or tiddler naming the result is 
stored in a json file with the tiddler format and becomes a plugin. This is 
my dataset processing and conversion utility , I then drop the data plugin 
on a wiki and build the code or view templates etc... for processing the 
data as data tiddlers using native TiddlyWiki. Another advantage of this 
approach is its easy to save, annotate, regenerate and export your data. 
Including capturing changes when the shadow tiddler is overridden.

JSON mangler is also able to process deeper third party json files.

Of course ultimately you may want to build a solution that includes JSON 
mangler or other import methods in your wiki, but until that day a utility 
wiki for data set import and production is wise.

Despite using JSON mangler for some sophisticated datasets I often build my 
own parsing methods if the delimiters are simple, starting with \n then 
perhaps , etc... CSV has the advantage you can also export CSV from 
tiddlywiki.

If someone gives me a few publicly available data sources of use I would be 
happy to build a range of "test data" "data plugins".
eg;

   - countries
   - country international codes
   - Airport codes
   - Geological epochs
   - The Planets
   - etc...


Regards
Tones

On Thursday, 17 December 2020 at 11:38:19 UTC+11 Mark S. wrote:

> On Wednesday, December 16, 2020 at 4:16:46 PM UTC-8  wrote:
>
>>
>> The text file is simple enough to find records using splitregexp[/n] . 
>> However, I know this particular file has a unique key for each record. I am 
>> able to convert the file using .Net into a json file describing a 
>> DataTiddler that I can import. This way I can reference each record by its 
>> primary key. If there was a way to auto-number the list entries and persist 
>> them to a DataTiddler, this would be close enough for me to selectively 
>> process the records further without having to re-split the original list 
>> over and over.
>>
>> I'm confused. If you've made your text file into an importable JSON file, 
> and if each record has a primary key, why do you need to add an index? 
> You're adding an index to something that already has an index. 
>
> There's the temptation when you first using TW to perceive data 
> dictionaries/DataTiddlers as the primary method of data storage and 
> manipulation because that is what they would be in other technologies. But 
> in TW, the DataTiddlers are there more as a convenience tool. They are very 
> limited. The basic data entity in TW is the *tiddler*.  There are lots of 
> filter operators and widgets dealing with tiddlers, and very few dealing 
> with DataTiddlers. Possibly consider converting your text file into 
> multiple tiddlers (either individual tiddler files or a JSON file 
> containing them all).  You will likely have a better experience down the 
> road manipulating those records then stowing them in a DataTiddler.
>

-- 
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/9818ab06-12ba-48c8-8792-ca50051f8f05n%40googlegroups.com.

Reply via email to