Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread TW Tones
Bob, Perhaps this helps, or not, I have not read this topic. fieldname[value] works in any filter to return only tiddlers with a fieldname with the ""value", it allows you to create things which look like new filter operators; eg display-code[show] However if you start using multiple

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Dr Bob Jansen
Saq, Ah, clever. Did not know about these templates. Will try tomorrow. Thanks for your help. BobJ --- Dr Bob Jansen The Cultural Conversations project Turtle Lane Studios Pty Ltd trading as the Australian Centre for Oral History 122 Cameron St, Rockdale NSW 2216, Australia Ph

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Saq Imtiaz
You can further simplify things a lot by using custom view templates, so you don't need to manually call each macro etc in each artwork tiddler and each person tiddler. For example, to get the same code applied to what you see for each Artworks tiddler, create a tiddler with this content and

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Dr. Bob Jansen
Colleagues, I should have added, if you are going to play with the file, the artwork that shows the wrong behaviour is TK1 and no other. The others don't have the correct macrocall in them. The list appears under the text, "*This artwork has been purchased by*" It should only show TK5.

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Saq Imtiaz
Bob, Try entering this directly in the TK1 tiddler: <$list filter="[{!!artwork_id}!is[blank]]" variable="not_blank"> <$list filter="[tag[Names]!tag[Index]!matchcontains:artwork_id{!!artwork_id}]"> <$view field="person_name"/> On Thursday, September 17, 2020 at 2:34:30 PM UTC+2,

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Dr. Bob Jansen
Sorry Saq, doesn't work either. You can download a copy of the TW from http://cultconv.com/TLSConsignment.html bobj On 17/9/20 10:12 pm, Saq Imtiaz wrote: Try: <$list filter="[[$artworkID$]!is[blank]]" variable="not_blank">    <$list

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Saq Imtiaz
Try: <$list filter="[[$artworkID$]!is[blank]]" variable="not_blank"> <$list filter="[tag[Names]!tag[Index]!matchcontains:artwork_id[$artID$]]"> <$view field="person_name"/> If you still have issues, it would be a lot easier to assist if you could post a copy of your file where we

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Dr. Bob Jansen
Colleagues, Experimenting with the contains operator but having trouble with how to write the operator string correctly. Am changing my <$list> structure to <$list filter="[[$artworkID$]!is[blank]]" variable="not_blank">    <$list filter="[tag[Names]!tag[Index]!match">   <$list

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Dr. Bob Jansen
Colleagues, just some more experimenting. If I put something into the artwork_id field of TK6 and TK7, for example, "TK2", the result displayed remains TK5, TK6 and TK7. That implies the problem is that search is not correctly matching the field content with the search string. bobj On

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Dr. Bob Jansen
Eric, that doesn't work, no results returned. Have also tried <$list filter="[tag[Names]!tag[Index]!matchsearch:artwork_id[$artID$]]"> which doesn't work either, no results returned. Interestingly, Saq's comment about replacing the call to the macro with <$macrocall

Re: [tw5] Re: search widget odd behaviour

2020-09-17 Thread Dr Bob Jansen
Saq, Thank you for your email and comments. The issue of one-to-many links is replicated in other relationships and so the issue still need to be resolved. Also, in the case of a print, there is more than one buyer of an artwork and thus we need the search facility. The issue of the macrocall