I first looked at this bug on our production (EG 3.7.2) and test (EG 3.9.1) servers to familiarize myself with the issue. I saw what both Mieke and Carol reported. I tested the fix on the Mobius server.
I imported a new record (#353) that includes both a 100 and a 600 field. In the MARC edit screen, I chose to create an authority link from the 100 field. A list of potential authority record matches displayed as expected. The same was true when creating an authority link from the 600 field.
Please see attached screenshot (prince_600_mobius.png).
I also chose to create authority links from the 655 field in a different bib record (#77) and a list of potential authority record matches displayed in this case, as well.
Please see attached screenshot (sibelius_655_mobius.png).
Unless I have misunderstood the initial bug report, this fix appears to work great. Do either of the original posters have additional comments?
I first looked at this bug on our production (EG 3.7.2) and test (EG 3.9.1) servers to familiarize myself with the issue. I saw what both Mieke and Carol reported. I tested the fix on the Mobius server.
I imported a new record (#353) that includes both a 100 and a 600 field. In the MARC edit screen, I chose to create an authority link from the 100 field. A list of potential authority record matches displayed as expected. The same was true when creating an authority link from the 600 field.
Please see attached screenshot (prince_ 600_mobius. png).
I also chose to create authority links from the 655 field in a different bib record (#77) and a list of potential authority record matches displayed in this case, as well.
Please see attached screenshot (sibelius_ 655_mobius. png).
Unless I have misunderstood the initial bug report, this fix appears to work great. Do either of the original posters have additional comments?