When searching indexed databases on the web, the word “windsor” returns all the documents in the database. This is probably because the $$updatedby field has the updater name ( John Testeraski/Windsor. I was wondering if there is a way to avoid that?
Subject: Index Search help
Unfortunately not, since you cannot specify which fields to exclude from the FT matching.Unless, of course you can perform field specific searches like:
[subject]=windsor or [body]=windsor
- which wouldn’t match $UpdatedBy contents.
Wouldn’t it be nice, if you had a FT property like “Don’t index $xxx fields”, or simply not searching those fields unless explicitly referenced, as in:
[$UpdatedBy]=Windsor
But I wouldn’t hold my breath 
Subject: Possible (simple) solution: exclude $updatedby from search result
when you make FTsearch or Domain Search notes searches for all fields. Unfortunately also the auto generated fields - including $updatedby.
This is very annoying… A possible solution could be to set the database-property ‘Limit entries in $updated fields’ to 1. But still at least one name will be saved with the field
Solution: go to the QuerySave event and simply use this formula:
field $updatedby:=“”;null
The disavantage is now, that you of course can´t use the $updatedby field anymore. as an alternative you can set the form property to Anonymous
If you have readers/authors fields you must use group/role names instead of person names.
This works, but only on new documents. Older documents cant have $updatedby removed this way. There is only one way as I see it. Create new documents and copy the fields one by one to these document, using the Notesdocument.items property. You then have to avoid $updatedby to be transferred with a simple if-statement.
ZoomTek.dk
Subject: RE: Index Search help
Thanks Morten, I was hoping you would tell me to simply go to the form property and uncheck or check something and Voila!
I am thinking two approaches:
Trap the string ( if the query field contains ‘Windsor’)
-
send the request to an agent that does a specific search on that ( like go through the documentcollections - which in this case will be almost all of them - and filter out the returns) - over 500 documents!!!
-
create a view for all the documents that are unique to Windsor and go against it using a simple @dbcolumn
I like the later and am about to implement it. Unless of course you have a better idea.