{'fraction_non_alphanumeric': 0.014755959137343927, 'fraction_numerical': 0.0, 'mean_word_length': 5.391304347826087, '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}}
Using the open archives initiative protocols with EAD

The Open Archives Initiative Protocols present a promising opportunity to make metadata about archives, manuscript collections, and cultural heritage resources easier to locate and search. However, several technical barriers must be overcome before useful OAI records can be produced from the disparate metadata formats used to describe these resources. This paper examines Encoded Archival Description (EAD) as a test case of the issues to be addressed in transforming cultural heritage metadata to OAI. While EAD and OAI may appear to be incompatible, a mapping would be both useful and technically feasible. The authors suggest that it will be necessary to create numerous OAI records from one EAD file. In addition, the findings indicate that further standardization of EAD markup practices would enhance interoperability.