Search bug or by design?

MJ. Smith

In verifying the results of the following search

• <1 Maccabees>

I ran the search

• "( "1 Macc", "1 Mac", 1M, "I Ma", 1Ma, "I Mac", 1Mac, "I Macc", 1Macc, "I Maccabees", 1Maccabees, "1st Maccabees", "First Maccabees") (1, 2, 3, 4, 5, 6, 7, 8, 9)"

thinking that a numeric character would omit false positives. However, it appears that this fails to pick up 2 digit chapters i.e. it requires a match up to the colon. Running the search

• "( "1 Macc", "1 Mac", 1M, "I Ma", 1Ma, "I Mac", 1Mac, "I Macc", 1Macc, "I Maccabees", 1Maccabees, "1st Maccabees", "First Maccabees") (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)"

appears to work for verification purposes. Is this the expected behavior? Is there any efficient way to avoid having to list all chapters?

Mark Barnes

Is this the expected behavior?

Yes. Numbers are treated like words when you search (so 1 won't find 100, just like a won't find abacus).

Is there any efficient way to avoid having to list all chapters?

Use wildcards: 1*, 2*, 3*,… 9*. Or RegEx. I'll experiment with that. It's a dark art I've yet to master [:)].