When using the quick search function it returns all renditions of each file. Is there a way to make sure search result only return the main asset and not any additional renditions generated? (Since the additional renditions will be avaliable from the asset detail window anyway…).
Thanks for your question. May I know about the keyword which you used by Quick Search ? You search by file name or keywords or label ?
If you do not want show the renditions of an original file in search result , so you can go to Administration —> Settings — > Find : “Renditions” —> Choose “Yes” at Hide renditions in search results.
You can omit the renditions from the search results by going to
Administration → Settings → and click yes in the section “Hide renditions
in search results”
I am using the quick search with no additional filtering, as far as I can tell it searches by filename. One of the keywords tested was “hd”, but other keywords yielded the same results (for any matching assets).
Great suggestion, but I was unable to find this option in our local version. So far we have been testing with the virtual machine version with Razuna version 1.7. After your comment I searched the Git repository for clues. Turns out the “Hide renditions in search results” option was first introduced to 1.8RC2 last week.
I guess we could try to merge the changes from the patch to our local 1.7 version, but this brings up what might be a more important question for us:
Since we are just getting starting with Razuna and have to decide what setup to use (mostly testing1.7 VM so far), is the 1.8RC2 stable for production use? Will we be able to upgrade from 1.8RC2 to the final 1.8 release once the time comes?
Actually, showing rendition in the search has been added for over sic month
now. In any case, I would recommend that you use Razuna 1.8. There are some
major search enhancement in that version, plus we separated the search from
the main app.
We are actually almost done with 1.8 and will release it in the next 1-2
weeks. How to update will be made public by then.
Your are of course completely correct. I checked again and I misread the date on this commit… seems I haven’t fully adjusted to 2016 on the calendar yet.
Sounds like 1.8 is the way to go. If we have to go live before the final release is out, in your estimation, would our best bet be to use 1.8RC2 and upgrade from there (instead of going from 1.7 to 1.8)?
Just use 1.8RC2. If you want you can even grab the “DEVELOP” branch from
Github. We are very, very close to release. Nothing groundbreaking is going
into 1.8 anymore. Just small fixes, maybe 1-2 more commits. We run most of
our customers on 1.8 already, even our hosted edition is on 1.8.
Oh forgot to say. If you use 1.8 you also need to download the
search-server. Just put it into the same web apps directory as razuna. It
is available at https://github.com/razuna/razuna-searchserver.git
The search server is auto-configured. But in case the search doesn’t work,
you can watch the catalina.out to see any errors. Look into this after you
set up Razuna.