To some extent, the /concepts keyword search is Google - like in that matches to any of the keywords are returned. Generally, it is suggested that a ranking of "high quality" (more keywords matched) results returned first versus "lower quality" result returned further down the list, is assumed (need to check if this expectation is well documented in the API).
However, it may be the case that users are only interested in "exact matches" to all keywords. Adding an "exactMatch" or "matchAll" flag to the input parameters as an expectation, could be helpful to make the keyword search more precise for some use cases.
Q: Do we need both: "exactMatch" might mean "exactly verbatim as written (keywords in order and including whitespace)" versus "matchAll" which might imply that the concept name must include (i.e. "match") all the keywords specified?
To some extent, the /concepts keyword search is Google - like in that matches to any of the keywords are returned. Generally, it is suggested that a ranking of "high quality" (more keywords matched) results returned first versus "lower quality" result returned further down the list, is assumed (need to check if this expectation is well documented in the API).
However, it may be the case that users are only interested in "exact matches" to all keywords. Adding an "exactMatch" or "matchAll" flag to the input parameters as an expectation, could be helpful to make the keyword search more precise for some use cases.
Q: Do we need both: "exactMatch" might mean "exactly verbatim as written (keywords in order and including whitespace)" versus "matchAll" which might imply that the concept name must include (i.e. "match") all the keywords specified?