Yes to suppressing subfields. . . . for what it's worth, I'll relay that we see this URI information in our webpacPreferred Searches email that goes out to patrons. . . . When new materials tied to a person's preferred search come into the catalog, they get an email with basic bibliographic information the next Monday. Suppressing the $1 of the 1xx would be better for the patron experience.

Hi all! We were able to suppress these in our webpac catalog through the Web Options > Search Results > BROWSE file. To give an example, here's the line we currently have for browse_a "100/ad/ad|110/ad/ad|700/ad/|710/ad/."

This should also include all authorized fields, 6xx, 8xx, anything else I may have forgotten.

Even if you were using linked data, you probably don't want to look at this in your records all the time. It should hide away, and maybe have a rollover popup, or something to let you see it if you want to.

Also include subfield |0, not just |1.

At least once a week, I have to explain to staff what this link is--they all think it's some sort of cataloging error (which it's not), and/or they report that it's confusing to patrons. Until we have a clear path on how to use linked data, it would be most helpful to have this data suppressed.

Our cataloging staff enthusiastically supports this suggestion. I believe their exact words were "oh, hellz yeah."

Our staff in the branches get confused by this "messy" addition to the 1xx field; until we need it for linked data, we'd appreciate being able to suppress it.