Closed nathandunn closed 8 years ago
The default is that these are "AND" closures.
for AND, this is done at the SOLR level we should be able to do fq=<1>&fq=<2>
for the OR case, it would be fq=(<1>OR<2>)
in both cases it is fq=subject_closure:DOID:123 or the like.
with the "OR" it is correct: 141 -1 = 140
with the "AND" it is 0
with DOID:14430 it is 131 -1 = 130
Orphanet:255249 it is 11 - 1 = 10
So, predictably no overlap in records.
if I replace with an AND . . I get the expected result (the same as the individual) and it provides an intersection.
GOLR should allow "OR" clauses in queries