31 Ottobre, 2016
Every library is unique in some way, so it is logical that libraries need to take different approaches to evaluating which discovery service might be right for them.
There have been a significant number of published papers and conference presentations in recent years about how to evaluate, select, and choose a discovery service. Included within this vast repository of information are pieces that focus on particular aspects of this selection process – including cost, relevance ranking, service administration, customization options, content coverage, usability, APIs, mobile interfaces, library management system integration, linking options and more. Quite often, though, the most obvious outcome that libraries want from a discovery service – to ensure that all library collections, especially currently underutilized collections, are discovered equally – takes a backseat as a deciding factor in favor of a more feature-oriented approach.
This is where the concept of content neutrality comes into play. In our recent blog posts on content neutrality we pointed out some of the dangers of ignoring content neutrality in discovery, including promoting bias by favoring one content vendor over another, a bias that has potential consequences on both equal discovery and research integrity.
Compelling vendors to adhere to content neutrality principles through UX and UI design will enhance the discovery of library content and improve research outcomes. Failing to factor in content neutrality in the library’s discovery service choice will likely mean falling short of the library’s goals for choosing a discovery service in the first place.
- How does the system protect a content-neutral approach?
- Are records handled in a way that does not filter out data?
- Does the handling of duplicate items systematically favor one content provider over another?
- Does the relevancy-ranking approach weight items disproportionately?
- Does the discovery provider enrich the metadata of some content provider records, but not others, influencing the discovery of those records?
- Are all content providers treated equally in the display of results?
- How do the user interface and experience maintain a provider-agnostic approach?
- Are there any aspects of the interface that bias the user, or foster future bias?
- Is the delivery of data influenced by any factors that the vendor controls?
- Does the vendor do anything from a technical standpoint that overtly favors the vendor’s own content?
- If the return of results seems to bias results in favor of the vendor’s own content, is that circumstantial or deliberate?
- If there are elements such as URLs, return of results, platform elements, results display and interface design that seem to favor a vendor’s own content, is that incidental or intentional?
Libraries, librarians, and patrons will benefit from scrutinizing the neutrality of discovery systems with these types of questions.