fix: thesaurus retrieval from UI when editing a metadata

[f-necas]

When a thesaurus contains keys which can be contained in another, it may display the wrong key when editing a metadata.

By example, there's two thesaurus keys http://domain.com/mykey/1 and http://domain.com/mykey/12.

Depending on the order in the thesaurus, if I have the first one in my metadata record, geonetwork may answer with the second one.

How to replicate:

• Import this thesaurus place-test.zip
• Edit/create a record and add this thesaurus with Test 1 keyword
• Save and close
• Check value: Will be ok Test 1
• Re-edit the record and go to thesaurus part
• 🚫 The value show will be Test wrong

[pmauduit]

I am not into JS, but I'd have expected that the typeSearch parameter should be set elsewhere so that the filter is used as is / without using wildcards ?

[f-necas]

I am not into JS, but I'd have expected that the typeSearch parameter should be set elsewhere so that the filter is used as is / without using wildcards ?

The filter is already set without wildcard, and is used inside the q parameter above.

q: filter || "",
uri: (typeSearch === "MATCH" ? filter : "*" + filter + "*") || "",