Comment 3 for bug 1364652

Hi Kathy,

Yes, you are right! I do believe this issue is a duplicate reporting of the issue reported by Tim.

But to clarify the difference between a complete and isolated set.

An "isolated" auth/bib set would be the following:

Auth A:
=100 1\$aPoppen, Nikki,$d1967-
=400 1\$aPoppen-Eagen, Nikki,$d1967-
=400 1\$aEagen, Nikki Poppen-,$d1967-
=500 1\$aScott, Bronwyn,$d1967-

Bib A:
Book by Poppen, Nikki,$d1967-

It is when you simply have an auth, and one or more bibs linked to that auth. It consists of just one auth and its associated bibs. None of Auth A's 4xx will surface when browsing for them.

A "complete" auth/bib set would be the following:

Auth A:
=100 1\$aPoppen, Nikki,$d1967-
=400 1\$aPoppen-Eagen, Nikki,$d1967-
=400 1\$aEagen, Nikki Poppen-,$d1967-
=500 1\$aScott, Bronwyn,$d1967-

Auth B:
=100 1\$aScott, Bronwyn,$d1967-
=500 1\$aPoppen, Nikki,$d1967-

Bib A:
Book by Poppen, Nikki,$d1967-

It is when you have an auth, and one or more bibs linked to that auth. Additionally, that auth is also linked to its cross reference. It's that additional interlinking between Auth A & Auth B that turns this into a "complete" set versus an "isolated" set. Now, Auth A's 4xx will surface when browsing for them.

Again, this is a duplicate reporting of bug: https://bugs.launchpad.net/evergreen/+bug/1358392?

I think we were both trying to report the fact that if there is no See Also reference for an auth, the unauthorized references for that auth do not surface in browse result, and that this should not be the case. See Also references should not have to exist for an auth for its unauthorized references to surface in browse results.