Reese notes that the OSU metasearch solution uses the same approach as Ex Libris' MetaSearch; both are "metadata-driven knowledge base systems." He describes a key deficiency of code-based systems, such as III MetaFind, which require vendor mediation for activities such as making interface changes and repairing broken connectors.
Reese then describes the OSU metasearch architecture. The key component are:
- Knowledge base: employs a parent object/child object structure for simplicity
- API: link between the knowledge base and the resource
- Queried resources: must use "a standard query protocol or XML gateway interface"
- Translation service: ensures that the "connection class retain no information regarding the handling of supported metadata types"
Earlier this year, I participated in writing an NEH grant proposal related to Western Waters in which the use of this open source metasearch tool was projected to support cross-repository searching. As Reese notes, extending open source to metasearch is an intriguing development.
