Comment 4 for bug 1949214

I believe we are seeing this in 3.7.2 ,as well. I also believe this is due to the fix in LP #1912852.

Dan gives a good description.

When a metarecord search produces one result, it tries to go directly to the record. But it's using the ID field in metabib.metarecord, which isn't a bib ID at all. In our system, this can lead to some unexpected results.

We had a library report they tried to group formats/editions for a book about Muhammad Ali. When they executed the search, they were taken directly to a deleted record for a diet recipe book.

Ideally, when a Metarecord search is performed, the fix for LP #1912852 should not be honored, and the search results should simply display.