EDIT

Wildcards in the same word seem to work. I tested with "chi*ll" on test.cyprus.

However, "chi*ll*san" to find Achillea santolinoides Lag. and similar taxa did not work. It needs a whitespace like "chi*ll san*". Is this expected behavior, then we should mention it in the search explanation.

For names with multiple whitespaces it is even more tricky.

wilhelm returns "Achillea santolinoides subsp. wilhelmsii (K. Koch) Greuter"

However, "subsp. *wilhelm" does not return anything. Same with "Achil* * * wilhelm" or "Achil* wilhelm"

The search seems not to be sorted. This is what I get for "V*"

Vitex
Vitis vinifera L.
Vitis
Vulpia brevis Boiss. & Kotschy
Vulpia
Vulpia ciliata Link
Vulpia fasciculata (Forssk.) Fritsch
Vulpia muralis (Kunth) Nees
Vulpia myuros (L.) C. C. Gmel.
Verbenaceae
Hordeum vulgare L. subsp. vulgare
Viola heldreichiana sensu R. D. Meikle
Vulpia membranacea sensu R. D. Meikle
Aegilops biuncialis Vis. subsp. biuncialis
Lobularia libyca (Viv.) Meisn.
Verbascum geminiflorum Hochst.
Aloe vera (L.) Burm. f.
Moricandia spinosa subsp. maroccana sensu R. Vogt & A. Aparicio
Amaranthus graecizans subsp. silvestris (Vill.) Brenan
Vaccaria hispanica (Mill.) Rauschert
...

was it like this before. Is the sorting by some kind of percentage?

The area search has a problem. Searching for "V*" and division1 returns NO result.
Searching for "*".

Searching for "*" and "Cyprus" return 1 1/2 pages (but should return almost the whole list)

OK, on th enew vesion of the cyprus database it works better. Especially the geo-search works better.

But synonym search does not seem to work.

Searching on "Phyla can*" with division6 and accepted+synonym finds Phyla canescens, but Same search on "Phyla fil*" does not find it's synonym Phyla filiformis (Schrad.) Meikle, but should.

Andreas Müller wrote:

OK, on th enew vesion of the cyprus database it works better. Especially the geo-search works better.

But synonym search does not seem to work.

Searching on "Phyla can*" with division6 and accepted+synonym finds Phyla canescens, but Same search on "Phyla fil*" does not find it's synonym Phyla filiformis (Schrad.) Meikle, but should.

This seems to happen only with subtree filter switched on. But is maybe related to the fix of this ticket as it was not recognized before. Looks like the current implementation does not return any synonyms if the subtree filter is switched on.

The subtree filter works very similar to the classification filter but uses a termQuery instead of IdQuery:

        if(classification != null){
            finalQueryBuilder.add(taxonBaseQueryFactory.newEntityIdQuery("taxonNodes.classification.id", classification), Occur.MUST);
        }
        if(subtree != null){
            finalQueryBuilder.add(taxonBaseQueryFactory.newTermQuery("taxonNodes.treeIndex", subtree.treeIndexWc(), true), Occur.MUST);
        }

The implementation of the term query has been changed within this ticket.

The classification filter does NOT have any effect in the webservice (1). But it has in the service(2)!

I tested (1) by changing the uuid in the service => returning same result, but should be empty because the classification does not exist. Also I added a second classification with a taxon name that is in both classification => both taxa were returned, though only 1 is in the filter classificaiton. Looks like the classification is set to null somewhere.
Not testing the return valud of classificationService.find(uuid) is definetely a bug. It should return an error message if classification does not exist. Or at least an empty result.

Then, the reason why it is always null is that the former parameter tree has been renamed to classification(Node)Uuid (cdmlib|bfda0eba8f7 and cdmlib|3b2b43193ee). Therefore it is not effective anymore :-(

I tested (2) by writing a test in TaxonServiceSearchTest. Not yet commited.

With the result of (2) - having an effect - the expected behavior is, that synonyms are not found at all, because the classification filter same as the subtree filter queries "taxonNodes.xxx", but for synonyms there is no such field. The field should be "accTaxon.taxonNodes.xxx" but this is not indexed. Maybe this worke some time ago when synonyms were still synonymRelations and the result was handled with the taxonRelationship index. Currently it can't work.

I moved synonym search and classification/subtree filters to new ticket #7764 as it is not really related to the topic of this ticket