FYI:
We can get an "index" number for items in a list, and we could use this in
a button to set an index field in each tiddler or a data tiddler for later
reference using the allbefore and count + 1
<$list filter="[tag[TableOfContents]]">
{{{ [tag[TableOfContents]allbefore<currentTiddler>count[]add[1]] }}}
<$link/><br>
</$list><br>
However this will need the whole list to be processed for each item in the
list. and could take a lot of time.
- With a little trickery you may be able to make the numbering "re-start
able", ie get the last issued and add more from there.
Tones
On Thursday, 17 December 2020 at 09:49:47 UTC+11 TW Tones wrote:
> Is your primary purpose to assign a number to a set of tiddlers and retain
> them indefinitely?
> Is processing the large number of items only the first time, or on import
> because we could assign "serial numbers" as created or as used?
>
> I suppose I need to understand why you need this, or to what purpose to
> present one of a number of different methods.
>
> - The created date is almost, if not actually unique, and there is a
> way to make them unique in retrospect if necessary.
> - It is possible to store tiddler titles in a list that is itself in
> the order required, without introducing index's
> - List item can be generated automatically
> - It is common in tiddlywiki to access tiddlers in a list by more than
> one sort method, in different orders the serial number is less important.
> - I have built serial number assignment for tiddler if that would
> satisfy your needs.
>
> Tones
>
> On Thursday, 17 December 2020 at 04:48:44 UTC+11 [email protected]
> wrote:
>
>> Would it be desirable to add a new button action to persist a list filter
>> directly into a DataTiddler, with the row number as the index?
>>
>> I can construct a DataTiddler like this manually using:
>>
>> * A count of entries from a filter
>> * A range up to the count, subtracting one from each to make it base zero
>> * Re-run the first filter, butfirst<current range value>, first entry
>> * Set-field action to save the filter result to a DataTiddler, using the
>> current range value as the index
>>
>> If the range filter exceed 10,000 records, this process cannot run. Even
>> when I break the process out into smaller chunks, the throughput gets very
>> slow after 20,000 records.
>>
>> Does anyone else think this could be useful when trying to pre-process a
>> large amount of data?
>>
>
--
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/2cb36186-0e58-483b-bd62-f9dda1bbb3b7n%40googlegroups.com.
