Upgrade StorageQuick search not so quick: let us optionally search just title+author (and not fulltext)
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
A related problem is that if you perform a quicksearch and then add a Tag to a result it seems that Zotero runs the search again after the change; since in normal-sized library quicksearches are very slow (!) this makes adding multiple tags a pain (the browser freezes for many seconds).
A quick fix (until next release) would be to change in your chrome/content/zotero/xpcom/ the file search.js and at line 401 change the lines as following
if (condition=='quicksearch'){
var parts = Zotero.SearchConditions.parseSearchString(value);
for each(var part in parts) {
this.addCondition('blockStart');
this.addCondition('title', operator, part.text, false);
this.addCondition('creator', operator, part.text, false);
//this.addCondition('tag', operator, part.text, false);
this.addCondition('note', operator, part.text, false);
this.addCondition('annotation', operator, part.text, false);
/*if (part.inQuotes) {
this.addCondition('fulltextContent', operator, part.text, false);
}
else {
var splits = Zotero.Fulltext.semanticSplitter(part.text);
for each(var split in splits) {
this.addCondition('fulltextWord', operator, split, false);
}
}*/
this.addCondition('blockEnd');
One request though: Would it be possible to add "Note Content" to the drop-down menu in the quicksearch bar? I think that would be pretty helpful for those of us who use notes extensively.
Thanks!
JR
Regards
JR
How difficult would it be to:
1. Make the user have to hit enter before the search starts
2. Give users an option to turn off quick search altogether
Either of these would provide a solution.
This has been an issue for 18 months. I don't mean to complain so vociferously, but really, having an extension which freezes the browser for 20+ seconds is really unacceptable. It's frustrating as a user to have this happen multiple times a day, especially when it seems from the outside that a simple workaround could have been implemented.