List of Tiddler NOT having a defined tag of field?

Hello Experts,

I try to establish Tiddlywiki as Wiki in a professional environment what is really difficult but I believe in Tiddlywiki.
So we have a lot of chapters in the Wiki now and we need to find out what was reviewed in the last x month or in the last year.
My Idea is to ha a field named “2023” in each Tiddler with the name of the reviewer as content (eg “Stefan”). As alternative a Tag can be added but than I am missing the name of the reviewer.

To have an overview about the Tiddlers what are NOT reviewed I am searching for a list definition for all Tiddlers NOT having the field “2023”.

Is that “negative” searching possible?

Thx in advance

Short answer - yes. Many filter operators are able to be used inverted. On the main page Filter Operators there’s a table and with some extra columns, with the second-last being red exclamation points. Those indicate the filters that can be inverted. I think you’d use has[2023] for ones with the field (and must have a non-empty value), and conversely !has[2023].

That said, the community is welcoming around brainstorming design decisions as well. I think what you describe will work, but based on the situation there may be some alternatives that are less clunky. I’m curious how many editors are involved, or are there multiple reviewers but you’ll be the only editor? Would it be more helpful for you to have a log of all changes for instance? Note that every time a tiddler is saved it also updates it’s own modified field, so part is done automatically if “reviewing” involves saving.

Hi @stobot ,

thank you for the fast answer.
Let me try if I can find the right syntax.

You asked for the use case?
As I wrote. I try to establish a Wiki with very special information in it. It will be multilingual (solved by a lot of help from here) and a lot of the Tiddlers needs to be reviewed each year. It is not enough to save the Tiddler again. I want to establish a process that the person who perform the review has to write active his/her name into the field. No simplification here :slight_smile:

Sorry if I was unclear - I guessed that you’d just need the !has[2023], note it’s just that extra exclamation point.

I asked about the multiple editors because that’s something you have to be careful with. Each of the different savers has different pros / cons when it comes to this. The standard version is last-save-wins and it’s saved at a whole wiki-level only. So if you and other people have it open, you could make changes and hit save, but others with it open don’t get notified it’s been changed, so if they make their own changes and save, your original changes are lost. I work in a corporate environment and have tried almost all of the mechanisms, some are simple, some are complex, just a warning so you don’t go down the same path I did. Good Luck!

Hi @stefan_from_germany,

Rather than storing reviews in the reviewed tiddler, I would create Review tiddlers, tagged “Review”.
These review tiddlers would store the reviewer name, the reviewed tiddler title and the date in fields, and you could even have a dedicated viewtemplate which displays the review instructions.

Finding articles not reviewed in 2023 would be done thanks to a filter like this (untested):
[tag[Article]]:filter[all[tiddlers]tag[Review]article<currentTiddler>regexp:date[^2023]count[]compare:number:eq[0]]
This example assumes that reviewed tiddlers are tagged “Article”, and review tiddlers store the date in a date field and the reviewed article in an article field.

Have fun,

Fred

@tw-FRed ,
I like the Idea. Let me discuss it with the editorial team.

The last outcome of our discussion was that we need the help from the native speaking participants to translate the content. The main language is English. If a tiddler was added or changed we need to have a filter to find them to help for translation. This is solved by a filter to search for the changes since a defined date.
But I, as main global responsible, want to have an overview about all non reviewed / translated tiddlers to adjust the workload in the team.

I will report further how we make it

Stefan