Hi Bob,

This explanation comes from our Head Cataloger:

By check a URL, I mean to run the record through the URL checker to see whether each URL in the catalog works (opens desired document) or not. This happens when opening and running the function of URL checker. This function then groups errors into various categories for types of errors found by the URL checker.
For various reasons, we use a suppression code in our BIB records. This enhancement would prevent those BIBS from running through the URL checker every time, overpopulating the error report needlessly.

Elaine, could you explain the benefit of this idea? For starters, what does it mean to check a URL? I have seen the feature in Sierra, but don't understand its purpose. Thank you.

@Elaine, in most cases, for an idea submitted through Idea Exchange, like yours, in order for it to be brought into production, it first has to be selected for an enhancement ballot & then be among the winning ideas once put to a vote by the user community.

The Sierra MEEP group has been discussing the possibility of a different approach for the next round of voting to give ideas like yours more of a shot at being brought to fruition.

Beginning with the ballot for 7.2 later this year, we may alternate between a general ballot where all eligible Sierra ideas are considered for inclusion, & a more focused one, where only those from a specific category, like Cataloging & Metadata Management, Reporting & Analytics, Acquisitions, Serials & Inventory Management, etc. are considered.

This approach would be an opportunity for ideas that may not have broad appeal but are still impactful a better chance of not only making the ballot, but winning.

Any updates? We are currently using v.6.6.0_4 and see no changes.

A set of rules for which bibs are checked by URL Checker would make that function much more useful.