{'fraction_non_alphanumeric': 0.03346203346203346, 'fraction_numerical': 0.017374517374517374, 'mean_word_length': 5.122047244094488, '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}}
Essential Audits for Proactive Electronic Resource Access Support

As electronic resource access (ERA) issues increase in frequency and complexity, technical services librarians are on the lookout for proactive techniques to identify and address these issues before they become a problem for patrons (Rathmel et al. 2015, 104-105). This poster highlights a number of “essential audits” employed by the ERA support team (eTeam) at Georgia Southern University to catch access issues before they are reported by patrons or public services personnel. Regular audits include bi-weekly link tests on the library’s A-Z Database List, quarterly link asset tests in LibGuides, and rolling link and authentication audits of link resolver records. Best Practices 1. Prioritize all resource audits according to usage or demand. 2. Use a ticketing system like LibAnswers or BugZilla to organize and track active audits. 3. Schedule and monitor reoccurring audits using a shared calendar like Google Calendars. 4. Use Google Sheets to easily share findings and adjust permissions on the fly. Include links to these sheets within their corresponding tickets for easy reference. 5. Utilize your content management system’s ability to create and map resource permalinks to reduce the number of locations where you need to correct URLs. Reference: Rathmel, Angela, Liisa Mobley, Buddy Pennington, and Adam Chandler. “Tools, Techniques, and Training: Results of an E-Resources Troubleshooting Survey.” Journal of Electronic Resources Librarianship 27, no. 2 (2015): 88-107.