{'fraction_non_alphanumeric': 0.01639344262295082, 'fraction_numerical': 0.0, 'mean_word_length': 5.603603603603603, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Vendor-Supplied Authority Control: Some Realistic Expectations

ABSTRACT Automated authority control systems can be used to clean up an existing database, provide ongoing authority control for current cataloging, and keep the entire database synchronized with changes in headings. If your library decides to outsource your authority control to a vendor, that is, to contract to a vendor the authority control workload that would otherwise be performed by library employees, it is very important to understand what can be expected of vendor-supplied authority control and what must be done locally to supplement those services. This article discusses some realistic and unrealistic expectations for vendor-supplied authority control.