Hi Tonio,
A couple of tips that might help:
First, just about any parameter that can be used in the advanced search interface can also be applied to the information object browse REST API endpoint. In the advanced search, you can limit a field to searching against the reference code, which should help narrow the results.
Second, there should be a big difference if you use quotations in your search. When you search without quotations, then AtoM will use AND as the default operator between any element. In some cases, dashes are also ignored (and treated as spaces) so a search for CH FF1971-C-A-01 can in fact be interpreted as a search for:
- CH in any field, AND
- FF1971 in any field, AND
- C in any field, AND
- A in any field AND
- 01 in any field
When you put a string in quotations, it tells the search index to perform an exact search - meaning only matches that have CH FF1971-C A-01 in that exact order will be considered matches.
Here's an example of searching for a record by putting the full reference code in quotations, and limiting the matching results to the reference code field in the Demo site:
You should be able to apply very similar parameters to a REST API query, like so:
- [your base URL here - e.g. https://www.example.com]/api/informationobjects?
sq0=%22CH FF1971-C A-01%22&sf0=referenceCode&topLod=0
Hopefully that will help return more precise results?
Finally, please note that there have been some improvements to the search index in release 2.6.3 that might help remove noise from the results. If you've not updated to the most recent version, you may wish to try this.
Cheers,